2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 9 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Webiny CMS through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Webiny CMS tool calls without waiting for prompts between steps. Connect 9 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Webiny CMS

Ask Cline: "Using Webiny CMS, help me...". 9 tools available

Why Use Cline with the Webiny CMS MCP Server

Cline provides unique advantages when paired with Webiny CMS through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Webiny CMS + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Webiny CMS and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Webiny CMS tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Webiny CMS and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Webiny CMS for real-time status and let Cline generate hotfix patches based on the findings

Webiny CMS MCP Tools for Cline (9)

These 9 tools become available when you connect Webiny CMS to Cline 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 Cline

Ready-to-use prompts you can give your Cline 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 Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Webiny CMS + Cline FAQ

Common questions about integrating Webiny CMS MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Webiny CMS to Cline

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