Skip to main content

How to Add Custom MCP Servers?

Through the Model Context Protocol (MCP), AI models can access external tools and data sources, enabling more powerful functionality. ConsoleX AI provides comprehensive support for MCP tools, including SSE-based and Stdio-based MCP servers.

Integrating and Using MCP Servers in ConsoleX​

Adding and using MCP services in ConsoleX AI is very simple, just follow these steps:

  1. Log in to ConsoleX AI and click the Tools Vault entry at the bottom-left corner.
  2. Click the Add a MCP server button at the top of the page.
  3. Fill in the JSON description of the MCP server.
  4. Click the Save button to complete the MCP server integration.

MCP Custom

How to Configure SSE-based MCP Servers​

Configuring and adding SSE-based MCP servers in ConsoleX AI is very simple, just enter the following format configuration:

{ 
  "url": "<your_sse_mcp_server_endpoint>" 
}

You can also add any additional parameters, all those parameters will be passed to the server through header attributes. For example, you can add header authentication or pass other configuration parameters:

{ 
  "url": "<your_sse_mcp_server_endpoint>", 
  "Authorization": "Bearer <your_auth_token>", 
  "timezone": "Europe/Berlin" 
}

Note: SSE servers need to extract parameters from headers for authentication or use in functional logic themselves.

How to Configure Stdio-based MCP Servers​

ConsoleX is a cloud service, so it cannot directly call local resources through Stdio. However, you can use MCP-connect to implement relay and enable MCP server calls with Stdio transport protocol.

The specific steps are as follows:

  1. Install and run mcp-connect on your local computer and set the auth_token for security consideration.
  2. Make your MCP proxy URL publicly accessible through tunnel services (such as ngrok or Cloudflare Zero Trust).
  3. Enter the global MCP proxy URL and auth_token in ConsoleX Settings.
  4. Then you can add Stdio-based MCP server configurations on ConsoleX just like a local MCP client.

Individual Configuration:

Besides setting global proxy endpoints and auth_token, you can also set bridge_url and auth_token individually for each MCP server. Individual settings will override global configurations.

For example:

{
    "bridge_url": "<your_mcp_bridge_url>",
    "auth_token": "<your_auth_token>",
    "command": "uvx",
    "args": ["mcp-server-fetch"]
}

Frequently Asked Questions​

Q: Which models support MCP servers?

A: The MCP protocol was initiated by Anthropic, so Claude's Sonnet and Opus model series can provide better support for MCP server calls. However, the tool part of MCP servers is available for any other large model that supports tool calling.

Q: What are the limitations of using MCP servers in ConsoleX?

A: You cannot directly add Stdio-based MCP servers in ConsoleX, but you can implement MCP calls with Stdio transport protocol through MCP Bridge.

Q: I cannot successfully add local Stdio-based MCP servers, what should I do?

A:

  1. First, please ensure that mcp connect has been successfully installed and is running.
  2. Confirm that the mcp connect endpoint can be accessed through the public network (you can confirm this through the health check endpoint).
  3. If the endpoint is accessible but there are still issues, please check the output logs of mcp connect in the terminal to find the cause.