Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.metamcp.com/llms.txt

Use this file to discover all available pages before exploring further.

General Stdio Integration allows any MCP client that supports stdio servers to connect to MetaMCP’s remote endpoints. Since MetaMCP endpoints are remote-only (SSE, Streamable HTTP), you’ll need a local proxy to bridge the connection.

​
Prerequisites

Before starting, ensure you have:
  • MCP client that supports stdio servers (Claude Desktop, Cursor, etc.)
  • MetaMCP running locally or deployed
  • Active endpoint configured in MetaMCP
  • API key generated (if authentication is enabled)
  • mcp-proxy installed (uvx mcp-proxy)

​
Basic Configuration

​
Using mcp-proxy (Required)

Since MetaMCP endpoints are remote only, you need mcp-proxy to convert between stdio and HTTP/SSE protocols. 
{
  "mcpServers": {
    "MetaMCP": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "--transport",
        "streamablehttp",
        "http://localhost:12008/metamcp/your-endpoint-name/mcp"
      ],
      "env": {
        "API_ACCESS_TOKEN": "sk_mt_your_api_key_here"
      }
    }
  }
}

​
Authentication Methods

Most common method using environment variable:
{
  "mcpServers": {
    "MetaMCP": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "--transport",
        "streamablehttp",
        "http://localhost:12008/metamcp/your-endpoint-name/mcp"
      ],
      "env": {
        "API_ACCESS_TOKEN": "sk_mt_your_key_here"
      }
    }
  }
}
For public endpoints without authentication:
{
  "mcpServers": {
    "MetaMCP": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "http://localhost:12008/metamcp/your-endpoint-name/sse"
      ]
    }
  }
}

​
Troubleshooting

​
Common Issues

  1. Connection refused: Ensure MetaMCP is running and accessible
  2. Authentication failed: Verify API key is correct and has proper permissions
  3. mcp-proxy not found: Install with pip install mcp-proxy or uvx mcp-proxy

​
Debug Mode

Enable debug logging for mcp-proxy: 
{
  "mcpServers": {
    "MetaMCP": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "--transport",
        "streamablehttp",
        "--debug",
        "http://localhost:12008/metamcp/your-endpoint-name/mcp"
      ],
      "env": {
        "API_ACCESS_TOKEN": "sk_mt_your_api_key_here"
      }
    }
  }
}

​
Important Notes

  • Replace your-endpoint-name with your actual endpoint name
  • Replace sk_mt_your_api_key_here with your MetaMCP API key
  • mcp-proxy handles the protocol conversion between stdio and Streamable HTTP/SSE
  • Environment variables are the secure way to pass API keys

General Stdio Integration using `mcp-remote` with OAuth` with API Key

Configure any stdio-based MCP client to connect to MetaMCP endpoints using mcp-remote with OAuth

MCP OAuth Troubleshooting

Troubleshoot common OAuth-related issues

Connect to Cursor

Configure Cursor IDE to use your MetaMCP endpoints

Connect to Claude Desktop

Set up Claude Desktop with MetaMCP using mcp-proxy