Mcpproxy Go vs Findagent MCP
A side-by-side look at the Mcpproxy Go and Findagent MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mcpproxy Go for aggregators work over a hosted endpoint; choose Findagent MCP 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 Mcpproxy Go when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Findagent MCP when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 57/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 387 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mcpproxy Go | View Findagent MCP |
Tools & capabilities
Mcpproxy Go tools
No tool names declared yet. Check the project README from the listing page.
Findagent MCP 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.
Mcpproxy Go
{
"mcpServers": {
"smart-mcp-proxy-mcpproxy-go": {
"url": "http://localhost:8080/mcp/"
}
}
}
Findagent MCP
{
"mcpServers": {
"team886-findagent-mcp": {
"url": "https://mcp.findagent.cloud/mcp"
}
}
}
Frequently asked questions
Mcpproxy Go is categorized under Aggregators and uses a remote HTTP/SSE transport. Findagent MCP belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Mcpproxy Go for aggregators work and Findagent MCP 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.
Mcpproxy Go is listed as free. Auth: no auth required. Findagent MCP has no declared pricing — check the project's own site. 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 smart-mcp-proxy-mcpproxy-go and team886-findagent-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mcpproxy Go has a quality signal of 57/100 (Good) with 6 views, 0 installs and 387 GitHub stars. Findagent MCP has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.