Skip to content
Vinkius

Crafter CMS Connector for AI agents.

10 live capabilities

Manage headless CMS content and Git-based workflows with natural language.

Live agent request Crafter CMS / Connector

Waiting for input…

AI Agent

Why people use Crafter CMS

Crafter CMS Content Management for Headless Workflows

This Connector changes that by putting the CMS in your chat window. You can ask your agent to find content, write new pages, or audit configurations without ever opening a browser tab. You get a direct path from your idea to a published live update.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a direct line of communication between your AI agent and your headless CMS content.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Searching for content across dozens of sites

    Instead of clicking through every site, a developer asks the agent to use search_crafter_delivery to find content and list results in a table.

  2. Real-world use case 02

    Updating global configuration variables

    A marketer asks the agent to use get_site_globals to find the current rule and then requests a specific change to the value.

  3. Real-world use case 03

    Verifying site config before a launch

    A DevOps engineer uses get_site_config to pull all Cloud logging tracing and Payload IDs into a summary for review.

Complete set · 10capabilities

The complete Crafter CMS capability set.

These are the exact actions your AI can choose when you ask it to work with Crafter CMS.

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 01 Capability

    Wipe studio xml

    Permanently deletes specific App nodes and drops the associated database bytes.

  2. 02 Capability

    Execute graphql payload

    Runs raw GraphQL queries to find specific data within the Headless Crafter Engine.

  3. 03 Capability

    Get site config

    Retrieves site configurations and cloud logging tracing for specific Payload IDs.

  4. 04 Capability

    Get site globals

    Lists all attached structured rules and exports the active configuration.

Capability set02 / 03

05—07

3 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 05 Capability

    List platform sites

    Identifies all active arrays and domains across your rented context.

  2. 06 Capability

    List studio users

    Verifies the structural matching of users against specific Blueprint constraints.

  3. 07 Capability

    Get studio tree

    Extracts properties from active Git hierarchies and identifies nested XML folders.

Capability set03 / 03

08—10

3 capabilities in this set.

Part of 10 available through Crafter CMS.

  1. 08 Capability

    Publish crafter content

    Migrates Studio changes to the live delivery engine and triggers a validation check.

  2. 09 Capability

    Search crafter delivery

    Performs full-text searches across internal arrays to find specific content or pictures.

  3. 10 Capability

    Write studio xml

    Generates new pages and provisions highly-available XML content nodes in the studio.

Set up in minutes

One URL. Then ask Crafter CMS to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Crafter CMS from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_P6chfyKRMZprL0PepFRAV3G74EOIIhKLJtyhWAmH/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Crafter CMS, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Crafter CMS for the conversation.

Where the request belongs

Work Crafter CMS can move forward.

Built around the request

This is for content developers and DevOps engineers who are tired of the click-fatigue associated with large-scale headless CMS platforms. It's for anyone who needs to manage content at scale without manually navigating nested menus.

01

Content Developer

Writing XML content nodes and testing GraphQL queries without leaving their editor.

02

DevOps Engineer

Monitoring site configurations and verifying publication workflows across different environments.

03

Technical Marketer

Searching for content across global sites to audit metadata and find specific assets.

04

Solutions Architect

Inspecting Git hierarchies and verifying environment variables for headless frontends.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
CrafterCMS logo
01 12 capabilities

CrafterCMS

Manage and query content from CrafterCMS. fetch pages, components, and trees, execute GraphQL/OpenSearch queries, and manage engine cache directly from your AI agent.

View Connector
ContentStack (Management) logo
02 10 capabilities

ContentStack (Management)

Grant your AI agent read-write capabilities using ContentStack CMA. Update, publish, and manage contents, schemas, and environments from chat.

View Connector
Contentful logo
03 12 capabilities

Contentful

Equip your AI agent to fetch, create, and manage digital content effortlessly using Contentful's headless architecture.

View Connector
Builder logo
04 10 capabilities

Builder

Automate Builder.io headless CMS workflows. generate content blocks, update models, and orchestrate visual components directly from any AI agent.

View Connector
Builder.io logo
05 10 capabilities

Builder.io

Manage your visual CMS via Builder.io. track content entries, models, and symbols directly from any AI agent.

View Connector
Payload CMS logo
06 11 capabilities

Payload CMS

Manage your Payload CMS instance. query collections, inspect documents, and manage content directly from your AI agent.

View Connector

Bring your own AI

Change the model, client or framework. Keep Crafter CMS connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Crafter CMS.

The practical details behind the request, access and result.

Can the Crafter CMS MCP write new pages for me?

Yes, you can ask your agent to generate new pages or content nodes. It uses the CMS's native XML structure to create the content exactly where you need it.

Does this work with Git-based content workflows?

Yes, it's designed specifically to navigate and write to Git-based XML structures. Your agent can trace nested folders and manage the Git boundaries for you.

Can I use it to search for content across multiple sites?

You can search across all content nodes and internal arrays. It's a great way to find specific assets or data without having to browse each site individually.

How does it handle publishing to the delivery engine?

The Connector triggers the automated workflows required to migrate your Studio changes to the live delivery engine. It even runs a validation check during the process.

Can I audit my site configurations using this?

Yes, you can ask your agent to pull your site globals or specific site configurations. It's perfect for checking variables and rules across different environments.

Is this safe for enterprise content?

Yes, it connects securely to your Crafter CMS instance using your provided access token. It identifies precise arrays and lists users securely based on your permissions.

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.

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.

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.

One connection away

Give your agent a direct line to Crafter CMS.

Connect Crafter CMS once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available