Prerequisites
Before starting, ensure you have:- MCP client that supports stdio servers (Claude Desktop, Cursor, etc.)
- MetaMCP running locally or deployed with OAuth enabled
- Active endpoint configured in MetaMCP
- OAuth application registered in MetaMCP
- mcp-remote available via npx (
npx -y mcp-remote
)
Basic Configuration
Using mcp-remote (Required)
Since MetaMCP endpoints are remote only, you needmcp-remote
to convert between stdio and HTTP/SSE protocols with OAuth authentication.
OAuth Flow
When you first connect,mcp-remote
will:
- Open your browser to the OAuth authorization URL
- Prompt you to authorize the application
- Redirect back to the local callback server
- Store the tokens locally for future use
- Establish the MCP connection with authenticated access
Token Management
- Tokens are stored locally by mcp-remote
- Refresh tokens are automatically used when access tokens expire
- Clear tokens by deleting the mcp-remote cache directory if needed
Important Notes
- Use
http://localhost:12008/metamcp/your-endpoint-name/mcp
for OAuth authentication - Replace
your-endpoint-name
with your actual endpoint name for public endpoints - mcp-remote handles the protocol conversion between stdio and HTTP/SSE
- OAuth flow requires browser interaction on first connection
- No manual OAuth setup required - MetaMCP handles it automatically
MCP OAuth Troubleshooting
Troubleshoot common OAuth-related issues
General Stdio Integration using `mcp-proxy` with API Key
Configure any stdio-based MCP client to connect to MetaMCP endpoints using mcp-proxy
Connect to Cursor
Configure Cursor IDE to use your MetaMCP endpoints
Connect to Claude Desktop
Set up Claude Desktop with MetaMCP using mcp-proxy