One live MCP endpoint — POST https://wingmanprotocol.com/mcp — works anonymously out of the box. A free key (500 calls/month) raises your quota.
# one command — HTTP transport, no bridge needed claude mcp add --transport http wingman https://wingmanprotocol.com/mcp
Then in any session: /mcp shows the wingman server, and the model can call its tools directly.
Claude Desktop's config is stdio-only, so the remote server goes through the mcp-remote bridge. Merge this into claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"wingman": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://wingmanprotocol.com/mcp"]
}
}
}Ready-made: /mcp/claude-desktop.json (alias /mcp/claude.json). Restart Claude Desktop after saving.
Or merge into ~/.cursor/mcp.json (or the project's .cursor/mcp.json):
{
"mcpServers": {
"wingman": {
"url": "https://wingmanprotocol.com/mcp",
"transport": "http"
}
}
}Ready-made: /mcp/cursor.json.
Add to your Continue config (config.yaml uses the same fields):
{
"name": "wingman",
"transport": { "type": "http", "url": "https://wingmanprotocol.com/mcp" }
}Ready-made: /mcp/continue-dev.json.
Ask your agent to call discover_tools — it's the catalog meta-tool, free, and proves the whole pipe end-to-end:
> call discover_tools with query "memory"
Or verify from a terminal without any client:
curl -s https://wingmanprotocol.com/mcp -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"discover_tools","arguments":{"query":"memory"}}}'A list of live tools comes back — you're connected.
Anonymous use works (IP rate-limited). A free key gives you 500 calls a month and attributes usage to you:
curl -s https://wingmanprotocol.com/keys/issue -H 'Content-Type: application/json' \
-d '{"email":"[email protected]","tier":"free"}'
# → {"api_key":"wa_live_...","monthly_limit":500}Send it as the X-API-Key header on REST calls. Quotas and paid options: pricing.