Getting Started with an MCP Server Connector in June AI

To activate your June agents to communicate with other real systems (e.g., CRM, internal tools) you need a MCP (MedeAnalytics Connect To People) Server Connector. It is effectively a bridging mechanism between. An agent's conversation with the user and perform all actions within the infrastructure. The arrangement one Once you understand what is what, the above is easy. Each field represents.

Step 1: Navigate to Connectors

From the left-hand menu, open the Connectors section. You'll find the option to create a new connector in the top-right corner. Click Create Connector to begin.

Step 2: Add Basic Information

Connector Name

Give the connector a name that makes sense to your team. For example, if this server connects to your CRM, something like CRM MCP works well. If it's tied to internal APIs, you might name it Backend Services Connector. Choose clarity over creativity.

Server URL

Enter the base URL of your MCP server. This is where the agent will send requests. It usually looks something like:

https://api.yourcompany.com/mcp

If the server is internal, make sure it's accessible through the proper network configuration. If it's public-facing, confirm that authentication is enforced.

Configuration

In the configuration field, you can define headers or required parameters. Most setups will include JSON headers and an authorization token. For example:

{ "Content-Type": "application/json", "Authorization": "Bearer {{secure_token}}" }

Avoid placing real production tokens directly in visible configurations. Use secure environment variables whenever possible.

Country

Select the country relevant to this connector. This setting can help align the connector with region-specific services or compliance considerations.

Description

Add a short description explaining what this connector is responsible for. For example: "This connector enables agents to create leads and retrieve customer information from the CRM system."

Step 3: Set Visibility

In the Visibility tab, decide who should have access to manage this connector. You can add team members individually. By default, the creator becomes the owner.

Step 4: Create the Connector

Once everything looks correct, click Create. The connector will then be available for assignment to agents.

A Few Practical Tips

• Use proper authentication when connecting to live systems. Security should never be an afterthought.
• Version your server endpoints when possible. It helps prevent unexpected issues if your backend changes later.
• Before using the connector in production workflows, test it with a staging agent. A quick validation step can save hours of troubleshooting later.