Supercharge your AI with Crafter CMS. Manage content, structure, and deployment from your agent.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Crafter CMS manages your headless content pipeline directly from an agent. You can run raw GraphQL queries against your delivery schema, create new XML-based pages in the Git repository, inspect existing site structures, or trigger live deployments to the final content engine.
What your AI can do
Wipe studio xml
Permanently deletes specified content nodes and data records within the CMS repository.
Execute graphql payload
Runs complex GraphQL queries against the CMS engine's data schema.
Get site config
Retrieves explicit site configuration details and logging payloads.
Execute raw GraphQL payloads to pull specific data points out of the delivery schema.
Inspect the entire Git hierarchy, tracing nested XML structures and identifying active content folders.
Generate new XML payloads to create physical content nodes that fit into your repository's version control system.
Trigger the automated workflow required to move and validate content changes from the Studio environment to the live delivery endpoint.
Perform deep, full-text searches across all content nodes using integrated Elasticsearch data.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 CompatibleWaiting for input…
Crafter CMS: 10 Tools
These tools let your agent manage the full lifecycle of content—from querying data structures to writing new files in Git and pushing those files live.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Crafter CMS on VinkiusWipe Studio Xml
Permanently deletes specified content nodes and data records within the CMS repository.
Execute Graphql Payload
Runs complex GraphQL queries against the CMS engine's data schema.
Get Site Config
Retrieves explicit site configuration details and logging payloads.
Get Site Globals
Enumerates structured rules defining active global settings for the CMS.
List Platform Sites
Identifies all active sites connected across different domain contexts.
List Studio Users
Retrieves a list of users and their associated structural permissions within the Studio.
Get Studio Tree
Maps out the full content structure, identifying nested XML folders and properties.
Publish Crafter Content
Triggers an automated deployment process, moving content changes from the CMS studio...
Search Crafter Delivery
Performs a deep search across all delivered content nodes for specific keywords or...
Write Studio Xml
Generates new XML payloads to create structured pages or components in the CMS...
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Crafter CMS, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The CMS admin panel always feels like a maze of nested menus.
Today, updating content means logging into the Studio. You click through site selectors, navigate dozens of folder trees to find the right component, manually edit the XML data, and then hit 'Save' followed by another button labeled 'Publish.' If you change something minor, you might forget a step, or worse, break the entire build because you missed a required global variable.
With this MCP, that manual process shrinks down to conversation. You tell your agent what needs fixing—maybe an old component needs updating or a new article must be added. The agent handles mapping the content structure using tools like `get_studio_tree` and then provisions the XML payload for you. It's done in chat.
You get structured, verifiable deployment with `publish_crafter_content`.
Before this connector, deploying a change often meant manually hitting the 'deploy' button and hoping all dependencies were met. You’d wait for email confirmation that everything was online, unsure if any required global variable had been missed or if the content hadn't fully migrated.
Now you just ask your agent to publish. The MCP triggers an automated validation check and handles migrating changes from Studio to the high-performance Delivery Engine—all in one step. You know it worked.
What your AI can actually do with this
You connect this MCP to take control of complex enterprise content workflows without opening the Studio UI. It lets you treat your entire headless CMS setup like a database and a file system simultaneously. Need to verify which sites are active across different domains? Or maybe you just need to find all articles mentioning 'Q1 report' in deep internal arrays? You can run full-text searches across all content nodes, or execute precise GraphQL queries against the delivery schema using raw payloads.
If you write new component files, this MCP provisions high-availability XML payloads directly into your Git boundary and even pushes those changes live to the Delivery Engine with a single command. With Vinkius hosting this connector, you get one place from which any AI agent can manage structure, content generation, and publishing across your whole platform.
019d757d-e0e3-71e4-ad90-3a8eea6bc35d Here's how it actually works
The bottom line is you manage complex CMS tasks and deployments using conversation, not through clicking menus in a web interface.
Subscribe to this MCP and provide your Crafter CMS Base URL and Access Token from the Studio.
Your agent uses natural language instructions, like 'List all sites' or 'Execute query for articles in site X,' to call specific tools on this connector.
The MCP runs the required operation—whether that’s fetching a list of users, running GraphQL, or publishing content—and returns structured data directly to your AI client.
Who is this actually for?
This MCP is for the developers and engineers who hate having to context-switch between their IDE, the documentation, and multiple administration dashboards. It targets anyone whose job involves validating content flow from code into the live website.
Uses it to test GraphQL queries or write XML content nodes directly against the CMS without ever opening the Studio interface.
Monitors site configurations and verifies that publication workflows run correctly across development, staging, and production environments.
Searches for specific content metadata or audits global sites using natural language prompts to validate campaign coverage.
What Changes When You Connect
Stop relying on manual UI navigation. You can now use get_studio_tree to inspect the full Git hierarchy of a site without opening any web dashboard.
Cut down deployment time by using publish_crafter_content. This tool automatically runs validation checks and pushes content changes live, bypassing manual workflow triggers.
Need to know what data is available? Use execute_graphql_payload to run raw queries against the delivery schema. You get precise results without needing a developer console.
Quickly audit your setup by using list_platform_sites or get_site_globals. These tools let you see which sites are connected and what global rules they use, all from chat.
Searching for old content is easy. search_crafter_delivery performs deep internal array searches that go far beyond standard CMS search boxes.
See it in action
The Site Audit
A DevOps engineer needs to verify if all 14 regional landing pages are configured correctly. Instead of logging into 14 different sites, they ask their agent to run list_platform_sites first, then use get_site_globals on each site ID to check for missing required variables.
The Content Update
A technical marketer needs to add a new 'Sustainability' section. They don't want to mess with the Studio UI, so they ask their agent to use write_studio_xml to provision the XML payload and then immediately call publish_crafter_content to deploy it live.
The Data Pull
A content developer needs a list of all article titles related to 'Q1 financial report' across three specific sites. They use their agent to execute a targeted GraphQL payload, retrieving only the needed title fields and nothing else.
The Cleanup
An architect finds several outdated draft components in the CMS that must be removed before deployment. The agent uses get_studio_tree to map the location, and then executes wipe_studio_xml to safely delete the identified nodes.
The honest tradeoffs
Treating it like a simple database query
Asking the agent for 'all content' or running a basic keyword search. This misses the structural context of the CMS.
If you need full-text search, use search_crafter_delivery. If you need to know what structure is available before querying, run get_studio_tree first.
Assuming local changes are live
Writing content via the agent (write_studio_xml) and assuming it appears on the website instantly.
After writing or modifying any content, you must explicitly run publish_crafter_content to trigger the necessary workflow that moves data from the CMS into the live delivery engine.
Trying to find all properties via GraphQL
Writing a massive, complex query trying to pull every single property and variable across all sites at once. This often hits schema limits.
First, run get_site_globals or get_site_config to get the defined list of properties. Then build your GraphQL payload using only those known fields.
When It Fits, When It Doesn't
Use this MCP if your workflow requires managing content across multiple stages: from structured repository definition (XML writing/Studio Tree) through data querying (GraphQL) and finally to live deployment (Publishing). Don't use it if you only need simple, isolated tasks—for example, just reading a single user list is easier with a generic directory tool. If your goal is purely content creation without worrying about the underlying structure or version control, an external editor might be simpler. But if you are working in a professional headless environment where every change must pass through Git and a defined publishing pipeline, this MCP is essential because it controls that entire lifecycle.
Questions you might have
How do I list all my active sites using list_platform_sites? +
You ask your agent to run list_platform_sites. It returns a precise array of every site connected across the CMS, giving you their unique IDs and context domains.
Can I create new content pages with write_studio_xml? +
Yes. Running write_studio_xml generates brand new XML payloads that fit into your Git boundary. This is how you provision a page or component without opening the Studio.
What's the difference between GraphQL and searching for content? +
Use execute_graphql_payload when you need very specific, structured data (like only titles and dates). Use search_crafter_delivery when you just want to find articles containing a keyword across all content nodes.
Do I have to manually push changes after using get_site_config? +
No. If your goal is deployment, always follow up configuration reads with publish_crafter_content. This ensures the system validates and pushes those settings live.
What does `list_studio_users` show me regarding content access and permissions? +
It retrieves the exact structural details for all studio users. You see which Blueprint constraints are applied, helping you audit who can access specific content nodes.
When I use `get_studio_tree`, what data structure am I actually extracting? +
You get a safe structural extraction of properties that drive active Git hierarchies. This allows you to trace and visualize nested XML structures within your content repository.
If I run `wipe_studio_xml`, what is the scope of data removal, and is it recoverable? +
No, this action irreversibly vaporizes explicit App nodes. It drops live database bytes from the CMS; use it only when you are sure content must be completely purged.
What kind of variables can I retrieve using `get_site_globals`? +
It enumerates all structured rules that export active configuration data. You get access to environment variables tied directly to your frontend SDKs, useful for site auditing.
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.
We've already built the connector for Crafter CMS. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.