How to Use the Craft CMS (Craftnet) MCP in Claude

Q: How do I install the Craft CMS (Craftnet) MCP Server in Claude Desktop?

Open your developer settings and edit the claudedesktopconfig.json file. Add the Vinkius endpoint under the mcpServers key. Restart the app to see the tools appear in your chat.

Manage Craftnet plugin sales, track payouts, and audit CMS licenses directly from Claude Desktop.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Craft CMS (Craftnet) MCP to Claude Desktop

Create your Vinkius account to connect Craft CMS (Craftnet) to Claude Desktop 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 Craft CMS (Craftnet) with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Track Craftnet sales via Claude Desktop

Connect this MCP Server to Claude and pull live transaction data straight from your Craftnet account. Ask the agent to run `list_sales_history` to see exactly who bought your plugins today. You get raw revenue numbers without clicking through the Craft Store dashboard. Need to check what you are actually taking home? Claude runs `list_payout_history` to break down developer disbursements. You can paste a spreadsheet of expected revenue into the chat and have the agent verify it against real API responses instantly.

Audit client CMS licenses

Managing client sites gets messy when you lose track of who owns what. Use `list_cms_licenses` to dump every active Craft CMS license tied to your account into the conversation window. Claude formats the output into a clean markdown table so you know exactly which domains need renewals. You can also track third-party add-ons using `list_plugin_licenses`. If a client asks why their site broke after an update, you just ask Claude to check the expiration dates on their specific plugin bundle.

Research the plugin ecosystem

Building a new Craft site requires picking the right add-ons. Tell Claude to `search_plugins_by_name` for specific functionality like SEO or caching. The agent pulls live store data instead of hallucinating outdated packages. Dig deeper into specific tools with `get_plugin_details`. Claude reads the metadata, checks author details, and reviews compatibility requirements. You can even run `list_plugin_categories` to explore entirely new verticals while planning a site architecture.

Setup guide

Set up Craft CMS (Craftnet) MCP in Claude Web or Desktop

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 Craft CMS (Craftnet) MCP tools are available immediately — no restart needed.

Endpoint URL

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

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Craft CMS (Craftnet) MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under craft-cms-craftnet-mcp.

json

{
  "mcpServers": {
    "craft-cms-craftnet-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 Craftnet. 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 Craft CMS (Craftnet) 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 Craft CMS (Craftnet) MCP in Claude Desktop

Open your developer settings and edit the claude_desktop_config.json file. Add the Vinkius endpoint under the mcpServers key. Restart the app to see the tools appear in your chat.

Yes. The agent calls the Craftnet API directly to pull your historical developer disbursements. You get exact revenue figures right in your chat window.

You can connect it there too. Go to Settings, open Integrations, and paste the remote server URL as a custom connector. No local installation required.

The server fetches live store data, including categories, author information, and compatibility requirements. Ask the agent to find specific tools based on a keyword.

Vinkius runs the server in an isolated V8 sandbox that only lives for the duration of the request. Your plugin sales, payout history, and user lists never persist on our infrastructure. The agent reads the transaction data, answers your prompt, and the container dies.

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