Agent MCP Hub vs Gossipcat
A side-by-side look at the Agent MCP Hub and Gossipcat MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent MCP Hub for coding agents work as a local process; choose Gossipcat for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent MCP Hub when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_AGENTS, MCP_CONFIRM. - You want tools like
codex, cursor, opencode.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 52/100 · Good | 35/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MCP_AGENTSMCP_CONFIRM | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 41 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Agent MCP Hub | View Gossipcat |
Tools & capabilities
Agent MCP Hub tools 8
codexDelegate a prompt to `codex exec` (prompt piped via stdin)cursorDelegate a prompt to `cursor-agent -p` (prompt piped via stdin)opencodeDelegate a prompt to `opencode runclaudeDelegate a prompt to the Claude Code CLI (prompt piped via stdin)agyDelegate a prompt to Google Antigravity (`agy --print=…`, prompt passed as a flag value)run_allSame prompt to all agents in parallel, results side by sidelist_agentsWhich agent CLIs are installed and on PATHpingHealth check
Gossipcat 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.
Agent MCP Hub
{
"mcpServers": {
"agent-mcp-hub": {
"command": "npx",
"args": [
"-y",
"re-resolves"
],
"env": {
"MCP_AGENTS": "YOUR_MCP_AGENTS_HERE",
"MCP_CONFIRM": "YOUR_MCP_CONFIRM_HERE"
}
}
}
}
Gossipcat
No confirmed install command for Gossipcat yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Agent MCP Hub is categorized under Coding Agents and uses a local stdio subprocess. Gossipcat belongs to Coding Agents and uses an install path we have not confirmed yet. Pick Agent MCP Hub for coding agents work and Gossipcat for coding agents.
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. Gossipcat has no confirmed install command yet — follow its own setup instructions.
Agent MCP Hub has no declared pricing — check the project's own site. Gossipcat 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 agent-mcp-hub and gossipcat as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent MCP Hub has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Gossipcat has 35/100 (Fair) with 0 views, 0 installs and 41 GitHub stars.