MCP Server Catalog

This map shows all 8 MCP servers registered in .mcp.json and how they connect to Claude Code tools. Read this when debugging a missing MCP tool, understanding which server provides a capability, or planning a new MCP integration.

Diagram

graph TD
    CC["Claude Code\n(this session)"]

    subgraph internal["Internal / VPS-hosted"]
        OT["openclaw-tools\n11 tools: memory, supabase,\nscripts, gateway logs, portkey"]
        AO["aurora-orchestrator\n20 tools: HubSpot, Slack,\nSMS, DocuSign, memory"]
    end

    subgraph external["External / npx-launched"]
        C7["context7\nLibrary docs lookup"]
        PW["playwright\nHeadless browser / QA"]
        SIO["shortio\nURL shortener ops"]
        MG["21st-magic\nUI component builder"]
        PX["perplexity\nWeb research + reasoning"]
    end

    subgraph broken["Broken / Inactive"]
        FG["figma\nDesign file access\n(broken — Phase 11.3a)"]
    end

    CC -->|"Python server.py"| OT
    CC -->|"Node aurora-mcp-server.js"| AO
    CC -->|"npx @upstash/context7-mcp"| C7
    CC -->|"npx playwright-mcp"| PW
    CC -->|"npx mcp-remote short.io"| SIO
    CC -->|"npx @21st-dev/magic"| MG
    CC -->|"npx @perplexity-ai/mcp-server"| PX
    CC -.->|"npx @anthropic/mcp-figma (broken)"| FG

How to read this

• openclaw-tools is the primary operational server — it exposes memory search/save, Supabase queries, script execution, gateway logs, Portkey status, HubSpot lookup. Hosted in /home/opsadmin/.openclaw/tools/openclaw-mcp/.
• aurora-orchestrator is Aurora’s MCP layer — it adds 20 tools for HubSpot deal creation/update, Slack escalation, SMS (OpenPhone thread history), DocuSign draft, and cross-agent memory. Hosted in /home/opsadmin/.openclaw/tools/quo-thread-orchestrator/aurora-mcp-server.js.
• context7 / playwright / shortio / 21st-magic / perplexity are spawned on-demand via npx. They require internet access and may lag on first call.
• figma is registered but broken (Phase 11.3a fix pending). Do not rely on it.
• No keys, tokens, or credentials are shown here — these are server names only. Actual credentials live in master.env and .mcp.json env blocks (not shown).

Related

• agents-tier-structure — Aurora and other agents consume these MCP tools
• request-lifecycle — aurora-orchestrator tools fire within agent execution
• governance-gates-network — G-NO-PLAINTEXT-CREDS applies to .mcp.json env blocks

See also

• CLAUDE.md — “MCP servers active (8)” line for current status and tool counts
• .mcp.json at /home/opsadmin/.mcp.json — server registration (keys redacted in this map)
• ARCHITECTURE.md — Section 5 for MCP integration patterns