MCP Tool Catalog¶

G6Solver exposes 262 MCP tools. Beyond those, 212 of the 270 components own at least one MCP sub-package — 244 in total — reachable through the invoke_component dispatcher. This catalog provides three views into the tool surface. 178 sub-packages have passed UAT (40 Tier 1 + 70 Tier 2 + 68 Tier 3).

How it works¶

The MCP server presents 262 tools to the client (Claude Code, Cursor, etc.). Components that are not advertised as their own tool are reached through the invoke_component dispatcher. The tiered access system controls which tools are available based on your license plan.

Client Claude Code · Cursor · etc.

262 MCP Tools tier-gated · 15 categories

270 Components 16 capability clusters

244 MCP Sub-packages 178 UAT-passed

Gateway vs. Component Tools

The 262 advertised tools are what your MCP client sees. Components organise further operations in their own MCP sub-packages, reached via invoke_component. Use nav_inspect to explore any component's full tool set.

Browse the catalog¶

View	What it shows
By Tier	Tools grouped by plan (Free Trial / Researcher / Builder)
By Cluster	Tools grouped by capability domain (Goal & Planning, Safety, ML, etc.)
By Component	Alphabetical flat index of all components with MCP sub-packages

Quick start¶

Local stdio (recommended)¶

claude mcp add g6 --transport sse \n  --url https://g6solver.com/mcp/sse \n  --header "Authorization: Bearer YOUR_API_KEY"

SSE (cloud)¶

claude mcp add g6 --transport sse \
  --url https://g6solver.com/mcp/sse \
  --header "Authorization: Bearer YOUR_API_KEY"

Claude Code MCP config (JSON)¶

For cloud-assisted grounding only:

{
  "mcpServers": {
    "g6": {
      "transport": "sse",
      "url": "https://g6solver.com/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Authentication¶

All remote requests require a valid API key passed via the Authorization: Bearer header. Obtain your key from your g6solver.com account.

Requests without a valid key receive a 401 Unauthorized response. Requests exceeding your tier's rate limit receive a 429 Too Many Requests response with a Retry-After header.