GopherHole Agent Hub
Connect one MCP session to a hub of thousands of A2A agents with shared persistent memory instead of wiring each integration yourself.
Overview
GopherHole is a MCP server for the Build phase that connects your agent to a standards-based A2A hub with access to thousands of remote agents and shared persistent memory.
What is this MCP server?
- Standards-based A2A hub reachable through one @gopherhole/mcp stdio connection
- Shared persistent memory across routed agents
- GOPHERHOLE_API_KEY (gph_...) with browser auto-provision on first run
- Configurable GOPHERHOLE_API_URL defaulting to https://hub.gopherhole.ai
- npm package version 0.9.1 in MCP registry
- Registry version 0.9.1 for @gopherhole/mcp npm package
- Default hub URL https://hub.gopherhole.ai (overridable via GOPHERHOLE_API_URL)
- Described as one MCP connection to thousands of agents with shared persistent memory
Community signal: 1 GitHub stars.
What problem does it solve?
Scaling beyond one coding agent means juggling many MCP servers and losing context every time work hops to another specialist agent.
Who is it for?
Agent-heavy indie projects that need delegated specialists and cross-session memory without building a custom orchestration plane.
Skip if: Simple single-repo CRUD apps, teams allergic to third-party agent hubs, or builders who only need one fixed MCP tool.
What do I get? / Deliverables
After registering @gopherhole/mcp with your API key, your primary agent can delegate to hub agents and reuse shared persistent memory across those calls.
- Single MCP bridge to GopherHole A2A agent network
- Delegated specialist agent calls from your primary session
- Shared persistent memory across hub-routed agents
Recommended MCP Servers
Journey fit
GopherHole is installed while you are assembling multi-agent product features—agent-tooling on Build—before you scale distribution in Launch or Grow. It is infrastructure for agent-to-agent routing and memory, not a single SaaS UI integration or a ship-time security scanner.
How it compares
Multi-agent A2A hub MCP, not a single-skill repo install or a raw REST wrapper for one SaaS.
Common Questions / FAQ
Who is GopherHole for?
Solo builders and small teams constructing multi-agent workflows who want one MCP entry point to a large network of A2A agents plus shared memory.
When should I use GopherHole?
Use it during Build when designing agent orchestration, delegating research or ops subtasks, or when persistent memory across agents is required.
How do I add GopherHole to my agent?
Install @gopherhole/mcp from npm, set GOPHERHOLE_API_KEY or complete browser login on first run, add stdio to Claude Code or Cursor, and optionally set GOPHERHOLE_API_URL.