Agent47 vs Pluggedin MCP Proxy
A side-by-side look at the Agent47 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 Agent47 for aggregators work over a hosted endpoint; 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 Agent47 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 want tools like
findJobs, comparePrice, getPlatformStats.
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 | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 5 | 136 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Agent47 | View Pluggedin MCP Proxy |
Tools & capabilities
Agent47 tools 3
findJobsDeep-search for contracts based on bounty, platform, or tags.comparePriceIntelligence on market pricing for agent services.getPlatformStatsReal-time health check of the agency network.
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.
Agent47
{
"mcpServers": {
"espadaw-agent47": {
"url": "https://agent47-production.up.railway.app/sse"
}
}
}
Pluggedin MCP Proxy
{
"mcpServers": {
"veriteknik-pluggedin-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@pluggedin/pluggedin-mcp-proxy@latest"
]
}
}
}
Frequently asked questions
Agent47 is categorized under Aggregators and uses a remote HTTP/SSE transport. Pluggedin MCP Proxy belongs to Aggregators and uses a local stdio subprocess. Pick Agent47 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.
Agent47 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 espadaw-agent47 and veriteknik-pluggedin-mcp-proxy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent47 has a quality signal of 51/100 (Good) with 1 views, 0 installs and 5 GitHub stars. Pluggedin MCP Proxy has 57/100 (Good) with 2 views, 0 installs and 136 GitHub stars.