2,500+ MCP servers ready to use
Vinkius

Webiny CMS MCP Server for VS Code Copilot 9 tools — connect in under 2 minutes

Built by Vinkius GDPR 9 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings Webiny CMS data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Webiny CMS MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Webiny CMS

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

Why Use VS Code Copilot with the Webiny CMS MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Webiny CMS through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Webiny CMS + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Webiny CMS MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Webiny CMS MCP Tools for VS Code Copilot (9)

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

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

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Webiny CMS + VS Code Copilot FAQ

Common questions about integrating Webiny CMS MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Webiny CMS to VS Code Copilot

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