An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Crafter CMS to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage Git-based workflows and GraphQL queries through your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 01

    Wipe studio xml

    This capability removes specific App nodes from the system, which permanently deletes the associated data.

  2. 02

    List platform sites

    Get a list of all active sites currently spanning your context domains.

  3. 03

    Write studio xml

    Generate new content nodes by provisioning XML payloads directly to the system.

  4. 04

    Execute graphql payload

    This capability runs raw GraphQL payloads to identify routing spaces within the Headless Crafter Engine.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 05

    Get site config

    Use this to pull specific site configurations and trace Cloud logging via Payload IDs.

  2. 06

    Get site globals

    This capability retrieves active configuration by enumerating attached structured rules.

  3. 07

    List studio users

    Retrieve user lists to verify Blueprint constraints and permissions.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 08

    Publish crafter content

    Trigger the migration of Studio changes to the live Delivery Engine endpoint.

  2. 09

    Search crafter delivery

    Perform deep searches within internal arrays to find specific content nodes.

  3. 10

    Get studio tree

    This capability navigates the Git hierarchy to extract properties and trace nested XML structures.

Real work

What teams actually run

01

Rapid Content Creation

Generate new pages by sending XML payloads through your agent instead of manual entry.

02

GraphQL Debugging

Test complex nested queries against your delivery schema instantly.

03

Environment Auditing

Check site configurations and global variables tied to your frontend SDKs.

04

Content Discovery

Use Elasticsearch to find specific content nodes across the entire platform.

Automate a task

Put Crafter CMS to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Crafter CMS works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Crafter CMS to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

882ms average. Fast in production.

Crafter CMS is checked daily against the live service.

Daily averagePeak 1159ms
Oct 3Today
Fastest day
724ms
Slowest day
1159ms
14-day trend
Slowing+27%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Crafter CMS, so you can see the experience inside your AI.

It does not authenticate your account with Crafter CMS. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Crafter CMS Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_P6chfyKRMZprL0PepFRAV3G74EOIIhKLJtyhWAmH/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Crafter CMS capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "crafter-cms-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_P6chfyKRMZprL0PepFRAV3G74EOIIhKLJtyhWAmH/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Crafter CMS in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Crafter CMS owners hand off.

Technical professionals who manage headless content and need to interact with Git-based CMS structures without manual UI navigation.

  • 01

    Content Developers

    They use the agent to write XML content and test GraphQL queries.

  • 02

    DevOps Engineers

    They monitor site configurations and publication workflows across environments.

  • 03

    Technical Marketers

    They search for content and audit metadata using natural language.

  • 04

    Architects

    They inspect Git hierarchies and verify environment variables for frontends.

FAQ

Questions Crafter CMS owners ask.

  • 01

    How do I connect this MCP to my Crafter CMS?

    You need your Crafter CMS Base URL and an Access Token. You can find the token in Crafter Studio under Token Management.

  • 02

    Which AI clients can I use with this MCP?

    You can use any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can I publish content directly through my agent?

    Yes, you can trigger automated workflows to migrate changes from Crafter Studio to the Delivery Engine.

  • 04

    Is it possible to write new pages using this capability?

    Yes, you can provision XML payloads to generate new pages or components within the Git hierarchy.

  • 05

    Can I search for content across all my sites?

    Yes, the agent can leverage integrated Elasticsearch to perform full-text queries across all content nodes.

  • 06

    Can my agent write new content files to Crafter Studio via Git?

    Yes. Use the 'write_studio_xml' capability. Provide the site name, file path, and raw XML content. The agent will command the backend to write the physical Git boundaries, generating new content nodes or pages directly in your Studio environment.

  • 07

    How do I publish changes from Studio to the live Delivery Engine?

    Use the 'publish_crafter_content' capability. Provide the site name and the specific object path. Your agent will trigger the automated publication workflow, migrating the changes from your Git-based Studio repo to the live high-performance delivery endpoint.

  • 08

    Can I perform full-text searches across all site content?

    Absolutely. The 'search_crafter_delivery' capability leverages Crafter's Elasticsearch integration. Your agent can pull explicitly queried words spanning all nodes, returning matches based on the query logic defined in your search engine.

Explore

More in Developer Tools

Suggestions

Connect Crafter CMS to Claude, Cursor, ChatGPT & more