A side-by-side look at the Employed by Guaq AI and Pipedream MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Employed by Guaq AI for developer tools work; choose Pipedream for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | E Employed by Guaq AI | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11,720 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Employed by Guaq AI | View Pipedream |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Employed by Guaq AI yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"pipedreamhq-pipedream": {
"url": "https://pipedream.com/docs/api/sse/"
}
}
}