MCP Proxy Server

What does “MCP Proxy” MCP Server do?

The MCP Proxy Server is a tool that aggregates and serves multiple MCP (Model Context Protocol) resource servers through a single HTTP server. By acting as a proxy, it allows AI assistants and clients to connect to several different MCP servers at once, combining their tools, resources, and capabilities into a unified interface. This setup simplifies integration, as developers and AI workflows can access a variety of external data sources, APIs, or services through a single endpoint. The MCP Proxy Server supports real-time updates via SSE (Server-Sent Events) or HTTP streaming and is highly configurable, making it easier to perform complex tasks such as database queries, file management, or API interactions by routing them through the appropriate underlying MCP servers.

List of Prompts

No information about prompt templates is provided in the repository or documentation.

Ready to grow your business?

Start your free trial today and see results within days.

Request demo Log in

List of Resources

No explicit resources are documented in the repository or example configuration. The server aggregates resources from connected MCP servers, but none are listed directly.

List of Tools

No tools are directly provided by the MCP Proxy Server itself; it acts as a proxy to tools from other configured MCP servers (such as github, fetch, amap as seen in the configuration example).

Join our newsletter

Get latest tips, trends, and deals for free.

Email address

Subscribe

Use Cases of this MCP Server

• Aggregating Multiple MCP Servers: Developers can connect several different MCP servers (e.g., for GitHub, Fetch, or Amap) through one proxy endpoint, simplifying setup and management.
• Unified API Gateway: Acts as a unified gateway for AI assistants to access various external APIs and data sources via the MCP protocol, reducing integration complexity.
• Real-Time Data Streaming: Supports SSE/HTTP streaming, enabling real-time updates from underlying MCP resource servers.
• Flexible Client Support: Can interface with different types of clients (stdio, sse, streamable-http), making it adaptable for diverse workflow requirements.
• Centralized Authentication & Logging: Offers centralized configuration for authentication tokens and logging, improving security and traceability when accessing multiple MCP resources.

How to set it up

Windsurf

1. Ensure you have Node.js and access to Windsurf configuration files.
2. Open your Windsurf configuration and locate the mcpServers section.
3. Add the MCP Proxy Server using the following JSON snippet:

   "mcpServers": {
     "mcp-proxy": {
       "command": "npx",
       "args": ["@TBXark/mcp-proxy@latest"],
       "env": {
         "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
       }
     }
   }
   

4. Save your configuration and restart Windsurf.
5. Verify the MCP Proxy Server appears in the Windsurf UI.

Note: Secure your API keys using environment variables as shown above.

Claude

1. Locate Claude’s configuration interface or file.
2. Add the MCP Proxy Server to the mcpServers section:

   "mcpServers": {
     "mcp-proxy": {
       "command": "npx",
       "args": ["@TBXark/mcp-proxy@latest"],
       "env": {
         "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
       }
     }
   }
   

3. Save the configuration and restart Claude.
4. Confirm the MCP Proxy Server is recognized by Claude.

Note: Use environment variables for secret tokens.

Cursor

1. Make sure you have Node.js installed and access to Cursor configuration.
2. Edit the Cursor configuration and add the following:

   "mcpServers": {
     "mcp-proxy": {
       "command": "npx",
       "args": ["@TBXark/mcp-proxy@latest"],
       "env": {
         "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
       }
     }
   }
   

3. Save changes and restart Cursor.
4. Check that the MCP Proxy Server is available.

Note: Use environment variables for sensitive credentials.

Cline

1. Open the Cline configuration file.
2. Insert the MCP Proxy Server details:

   "mcpServers": {
     "mcp-proxy": {
       "command": "npx",
       "args": ["@TBXark/mcp-proxy@latest"],
       "env": {
         "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
       }
     }
   }
   

3. Save and restart Cline.
4. Confirm functionality in the Cline interface.

Note: Secure API keys using the env property as in the example.

Example: Securing API Keys

"mcpServers": {
  "github": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-github"],
    "env": {
      "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
    }
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "mcp-proxy": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “mcp-proxy” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Based on the above, the MCP Proxy is a useful aggregation layer for MCP resources but lacks direct tools, resources, or prompt templates; it’s mainly a configuration and routing solution.

Our opinion

This MCP server is best rated as a backend utility, not suited for standalone use but excellent for aggregating and managing multiple MCP servers in a unified workflow. Its documentation is clear for configuration and security, but lacks details on prompts, tools, and resources. Overall, it is a solid infrastructure piece for advanced users. Score: 5/10.

MCP Score