> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evo-ai.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom MCP

> Configure custom external MCP servers with SSE and custom authentication

## Overview

**Custom MCP** allows you to connect external MCP servers hosted on your own infrastructure or third-party services. This functionality offers maximum flexibility to:

* **Integrate your own MCP servers** hosted externally
* **Connect with specialized APIs** not available in the Evo AI library
* **Use custom authentication** with personalized headers
* **Implement SSE (Server-Sent Events)** for real-time communication

<Note>
  **External Servers**: Unlike the Evo AI library, here you configure externally hosted MCP servers.
  You are responsible for the maintenance and availability of these servers.
</Note>

## How to Configure a Custom MCP

The Custom MCP configuration process has been divided into two main steps:

1. **Register the Custom MCP** in the settings menu
2. **Select the Custom MCP** in the agent settings

### Part 1: Register Custom MCP

<AccordionGroup>
  <Accordion icon="gear" title="Access settings menu">
    1. In the main menu, go to **"Settings"**
    2. Look for the **"Tools & Integrations"** section
    3. Within it, click on **"Custom MCP"**
    4. Click on **"Add New Custom MCP"** or **"New Custom MCP"**
    5. You will be directed to the registration form

    <Info>
      Here you will create a library of Custom MCPs that can be reused across different agents.
    </Info>
  </Accordion>

  <Accordion icon="server" title="Basic server information">
    Configure the fundamental information of your MCP server:

    **Server Name:**

    * Identifier name for the server
    * Used for internal reference
    * Example: "Custom CRM Server", "Financial API"

    **Description:**

    * Description of the functionalities offered
    * Helps you and other users understand the purpose
    * Example: "Integration with internal CRM system"

    **MCP Server URL:**

    * Complete endpoint of your external MCP server
    * Must support the standard MCP protocol
    * Example: `https://my-server.com/mcp`

    <Tip>
      Use descriptive names to facilitate identification when selecting in agents.
    </Tip>
  </Accordion>

  <Accordion icon="shield" title="Authentication configuration">
    Configure headers necessary for authentication:

    **Custom Headers:**

    ```json theme={null}
    {
      "Authorization": "Bearer your-token-here",
      "X-API-Key": "your-api-key",
      "X-Custom-Header": "custom-value",
      "Content-Type": "application/json"
    }
    ```

    **Supported authentication types:**

    * **Bearer Token** - For OAuth APIs
    * **API Key** - Simple access keys
    * **Basic Auth** - Encoded username and password
    * **Custom Headers** - API-specific headers

    <Warning>
      Authentication headers are stored in encrypted form on the platform.
    </Warning>
  </Accordion>

  <Accordion icon="bolt" title="SSE configuration and advanced options">
    **SSE (Server-Sent Events) Support:**

    * ✅ **Real-time response streaming**
    * ✅ **Continuous status updates**
    * ✅ **Push notifications** from server
    * ✅ **Persistent connections** for low latency

    **Advanced settings:**

    * **Timeout**: Connection timeout limit
    * **Retry attempts**: Reconnection attempts
    * **SSE endpoint**: Specific endpoint for events

    <Tip>
      SSE is ideal for servers that process long tasks or provide real-time updates.
    </Tip>
  </Accordion>

  <Accordion icon="check" title="Save Custom MCP">
    1. **Review all settings** carefully
    2. **Test connectivity** if there's a test option
    3. Click **"Save"** or **"Save"**
    4. The Custom MCP will be available in your library

    <Info>
      After saving, the Custom MCP will be available to be selected in any agent.
    </Info>
  </Accordion>
</AccordionGroup>

### Part 2: Select Custom MCP in Agent

<AccordionGroup>
  <Accordion icon="robot" title="Access agent settings">
    1. Go to the **agents screen** in the dashboard
    2. Locate the agent you want to configure
    3. Click the **"Settings"** icon (⚙️) on the agent card and then **"Edit"**
    4. You will be directed to the agent settings screen
  </Accordion>

  <Accordion icon="plus" title="Add Custom MCP to agent">
    1. In the agent settings screen, locate the **"Custom MCP"** section
    2. Click **"Add"** to add a Custom MCP
    3. A **list of registered Custom MCPs** will be displayed
    4. **Select the servers** that this agent should use
    5. Click **"Save"** to apply

    <Info>
      You can select multiple Custom MCPs for the same agent. Each agent can have a different set of servers.
    </Info>
  </Accordion>

  <Accordion icon="check" title="Verify configuration">
    **After saving:**

    * The selected Custom MCPs will appear in the agent's list
    * The agent will have access to the tools from these servers
    * You can add/remove servers at any time

    <Tip>
      Test the agent in a conversation to verify that the Custom MCPs are working correctly.
    </Tip>
  </Accordion>
</AccordionGroup>

## Advantages of the New System

<AccordionGroup>
  <Accordion icon="recycle" title="Server reusability">
    **Benefits:**

    * 🔄 **Reuse** the same Custom MCP across multiple agents
    * 🎯 **Specialize** agents with specific servers
    * 🛠️ **Maintain** centralized configurations
    * 📊 **Manage** all servers in one place
  </Accordion>

  <Accordion icon="users" title="Team collaboration">
    **Facilitates teamwork:**

    * 👥 **Share** Custom MCPs among team members
    * 📚 **Centralized library** of organizational servers
    * 🔧 **Simplified maintenance** of integrations
    * 📈 **Server evolution** without impact on agents
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion icon="triangle-exclamation" title="Common issues">
    **Server won't connect:**

    * Verify that the URL is correct and accessible
    * Confirm that authentication headers are valid
    * Test network connectivity
    * Check if the server is online

    **Authentication error:**

    * Validate tokens and API keys
    * Confirm header format
    * Check if credentials haven't expired
    * Test authentication directly on the server

    **SSE not working:**

    * Confirm if server supports Server-Sent Events
    * Check specific headers for SSE
    * Test events endpoint separately
    * Monitor reconnection logs

    **Tools don't appear:**

    * Check `/mcp/capabilities` endpoint
    * Confirm JSON response format
    * Validate tool structure
    * Test manual calls to the server
  </Accordion>
</AccordionGroup>

***

🔧 **Custom MCP configured!** Now you can integrate custom external MCP servers with custom authentication and SSE support for maximum flexibility!