2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 9 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "webiny-cms": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Webiny CMS
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.

Cursor's Agent mode turns Webiny CMS into an in-editor superpower. Ask Cursor to generate code using live data from Webiny CMS and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor via MCP

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

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Webiny CMS

Open Agent mode in chat and ask: "Using Webiny CMS, help me...". 9 tools available

Why Use Cursor with the Webiny CMS MCP Server

Cursor AI Code Editor provides unique advantages when paired with Webiny CMS through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Webiny CMS + Cursor Use Cases

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

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Webiny CMS MCP Tools for Cursor (9)

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

01

create_cms_entry

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

02

delete_cms_entry

This action is irreversible. Permanently deletes a content entry revision

03

execute_graphql_query

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

04

get_api_introspection

Retrieves the GraphQL schema introspection for the Webiny instance

05

get_model_entry_details

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

06

get_tenant_config

Retrieves global settings for the Webiny tenant

07

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

08

publish_cms_entry

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

09

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 Cursor

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

01

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

02

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

03

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

Troubleshooting Webiny CMS MCP Server with Cursor

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

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Webiny CMS + Cursor FAQ

Common questions about integrating Webiny CMS MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Webiny CMS to Cursor

Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.