Integration of Knit MCP Server with June AI Agent

The purpose of this page is to clarify a common point of confusion when working with Knit and June AI. What Knit refers to as an MCP Server is referred to as a Connector within June AI. This difference in naming can be confusing, especially for users who are new to the June AI platform.

In simple terms, June AI consumes MCP services provided by Knit. The connection is created from within an individual agent, rather than from a global or system-level settings page.

What Does This Connection Allow?

Once the connection is established, the June AI Agent can use the tools that are hosted on the Knit MCP Server. There is no additional middleware involved. All interactions occur through direct calls made by the agent to the permitted MCP endpoints.

If functionality issues occur after setup, they are rarely caused by MCP itself. In most cases, the problem is related to missing permissions or an incorrect access token.

Items to Verify Before Accessing June AI

These checks are basic, but verifying them early will prevent unnecessary troubleshooting later.

•  The Knit MCP Server endpoint responds to a direct request.
•  You understand which authentication method is required (token, header, key, etc.).
•  You have permission to edit the agent within June AI.

Where MCP Is Located in June AI

MCP settings are not located in general system or application settings. Instead, MCP is attached directly to each agent that you create.

To add an MCP Server, open the agent you want to configure and navigate to the Connectors section. From there, select the option to add a new connector.

Instructions for Adding a New MCP Connector

Follow the steps below to add a Knit MCP Server as a connector:

1. Click the Add Connector button. Depending on your setup, this option may appear as MCP or MCP Server.
2. Paste the Knit MCP Server endpoint into the provided field.
3. Enter the required username and password.
4. Click Save to complete the setup.

If the connector fails to save at this stage, stop and resolve the issue immediately. Continuing with the setup without a successful save will not resolve the problem.

The Importance of Permissions

After the MCP Connector has been created, not all tools are available to the agent by default. Each tool must be explicitly enabled or granted permission before it can be used.

If you encounter a "Tool Not Found" error, this usually indicates that the connector itself is working correctly, but permission for the specific tool has not yet been enabled.

Testing the MCP Connection

When testing the connection, keep the initial test simple. Make a single request and verify that a single response is returned successfully.

Once the basic test succeeds, you can proceed with more complex calls and workflows using the MCP Connector.

MCP Connector Stability in June AI

MCP Connectors are generally very stable in June AI once configured correctly. Most issues arise from rushing through the initial setup or skipping the permissions step. Taking a few extra minutes to verify configuration and permissions helps avoid repeated issues later.