Skip to main content
AI assistants like Claude are most useful when they can act, not just answer. The Model Context Protocol (MCP) is the wire format that lets them — the assistant connects to a local server process, asks “what tools do you have?”, and starts calling them. gavAI ships two MCP servers so any MCP-aware client can read and edit pages, rotate keys, fetch logs, and otherwise drive the platform from a chat window. By the end of this page you will know what MCP is, why we ship two servers instead of one, and which one to point at your workspace.

​
What MCP is, in 30 seconds

MCP is a small JSON-RPC protocol that an AI client (Claude Desktop, Cursor, Windsurf) speaks to a tool-providing server. The server runs as a local subprocess, advertises a list of tools, and the client invokes them with structured arguments. Every gavAI MCP tool call ends in an HTTP request to gavAI’s API — the server is a translation layer, not a separate runtime. Two properties matter:
  • The server holds the credential, not the client. Claude never sees your API key or session token.
  • Every call has the same authorization as a direct API call. The MCP server doesn’t widen scopes — if your token can’t publish a workspace, neither can Claude.

​
The two servers and how they differ

gavAI ships two MCP servers because they serve two different jobs and want different credentials. The Builder MCP is hand-curated: 14 tools that map to the operations a page editor actually performs. It is bundled with the gavAI CLI, so it inherits your CLI session and refreshes the token when it expires. Reach for it when an AI assistant should behave like a copilot inside the Builder. The Public API MCP is generated from the OpenAPI spec. Every endpoint tagged x-mcp-tool: true becomes a tool — including operations the Builder doesn’t expose (rotate a key, mint a domain, query logs). It authenticates with a workspace API key you mint in the console. Reach for it when the AI is doing platform-wide work that goes beyond editing pages.

​
Which to use

You can run both at the same time — they register under different names in the client config, and the AI picks whichever exposes the tool it needs. See Set up Claude Desktop for the side-by-side config.

​
What you should know before connecting one

​
Where to next