Metatool App vs Pluggedin MCP Proxy
A side-by-side look at the Metatool App and Pluggedin MCP Proxy 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 Pluggedin MCP Proxy for aggregators as a local process. 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.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Pluggedin MCP Proxy when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 45/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,697 | 136 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Metatool App | View Pluggedin MCP Proxy |
Tools & capabilities
Metatool App tools
No tool names declared yet. Check the project README from the listing page.
Pluggedin MCP Proxy 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
{
"mcpServers": {
"metatool-ai-metatool-app": {
"command": "uvx",
"args": [
"mcp-hn"
]
}
}
}
Pluggedin MCP Proxy
{
"mcpServers": {
"veriteknik-pluggedin-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@pluggedin/pluggedin-mcp-proxy@latest"
]
}
}
}
Frequently asked questions
Metatool App is categorized under Aggregators and uses a local stdio subprocess. Pluggedin MCP Proxy belongs to Aggregators and uses a local stdio subprocess. Pick Metatool App for aggregators work and Pluggedin MCP Proxy 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. Pluggedin MCP Proxy is listed as free. Auth: oauth 2.0. 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 veriteknik-pluggedin-mcp-proxy 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. Pluggedin MCP Proxy has 57/100 (Good) with 2 views, 0 installs and 136 GitHub stars.