How to Use the Crafter CMS MCP in Mastra AI

Q: Can a Mastra AI agent retry a failed Crafter CMS content publish?

Yes, that's a core feature. You can configure the publishcraftercontent step in your workflow with automatic retries and exponential backoff. Mastra's engine manages the failure handling for you.

Q: What's the process for creating a conditional workflow with Crafter CMS and Mastra AI?

In your Mastra AI agent definition, use a tool like getsiteconfig. Then, use the output of that tool in an if condition to decide the next step, like whether to proceed with a publishcraftercontent call.

Automate complex content publishing and maintenance workflows in Crafter CMS with Mastra AI.

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 Mastra AI

Create your Vinkius account to connect Crafter CMS to Mastra AI 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 Mastra AI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build Resilient Publishing Pipelines

Chain `write_studio_xml` and `publish_crafter_content` into a single, reliable workflow. Your Mastra AI agent can generate a new page, then immediately attempt to publish it to the live delivery engine. If the publish fails, Mastra's engine can automatically retry with exponential backoff. This turns a manual, error-prone process into a fire-and-forget background job. You define the workflow, and Mastra ensures it completes.

Create Conditional Content Workflows

Your agent can use `get_site_config` to check for specific settings before taking action. For example, it can verify GraphQL endpoint availability before attempting to run a query with `execute_graphql_payload`. Mastra's workflow engine lets you build conditional branches based on the tool outputs. If a config value is missing, the agent can stop the process and notify an admin. This prevents your automations from running with bad data.

Automate Site Cleanup with this MCP Server

Set up a recurring workflow where an agent uses `search_crafter_delivery` to find old or unpublished content. Once identified, the agent can stage it for deletion. For destructive actions like `wipe_studio_xml`, you can use Mastra's `requireToolApproval` feature. The workflow will pause and wait for a human to confirm the deletion, adding a critical safety check to your automated maintenance jobs.

Setup guide

Set up Crafter CMS MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All Crafter CMS tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "crafter-cms-mcp-client",
  servers: {
    "crafter-cms-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "Crafter CMS Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to Crafter CMS tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent Crafter CMS transactions"
);
console.log(result.text);

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 Mastra AI

Create a Mastra AI workflow that triggers on a schedule. The first step calls `write_studio_xml` to create the content, and the second step calls `publish_crafter_content`. Mastra handles the execution and retries.

Yes, that's a core feature. You can configure the `publish_crafter_content` step in your workflow with automatic retries and exponential backoff. Mastra's engine manages the failure handling for you.

In your Mastra AI agent definition, use a tool like `get_site_config`. Then, use the output of that tool in an `if` condition to decide the next step, like whether to proceed with a `publish_crafter_content` call.

The server itself doesn't, but your Mastra AI client does. You can wrap dangerous tool calls like `wipe_studio_xml` with Mastra's `requireToolApproval` to pause the workflow and wait for manual confirmation.

Your workflows will handle site configuration JSON, Git-based XML content, and GraphQL payloads. Each tool execution happens inside a dedicated V8 Isolate sandbox on Vinkius. Your data is processed for the job and then discarded; nothing is stored.

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