Vinkius
Crafter CMS

Supercharge your AI with Crafter CMS. Manage content, structure, and deployment from your agent.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Crafter CMS MCP on Cursor AI Code Editor MCP ClientCrafter CMS MCP on Claude Desktop App MCP IntegrationCrafter CMS MCP on OpenAI Agents SDK MCP CompatibleCrafter CMS MCP on Visual Studio Code MCP Extension ClientCrafter CMS MCP on GitHub Copilot AI Agent MCP IntegrationCrafter CMS MCP on Google Gemini AI MCP IntegrationCrafter CMS MCP on Lovable AI Development MCP ClientCrafter CMS MCP on Mistral AI Agents MCP CompatibleCrafter CMS MCP on Amazon AWS Bedrock MCP Support

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.

+ 7 more capabilities included
Run data queries

Execute raw GraphQL payloads to pull specific data points out of the delivery schema.

Map site structure

Inspect the entire Git hierarchy, tracing nested XML structures and identifying active content folders.

Write new pages

Generate new XML payloads to create physical content nodes that fit into your repository's version control system.

Publish changes

Trigger the automated workflow required to move and validate content changes from the Studio environment to the live delivery endpoint.

Search all content

Perform deep, full-text searches across all content nodes using integrated Elasticsearch data.

Compatible AI Apps

OAuth 2.0 Compatible
Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
Vinkius runs on Zendesk Zendesk
+ any other MCP app
Included with Plan

Waiting for input…

AI Agent

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 Vinkius

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.

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.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Crafter CMS integration is available immediately — no restart needed.

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
Start building

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
Crafter CMS MCP server cover

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

Your data is protected. See how we built it.

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.

Built · Hosted · Managed by Vinkius Crafter CMS MCP - Headless Content & Query Management
Server ID 019d757d-e0e3-71e4-ad90-3a8eea6bc35d
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

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.

Built & Managed by Vinkius 30s setup 10 tools

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 runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

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.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.