Bring Graphql
to VS Code Copilot
Create your Vinkius account to connect Crafter CMS to VS Code Copilot and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Crafter CMS MCP Server?
Connect your Crafter CMS instance to any AI agent and take full control of your enterprise headless CMS and Git-based content workflows through natural conversation.
What you can do
- GraphQL Orchestration — Execute absolute explicit nesting requirements against the delivery schema using raw GraphQL payloads natively
- Studio Tree Navigation — Perform structural extraction of properties driving active Git hierarchies and trace nested XML structures safely
- Git-Based Content Writing — Provision highly-available XML payloads to write physical Git boundaries and generate new pages or components
- Live Publishing — Trigger automated workflow bounds to migrate changes from Crafter Studio onto the high-performance Delivery Engine
- Elasticsearch Discovery — Inspect deep internal arrays leveraging integrated Elasticsearch to perform full-text queries spanning all content nodes
- Platform Governance — Identify precise active arrays spanning rented Context domains and list configured sites and studio users securely
- Environment Audit — Discovered disconnected physical limits fetching site configurations and global variables tied to your frontend SDKs
How it works
- Subscribe to this server
- Enter your Crafter CMS Base URL and Access Token (found in Crafter Studio > Token Management)
- Start managing your Git-based content from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Content Developers — test GraphQL queries and write XML content nodes without opening the Studio interface
- DevOps Engineers — monitor site configurations and verify publication workflows across environments
- Technical Marketers — search for content across global sites and audit metadata using natural language
- Architects — inspect Git hierarchies and verify environment variables tied to headless frontends
Built-in capabilities (10)
Identify bounded routing spaces inside the Headless Crafter Engine
json` isolating GraphQL URL limits. Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly
Enumerate explicitly attached structured rules exporting active Configuration
json` identifying exact folders tracing nested XML structures safely. Perform structural extraction of properties driving active Git hierarchies
Identify precise active arrays spanning rented Context domains
Retrieve the exact structural matching verifying Blueprint constraints
json` executing workflow bounds migrating a Studio change onto the Delivery Engine live endpoint. Dispatch an automated validation check routing explicit Deployments
Inspect deep internal arrays mitigating specific Picture constraints
Irreversibly vaporize explicit App nodes dropping live Database bytes
json` generating pages. Provision a highly-available XML Payload generating new Content nodes
Why VS Code Copilot?
GitHub Copilot Agent mode brings Crafter CMS data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Crafter CMS in VS Code Copilot
Why run Crafter CMS with Vinkius?
The Crafter CMS connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Crafter CMS using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Crafter CMS and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Crafter CMS to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Crafter CMS for VS Code Copilot
Every request between VS Code Copilot and Crafter CMS is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Runway ML Alternative
4 toolsAutomate AI video generation via Runway ML — create, monitor, and manage Gen-3 Alpha and Gen-2 tasks directly from any AI agent.

Tableau
7 toolsAccess workbooks, views, data sources, and dashboard insights from Tableau — the enterprise BI and analytics platform.

Iterable
10 toolsManage cross-channel marketing campaigns, users, and templates via Iterable API.

Dopplio
6 toolsSend personalized video messages at scale that use AI to customize each clip for the recipient and boost response rates.
