# Crafter CMS MCP for AI Agents AI Agent Connect

> Crafter CMS MCP lets you manage your headless content directly through your AI agent. It handles GraphQL queries, writes Git-based XML content, and triggers live publishing workflows. Instead of clicking through a complex UI, you can ask your agent to find specific content nodes, audit site configurations, or push updates to your delivery engine instantly.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_P6chfyKRMZprL0PepFRAV3G74EOIIhKLJtyhWAmH/ai-agent-connect
- **Tags:** graphql, git-based, content-delivery, enterprise-cms, web-development

## Description

Managing enterprise content usually involves jumping between a CMS dashboard, a Git repository, and a delivery engine. It's a lot of context switching. This Connector changes that by letting your AI agent do the heavy lifting for you. You can talk to your agent to find specific content across your entire site or ask it to draft new pages as XML payloads. Because it handles the Git-based boundaries for you, your updates stay consistent with your development workflow. You'll find that things like checking site globals or searching through deep internal arrays for specific content nodes become much faster. It's one of the ways Vinkius makes it easier to bridge the gap between your content strategy and your actual production environment. You don't have to worry about the manual steps of migrating changes from the studio to the delivery engine anymore; the agent handles the workflow for you.

## Tools

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

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

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

### get_site_globals
Lists all attached structured rules and exports the active configuration.

### list_platform_sites
Identifies all active arrays and domains across your rented context.

### list_studio_users
Verifies the structural matching of users against specific Blueprint constraints.

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

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

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

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

## Prompt Examples

**Prompt:** 
```
List all sites in my Crafter CMS deployment.
```

**Response:** 
```
I found 3 sites in your deployment:

* **Corporate-Website** (ID: corporate)
* **Developer-Portal** (ID: docs)
* **Marketing-Landing-Pages** (ID: marketing)

Which one would you like to explore?
```

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

**Response:** 
```
Query executed! I've retrieved the titles for all articles in the 'corporate' site. Here are the results:

| Article Title |
| :--- |
| Q1 Financial Report |
| New CEO Announcement |
| Sustainability Roadmap |
```

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

**Response:** 
```
Retrieving Studio tree... I found 5 files in '/site/website/landing-pages' including:

* summer-sale.xml
* winter-promo.xml
* black-friday.xml

Each of these represents a managed XML content node.
```

## Capabilities

### Execute complex GraphQL queries
Run raw GraphQL payloads to fetch specific data from your headless delivery schema.

### Write and provision new XML content nodes
Generate new pages and content nodes directly as XML payloads in your studio.

### Trigger automated publishing workflows
Migrate changes from your Studio to the live delivery engine with one command.

### Search across all content nodes using Elasticsearch
Perform full-text searches to find specific assets or content across your entire site.

### Audit site configurations and global variables
Retrieve and inspect site globals and cloud logging tracing for specific Payload IDs.

### Navigate nested Git content hierarchies
Trace nested XML structures and extract properties from your active Git hierarchies.

## Use Cases

### 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.

### 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.

### 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.

### Generating a new landing page
A content creator describes the page content to the agent, which then uses write_studio_xml to create the new content nodes.

## Benefits

- Skip the UI by using write_studio_xml to create new pages and content nodes directly through chat.
- Speed up content discovery by using search_crafter_delivery to find specific assets across all sites.
- Simplify your deployment by using publish_crafter_content to move changes to the live engine instantly.
- Audit your environment quickly by using get_site_globals to see all active configuration rules.
- Test your data fetching logic by using execute_graphql_payload to run raw queries against your schema.
- Maintain cleaner Git histories by using get_studio_tree to trace nested XML structures safely.

## How It Works

The bottom line is you get a direct line of communication between your AI agent and your headless CMS content.

1. Subscribe to the Crafter CMS MCP and grab your Base URL and Access Token from Crafter Studio.
2. Input those credentials into your AI client to establish a secure connection.
3. Start asking your agent to perform tasks like searching for content or pushing live updates.

## Frequently Asked Questions

**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' 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.

**How do I publish changes from Studio to the live Delivery Engine?**
Use the 'publish_crafter_content' tool. 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' tool 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.