MCP For Claude Marketplace
Crafter CMS

Crafter CMS MCP Connector for Claude

A+

Manage headless content via Crafter CMS — execute GraphQL queries, write Git-based XML content, and publish to delivery engines directly from any AI agent.

10 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

Connect your Crafter CMS instance to any AI agent and take full control of your enterprise headless CMS and Git-based content workflows through natural conversation.

What you can do

  • GraphQL Orchestration — Execute absolute explicit nesting requirements against the delivery schema using raw GraphQL payloads natively
  • Studio Tree Navigation — Perform structural extraction of properties driving active Git hierarchies and trace nested XML structures safely
  • Git-Based Content Writing — Provision highly-available XML payloads to write physical Git boundaries and generate new pages or components
  • Live Publishing — Trigger automated workflow bounds to migrate changes from Crafter Studio onto the high-performance Delivery Engine
  • Elasticsearch Discovery — Inspect deep internal arrays leveraging integrated Elasticsearch to perform full-text queries spanning all content nodes
  • Platform Governance — Identify precise active arrays spanning rented Context domains and list configured sites and studio users securely
  • Environment Audit — Discovered disconnected physical limits fetching site configurations and global variables tied to your frontend SDKs

How it works

  1. Subscribe to this server
  2. Enter your Crafter CMS Base URL and Access Token (found in Crafter Studio > Token Management)
  3. Start managing your Git-based content from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Content Developers — test GraphQL queries and write XML content nodes without opening the Studio interface
  • DevOps Engineers — monitor site configurations and verify publication workflows across environments
  • Technical Marketers — search for content across global sites and audit metadata using natural language
  • Architects — inspect Git hierarchies and verify environment variables tied to headless frontends
graphqlgit-basedcontent-deliveryenterprise-cmsweb-development

10 tools expose this connector's capabilities to your AI agent.

wipe_studio_xml

Irreversibly vaporize explicit App nodes dropping live Database bytes

list_platform_sites

Identify precise active arrays spanning rented Context domains

write_studio_xml

json` generating pages. Provision a highly-available XML Payload generating new Content nodes

execute_graphql_payload

Identify bounded routing spaces inside the Headless Crafter Engine

get_site_config

json` isolating GraphQL URL limits. Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly

get_site_globals

Enumerate explicitly attached structured rules exporting active Configuration

list_studio_users

Retrieve the exact structural matching verifying Blueprint constraints

publish_crafter_content

json` executing workflow bounds migrating a Studio change onto the Delivery Engine live endpoint. Dispatch an automated validation check routing explicit Deployments

search_crafter_delivery

Inspect deep internal arrays mitigating specific Picture constraints

get_studio_tree

json` identifying exact folders tracing nested XML structures safely. Perform structural extraction of properties driving active Git hierarchies

See how to talk to your AI agent using Crafter CMS.

List all sites in my Crafter CMS deployment

I found 3 sites: 'Corporate-Website' (ID: corporate), 'Developer-Portal' (ID: docs), and 'Marketing-Landing-Pages' (ID: marketing). Which one would you like to explore?

Execute GraphQL query on site 'corporate': '{ articles { items { title_s } } }'

Query executed! I've retrieved the titles for all articles in the 'corporate' site. Results include 'Q1 Financial Report', 'New CEO Announcement', and 'Sustainability Roadmap'.

Show me the Git tree for site 'marketing' at path '/site/website/landing-pages'

Retrieving Studio tree... I found 5 files in '/site/website/landing-pages' including 'summer-sale.xml', 'winter-promo.xml', and 'black-friday.xml'. Each represents a managed XML content node.

Yes. Use the 'write_studio_xml' tool. 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.

Related Connectors

Frontify

Frontify MCP

10 tools Official

Manage digital assets and brand guidelines via Frontify — list workspace projects and assets, handle metadata, audit brand portals, and manage users directly from any AI agent.

A+ View details →
DatoCMS

DatoCMS MCP

10 tools Official

Manage headless content via DatoCMS — execute GraphQL queries, handle record CRUD, manage content models, and audit media uploads directly from any AI agent.

A+ View details →
Cockpit (Self-hosted Headless CMS API)

Cockpit (Self-hosted Headless CMS API) MCP

17 tools Official

Manage your self-hosted Cockpit CMS content, assets, and menus directly from any AI agent.

A+ View details →
Kontent.ai (Enterprise Headless CMS)

Kontent.ai (Enterprise Headless CMS) MCP

10 tools Official

Manage enterprise content via Kontent.ai — create items, publish language variants, and audit content types.

A+ View details →