How to Use the Crafter CMS MCP in Claude

Q: How do I connect the Crafter CMS MCP Server to Claude Desktop?

Open your claudedesktopconfig.json file and add the server configuration under the mcpServers block with your Vinkius token. Restart Claude Desktop, and you will see the tools active via the hammer icon in your chat window.

Q: Can I query GraphQL delivery endpoints using Crafter CMS and Claude Desktop?

Yes. The executegraphqlpayload tool lets Claude Desktop query the headless engine directly. You can test payloads and inspect responses without leaving the chat interface.

Q: What happens when I publish content using Crafter CMS in Claude Desktop?

The publishcraftercontent tool executes a workflow migration that pushes your Git-based Studio changes to the live delivery engine. Claude Desktop tracks the deployment status and reports back once the endpoint updates.

Q: Can I manage multiple site domains with this integration?

Yes, the listplatformsites tool retrieves all active domains in your Crafter instance. You can switch contexts and target different sites by telling Claude Desktop which domain to query.

Manage your headless Crafter CMS engine directly inside Claude Desktop with native local tool calls.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Crafter CMS MCP to Claude Desktop

Create your Vinkius account to connect Crafter CMS to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Crafter CMS with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write and wipe XML nodes in Claude Desktop

`write_studio_xml` gives your AI client direct write access to generate new XML content nodes inside your Crafter CMS Git repository. This tool lets you create pages and structural definitions without leaving your desktop chat interface. It converts your natural language requirements into formatted XML schemas that fit your site's existing architecture. When you need to clean up old experiments, Claude Desktop uses `wipe_studio_xml` to remove specific App nodes. This operation drops live database bytes directly, so you must confirm the target before execution. The `get_studio_tree` tool maps the nested folder structure first to verify you are targeting the correct path.

Query headless delivery engines via MCP Server

`execute_graphql_payload` executes raw queries directly against the Headless Crafter Engine to test your content API. You feed Claude Desktop a schema requirement, and the MCP Server routes the payload to find active routing spaces. This eliminates the need to jump back and forth between your terminal and a separate GraphQL playground. To inspect specific content constraints, Claude uses `search_crafter_delivery` to scan deep internal arrays. If you run into endpoint limits, `get_site_config` pulls the exact JSON configuration to pinpoint your GraphQL URL boundaries. You get instant feedback on what your front-end will receive.

Track sites and publish changes from Claude Desktop

`list_platform_sites` identifies the precise active domains rented across your Crafter CMS platform setup. Claude Desktop pulls this list to verify which environment you are targeting before pushing updates. You can also run `get_site_globals` to extract the structured routing rules and active configurations. Once your edits look correct, `publish_crafter_content` migrates your Studio changes onto the live Delivery Engine endpoint. This tool handles the workflow bounds so you don't have to log into the Crafter Studio UI to click publish. Your content moves from Git to live delivery in one conversational turn.

Setup guide

Set up Crafter CMS MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Crafter CMS MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Crafter CMS MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under crafter-cms-mcp.

json

{
  "mcpServers": {
    "crafter-cms-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Crafter CMS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Crafter CMS now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Crafter CMS MCP in Claude Desktop

Open your `claude_desktop_config.json` file and add the server configuration under the `mcpServers` block with your Vinkius token. Restart Claude Desktop, and you will see the tools active via the hammer icon in your chat window.

Yes. The `execute_graphql_payload` tool lets Claude Desktop query the headless engine directly. You can test payloads and inspect responses without leaving the chat interface.

The `publish_crafter_content` tool executes a workflow migration that pushes your Git-based Studio changes to the live delivery engine. Claude Desktop tracks the deployment status and reports back once the endpoint updates.

Yes, the `list_platform_sites` tool retrieves all active domains in your Crafter instance. You can switch contexts and target different sites by telling Claude Desktop which domain to query.

Vinkius runs this MCP Server in an isolated, ephemeral V8 sandbox. Your Crafter CMS XML configurations, user lists, and GraphQL payloads are never stored on Vinkius servers, keeping your Git credentials completely private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript