A side-by-side look at the Mcpqueen and Mcpproxy Go MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mcpqueen for aggregators work over a hosted endpoint; choose Mcpproxy Go for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mcpqueen when
You need dedicated capabilities in the Aggregators domain.
You prefer a remote HTTP/SSE transport.
Its auth model fits you: No auth required.
You have the keys it needs: OPENAI_API_KEY, HF_TOKEN.
No tool names declared yet. Check the project README from the listing page.
Mcpproxy Go tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mcpqueen is categorized under Aggregators and uses a remote HTTP/SSE transport. Mcpproxy Go belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Mcpqueen for aggregators work and Mcpproxy Go for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mcpqueen is listed as free. Auth: no auth required. Mcpproxy Go is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcpqueen-mcpqueen and smart-mcp-proxy-mcpproxy-go as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mcpqueen has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Mcpproxy Go has 57/100 (Good) with 6 views, 0 installs and 387 GitHub stars.