hub / connect

Connect

One URL stops your agent hallucinating library usage: verify current APIs, pull real usage examples, and diff versions across every graph in the hub — no auth, no key, 60 seconds.

MCPhttps://www.codehub.bot/mcp

Run in any terminal:

claude mcp add --transport http codehub https://www.codehub.bot/mcp

That's it — the tools are available in every session.

tools: verify_api · usage_examples · api_changes · whats_new · find_repos · similar_repos · dependents · search · symbol_context · load_source · read_file · grep · callers · implementers · impact · overview · list_symbols

Open Settings → Connectors (web or desktop)

Click Add custom connector and paste:

https://www.codehub.bot/mcp

Enable codehub in the tools menu of any chat.

Create .vscode/mcp.json in your workspace (Copilot agent mode):

{
  "servers": {
    "codehub": { "type": "http", "url": "https://www.codehub.bot/mcp" }
  }
}

Reload — the codehub tools appear in agent mode.

Add to ~/.cursor/mcp.json (or per-project .cursor/mcp.json):

{
  "mcpServers": {
    "codehub": { "url": "https://www.codehub.bot/mcp" }
  }
}

Settings → MCP → edit mcp_config.json:

{
  "mcpServers": {
    "codehub": { "serverUrl": "https://www.codehub.bot/mcp" }
  }
}

Hermes, OpenClaw, Zed, Cline, Continue — any client that speaks MCP streamable HTTP: add a server with this URL. No auth, no key.

https://www.codehub.bot/mcp

Most clients take it as { "url": … } or { "serverUrl": … } in their MCP config.

Then try asking

“verify against CodeHub what fastmcp's tool decorator actually takes these days”

“show me real production usage of langgraph's StateGraph before I write mine”

“my build broke after upgrading this library — ask CodeHub what changed in its API”

“what's the blast radius if dskit's InjectOrgID changes?”

Make it a habit one rule in your agent's config makes every session grounded

Add this to your CLAUDE.md, .cursorrules, or system prompt — the agent will verify library APIs against the live index before writing integration code:

Before writing code that imports or calls a third-party library, verify the API against CodeHub (verify_api / usage_examples) — training-data knowledge of library APIs is often stale. After a dependency upgrade breaks the build, call api_changes first.