MCP Tooling

The technical reference for all tools exposed by the Axolot MCP servers. This is what your AI uses to talk to your CMS.

Axolot exposes a rich set of tools via the Model Context Protocol. When you connect your AI assistant (Cursor, Claude, etc.), it gains access to these functions to understand and manipulate your site.

Authentication & Context

cms_auth_status

Checks if the session is authenticated and identifies the active site.

cms_auth_login

Initiates the secure handshake to connect your local AI to the Axolot cloud.

cms_switch_site

Changes the target Site ID for all subsequent operations.

Core CMS Operations

These tools allow the AI to read your site's structure and design system.

getDesignTokens: Returns the brand palette, typography, and spacing. The AI uses this to ensure new components match your brand.
getPages: Lists all pages and their existing slots. Use this for site-wide audits.
getMedia: Accesses the digital asset library, including AI-generated alt text and WebP variants.
createSlot: Registers a new editable area. Usually called by the AI after it generates a new component for you.

Module Intelligence

Each module (Blog, Shop, etc.) has its own set of specialized tools.

getModuleCapabilities: Returns the technical blueprint (data structure and recommended components) for a module.
getBlogPosts / getProducts: Fetch raw content from the modules to build dynamic lists.
createBlogPost / createProduct: Directly inject new content into the CMS database.

AI-Ready Context

Tool Specification Example

// Definition of createSlot tool
{
  name: "createSlot",
  parameters: {
    pageId: string,
    key: string,
    type: "text" | "image" | ...,
    aiHint: string
  }
}

AI Insight

"When I see a module like 'blog', I first call getModuleCapabilities('blog') to understand the JSON schema before I attempt to render any list or single-post view."

Logic & constraints

Use Slot keys as primary keys.

Do not hardcode content strings.

Respect TypeScript interfaces.