Can I publish a draft content entry via chat?

Yes. The `publish_cms_entry` tool allows you to take any draft revision live. You just need to provide the entry ID and the model name, and your AI agent will handle the publication through the Webiny 'manage' API.

Is it possible to see the entire GraphQL schema of my instance?

Absolutely. Using the `get_api_introspection` tool, your agent can retrieve the full GraphQL schema introspection, giving you a complete overview of all available types, fields, and content models in your environment.

How do I add a new entry to a content model through conversation?

Use the `create_cms_entry` tool. Provide the singular model name (e.g., 'Article'), the target locale, and a JSON object containing the field data. Your agent will create the new draft entry instantly.

Webiny CMS MCP Server for Claude Desktop 9 tools — connect in under 2 minutes

Name: Webiny CMS
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 9 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Webiny CMS and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "webiny-cms": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Webiny CMS MCP Server

Connect your Webiny CMS instance to any AI agent and manage your headless content infrastructure through natural conversation.

Claude Desktop is the definitive way to connect Webiny CMS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Content Lifecycle — Create, update, publish, and delete content entries for any model directly from your agent
Model Discovery — List all entries for specific content models and browse available data structures using introspection
Advanced GraphQL — Execute raw GraphQL queries or mutations for custom logic and complex nested data operations
Revision Control — Retrieve specific entry details by ID to inspect metadata and field-level property values
API Management — Discover available types, fields, and models in your current environment through automated introspection
Global Config — Verify high-level tenant settings and configurations to ensure your CMS environment is healthy
Multi-Locale Support — Seamlessly manage content across different language locales (e.g., en-US, pt-BR)

The Webiny CMS MCP Server exposes 9 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Webiny CMS to Claude Desktop via MCP

Follow these steps to integrate the Webiny CMS MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Webiny CMS

Look for the 🔌 icon in the chat. your 9 tools are now available

Why Use Claude Desktop with the Webiny CMS MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Webiny CMS through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Webiny CMS + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Webiny CMS MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Webiny CMS MCP Tools for Claude Desktop (9)

These 9 tools become available when you connect Webiny CMS to Claude Desktop via MCP:

create_cms_entry

Provide the singular model name and field data as a JSON object. Creates a new draft entry for a content model

delete_cms_entry

This action is irreversible. Permanently deletes a content entry revision

execute_graphql_query

Specify api_type (manage, read, preview) and locale. Executes a raw GraphQL query or mutation against the Webiny CMS API

get_api_introspection

Retrieves the GraphQL schema introspection for the Webiny instance

get_model_entry_details

ID refers to the specific revision. Retrieves details for a specific content model entry

get_tenant_config

Retrieves global settings for the Webiny tenant

list_model_entries

Provide the model plural name (e.g. "Articles"). Specify api_type (manage for drafts, read for live). Lists all entries for a specific content model in Webiny

publish_cms_entry

Provide the specific revision ID. Publishes a draft entry, making it available via the "read" API

update_cms_entry

Provide the entry ID and a JSON object containing the field updates. Updates fields of an existing content entry revision

Example Prompts for Webiny CMS in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Webiny CMS immediately.

"List all entries for the 'BlogPosts' model in en-US."

"Create a new 'Author' entry: { 'name': 'John Doe', 'bio': 'Tech Writer' } in en-US."

"Publish the entry with ID 'post-123' for model 'Article'."

Troubleshooting Webiny CMS MCP Server with Claude Desktop

Common issues when connecting Webiny CMS to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Webiny CMS + Claude Desktop FAQ

Common questions about integrating Webiny CMS MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.