How to Use the Crafter CMS MCP in Cline

Q: Can Cline search my live Crafter CMS delivery engine?

It certainly does. The agent triggers searchcrafterdelivery to inspect deep internal arrays and verify that your content is actually rendering on the live endpoint.

Give Cline direct control over Crafter CMS to automatically scaffold XML pages, query the delivery engine, and publish headless content.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Crafter CMS MCP to Cline

Create your Vinkius account to connect Crafter CMS to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Crafter CMS with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Cline builds and publishes end-to-end

The XML writing tool lets your agent build frontend components and their backing content simultaneously. Your agent writes the React code, creates the backing CMS nodes using `write_studio_xml`, and then runs `publish_crafter_content` to push it live. Everything happens in one continuous motion. Instead of asking for permission at every step, the system reads the blueprint constraints via `list_studio_users` and executes the workflow bounds automatically.

Read deep Crafter CMS configurations

The configuration tools prevent your agent from hardcoding API limits. When your agent needs to know the exact routing spaces, it fires `execute_graphql_payload` through the MCP server to inspect the headless engine directly. Grabbing environment variables is just as simple. The system pulls `get_site_config` and `get_site_globals` to enumerate explicitly attached structured rules before it writes a single line of fetch logic.

Manage Git-based XML via this MCP Server

The studio tree tool maps out complex folder structures so you never have to click through a web UI. Now your agent identifies exact nested XML structures safely by calling `get_studio_tree`. Deleting old nodes is completely automated too. If a test suite fails, the agent runs `wipe_studio_xml` to irreversibly vaporize the explicit app nodes and clean up the database.

Setup guide

Set up Crafter CMS MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type crafter-cms-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Crafter CMS refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "crafter-cms-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Crafter CMS now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Crafter CMS MCP in Cline

Click the MCP Servers icon in your VS Code sidebar. From there, use the Marketplace tab for a one-click install or add the Vinkius remote server URL directly via the Streamable HTTP transport option.

It certainly does. The agent triggers `search_crafter_delivery` to inspect deep internal arrays and verify that your content is actually rendering on the live endpoint.

Your agent has full visibility into your rented context domains. It simply calls `list_platform_sites` to identify the precise active arrays you are currently running.

Tell your agent what you want the new model to look like. It will map the current state, generate the new highly-available XML payload, and write it straight to the Studio.

Your explicit Cloud logging traces and GraphQL payloads are completely protected. The Vinkius infrastructure relies on ephemeral, zero-trust execution, so your headless queries pass through a secure tunnel without leaving residual data behind.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript