A side-by-side look at the Metatool App 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 Metatool App for aggregators work as a local process; 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 Metatool App when
You need dedicated capabilities in the Aggregators domain.
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.
Metatool App is categorized under Aggregators and uses a local stdio subprocess. Findagent MCP belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Metatool App 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.
Metatool App 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 metatool-ai-metatool-app and team886-findagent-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Metatool App has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 2,697 GitHub stars. Findagent MCP has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.