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 needmcp-proxy
to convert between stdio and HTTP/SSE protocols.
Authentication Methods
API Key Authentication
API Key Authentication
Most common method using environment variable:
No Authentication
No Authentication
For public endpoints without authentication:
Troubleshooting
Common Issues
- Connection refused: Ensure MetaMCP is running and accessible
- Authentication failed: Verify API key is correct and has proper permissions
- mcp-proxy not found: Install with
pip install mcp-proxy
oruvx mcp-proxy
Debug Mode
Enable debug logging for mcp-proxy: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