CrafterCMS MCP for AI. Query and manage headless content structure directly.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
CrafterCMS MCP connects your agent directly to a headless content repository. Fetch structured page data, execute complex GraphQL queries against your schema, or run raw OpenSearch searches using just natural language prompts.
What AI agents can do with CrafterCMS Automation
Clear cache
Clears the Crafter Engine cache, requiring an administrative token to run.
Get breadcrumb
Retrieves the navigational path (breadcrumbs) for a specific URL.
Get children
Lists all subfolders or items contained within a specified directory.
You can pull single pieces of content using get_item or retrieve reusable parts of a page with get_component.
Understand how your website is built by getting the full navigation tree (get_navigation_tree) or listing folders using get_children.
Run complex data requests against the schema via graphql or execute raw searches with OpenSearch JSON syntax using search.
Perform administrative tasks like clearing the cache (clear_cache) or rebuilding the content context (rebuild_context).
Determine breadcrumb navigation using get_breadcrumb or adjust how a URL is generated with transform_url.
Ask an AI about this
Waiting for input…
What AI agents can do with CrafterCMS: 12 Tools
These tools allow you to read site structure, fetch specific content components, execute complex data queries, and manage the engine cache directly through your AI agent.
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 CrafterCMS on VinkiusClear Cache
Clears the Crafter Engine cache, requiring an administrative token to run.
Get Breadcrumb
Retrieves the navigational path (breadcrumbs) for a specific URL.
Get Children
Lists all subfolders or items contained within a specified directory.
Get Component
Renders and pulls the data for one specific content component type.
Get Item
Retrieves all metadata and content for a single, identified item in the CMS.
Get Navigation Tree
Generates a comprehensive map of the entire site's navigation structure.
Get Status
Reports the current operational health and status of the Crafter Engine.
Get Tree
Gets a complete, deep hierarchy listing for all content under a specified folder.
Graphql
Executes any defined query using the GraphQL language against your content schema.
Rebuild Context
Forces the system to rebuild its understanding of the site context, needing a...
Search
Runs a raw search query using OpenSearch JSON syntax across all content.
Transform Url
Applies specific logic to modify or adjust how a content path is presented in a URL.
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 CrafterCMS, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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 CrafterCMS. 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
Built on the Model Context Protocol (MCP) for 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 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Problem: Tracking down content structure is a massive pain point today., Solved with Vinkius AI Gateway
Today, figuring out how content is structured means opening the CMS admin panel, clicking through folder hierarchies, and running multiple reports. You copy paths, you check metadata, and you constantly switch between tabs just to confirm if a piece of content exists or where it belongs.
With this MCP, your agent handles that complexity for you. Instead of manual clicks and tab switching, you simply ask the system to generate the entire navigation map using `get_navigation_tree`. You get one clean output showing every section's relationship.
Get Site Context Instantly with CrafterCMS MCP
The biggest time sink is manually verifying if the content context matches your code. You have to jump into various administrative interfaces just to check status or trigger a fix.
Now, you tell your agent what needs fixing—maybe it's stale data after an update—and let it call `get_status` and then execute `rebuild_context`. The system handles the cleanup; you get clean data every time.
What your AI can actually do with this
Need to understand what's inside a large-scale content system without logging into the Studio? This MCP lets you inspect and query CrafterCMS directly through your agent. You can ask it to pull specific components, map out entire site hierarchies, or even run advanced searches using OpenSearch syntax. It’s built for deep visibility; use get_item to check a single piece of content, while graphql lets developers test complex data requests right from their workflow.
If you're already using Vinkius as your central catalog, connecting CrafterCMS means getting all that site context and structure information in one place, letting your AI client do the heavy lifting.
019ea5e6-bc7a-7006-991e-a6cf3e0c1229 Here's how it actually works
The bottom line is that your agent handles the connection details, letting you focus on asking questions about your site's content and structure.
Subscribe to the CrafterCMS MCP and provide your base URL, Site ID, and necessary access tokens.
Tell your agent exactly what content you need—for example, 'Show me all components under the /products folder.'
The MCP executes the correct query (like get_children or graphql) and returns structured data directly to your AI client.
Who is this actually for?
This MCP is essential for developers who need to test CMS logic without switching contexts. It also helps technical writers and product managers verify complex content structures before deployment.
You use this to validate data fetching paths, running graphql queries against the schema or checking component rendering using get_component.
You verify content relationships and site depth by calling get_navigation_tree and understanding folder hierarchies with get_children.
You monitor the engine health using get_status and manually trigger maintenance tasks like clear_cache after a major deployment.
What Changes When You Connect
Instead of opening the Crafter Studio to check metadata, you simply ask your agent to run get_item for a specific path, getting immediate data confirmation.
You can build complex queries without leaving your IDE. Use the graphql tool to test schema endpoints directly against your content store.
Need to understand site scope? Running get_navigation_tree instantly maps out every primary section and sub-page relationships.
Avoid manual cache flushes. If you know a deployment broke something, use clear_cache or rebuild_context via simple commands instead of jumping through admin panels.
Don't guess the URL structure. Use get_breadcrumb to verify the exact pathing for any piece of content before linking it anywhere.
See it in action
The developer needs data validation for a new feature.
A front-end dev can't confirm if an old article still exists under its expected path. They prompt their agent, asking to run get_item on the suspected URI. The MCP responds with the content payload or confirms it’s missing, letting them code confidently.
The content manager needs a full site map for audit purposes.
A marketing manager wants to confirm every section exists in the main navigation. They ask their agent to call get_navigation_tree, getting an immediate, comprehensive list of all top-level sections and subpages.
The DevOps team needs to troubleshoot slow content delivery.
A sysadmin suspects the CMS cache is stale. They instruct their agent to call get_status first, then, if needed, execute clear_cache, confirming the fix was applied without logging into a dashboard.
The product team needs to find all related content types.
A PM wants to see every folder under 'Products' and its sub-categories. They ask their agent to use get_children repeatedly, mapping out the entire taxonomy structure instantly.
The honest tradeoffs
Manually testing GraphQL endpoints
Trying to copy and paste a complex query into an external playground or switching between documentation and your IDE. This is slow and requires multiple logins.
Just ask your agent to run the graphql tool with the query you need. It keeps everything within your current workflow, making it fast and reliable.
Guessing content paths
A user knows they want a page but doesn't know if it’s at /site/page or /pages/page. They waste time checking multiple URLs.
Use the get_breadcrumb tool. It instantly validates the exact, correct navigational path for any content piece you provide.
Assuming cache status after a deployment
A developer pushes code and assumes the CMS is updated, only to find broken components because the engine context wasn't refreshed.
Always check the system first. Run get_status via your agent. If necessary, execute rebuild_context before running any content queries.
When It Fits, When It Doesn't
Use this MCP if you need to interact with CrafterCMS data—not just view it through a UI. You need programmatic access to the schema or the ability to trigger backend actions (like cache invalidation). If your goal is simply viewing the website as an end-user, don't use this; stick to standard browsing. However, if you are writing code that relies on content data, then this MCP is necessary. Specifically, if you need to check relationships, use get_navigation_tree. If you only need raw text searching across everything, the search tool works best. But if you're building something structured and complex, stick with graphql because it gives you precise control over exactly what data fields you retrieve.
Questions you might have
How do I check if a specific piece of content exists using CrafterCMS MCP? +
You use the get_item tool. Provide the full path to the item, and the MCP will return its data payload or an error indicating it's missing.
Is GraphQL required for all content queries with CrafterCMS MCP? +
No. While graphql is best for structured data requests, you can use search if you need a general keyword search across the entire content store using OpenSearch JSON.
What should I do if my site shows outdated information? CrafterCMS MCP? +
First, run get_status to see why the data might be stale. If the status is fine but the data is old, execute clear_cache or rebuild_context via your agent.
Can I map out all my site folders with CrafterCMS MCP? +
Yes, use get_navigation_tree. This tool generates a comprehensive visualization of the entire content hierarchy in one go.
We've already built the connector for CrafterCMS. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 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.