MCP

Ask the graph from a coding agent. Running the worker yourself needs no key at all — this page is for querying https://api.3.7.79.220.sslip.io, the worker behind this console. How to point a client at it.

generate a keyread-only · 7 days

The key reads the graph. It cannot add a repository, start an ingest or spend this worker’s GitHub budget — those stay with the operator. It expires on its own, and minting is rate-limited.

connect a coding agentgenerate a key first
Claude Code verifiedclaude mcp add --transport httpapi.3.7.79.220.sslip.io/mcpone command — nothing to clone
Codexadd it as an HTTP MCP serverapi.3.7.79.220.sslip.io/mcpwherever your client keeps its MCP servers
OpenCodeadd it as an HTTP MCP serverapi.3.7.79.220.sslip.io/mcpwherever your client keeps its MCP servers
Cursoradd it as an HTTP MCP serverapi.3.7.79.220.sslip.io/mcpwherever your client keeps its MCP servers
the config — identical for every client
{
  "mcpServers": {
    "reachable": {
      "type": "http",
      "url": "https://api.3.7.79.220.sslip.io/mcp",
      "headers": {
        "Authorization": "Bearer <generate one above>"
      }
    }
  }
}
or, for Claude Code, one command
claude mcp add --transport http reachable https://api.3.7.79.220.sslip.io/mcp --header "Authorization: Bearer <generate one above>"

Nothing to clone and nothing to install — the client opens an HTTP connection to /mcp and sends your key on every call, so the graph, the driver and HydraDB all stay on this side. All twelve tools answer; eleven read and only watch_repository writes, which a read-only key cannot call.