Skip to content
OpenClaw Team Docs

MCP Server Catalog

MCP (Model Context Protocol) lets Claude talk to external systems through a standardized protocol. 24 servers registered, 14 currently connected. Grouped by what they do.

Analytics & Cost

ccusage

(per-model costs)

dune ✓

(crypto data)

Internal Orchestration

openclaw-tools ✓

(11 tools: memory_search,

workspace_query, gateway_logs...)

aurora-orchestrator ✓

(20 tools)

Tools & Build

playwright ✓

firecrawl

21st-magic ✓

figma ✗ broken

shortio ✓

Comms & CRM

slack

discord

notion

claude_ai_Gmail

claude_ai_Google_Calendar

claude_ai_Docusign

claude_ai_Zoom

claude_ai_Quo

(OpenPhone)

Data Access

supabase ✓

hubspot ✗ token stub

airtable

github ✓

memory

(graph store)

LLM Augmentation

gemma

(Gemma 4 via OpenRouter)

sequential-thinking

perplexity

(web grounding)

context7

(library docs)

Claude Code

CLI

How MCP fits

Section titled “How MCP fits”

When Claude needs to talk to an external system, an MCP server is the standardized adapter. Each server:

  • Runs as a child process spawned by Claude Code (stdio) or an HTTP server (SSE)
  • Exposes typed tools (e.g. slack.slack_send_message, supabase.execute_sql) that Claude can call
  • Returns structured results

The internal orchestration servers (openclaw-tools, aurora-orchestrator) are the most-used — they wrap memory search, workspace queries, gateway logs, and 20+ Aurora-specific operations.

Live state — verify connected servers anytime with: claude mcp list. Configuration: ~/.mcp.json.