How do I correctly generate a Contentstack Delivery Token?

Log into your core Contentstack account dashboard securely. Access the specific Stack you wish to query and navigate toward the technical 'Settings' header before clicking on 'Tokens'. Within this specific submenu, specifically select 'Delivery Tokens'. Generate a new one with an identifying name, assigning it distinctly to your intended 'Environment'. Note down the produced Token safely to input along with the matching Stack API key below.

Can the agent update entries or publish content directly to the CMS?

No. The integration exclusively relies upon Contentstack's globally distributed 'Delivery API' rather than their 'Management API', deliberately restricting operations to a secure read-only modality focused on retrieving already published entries, preventing accidental automated or unauthorized payload mutations from impacting live production data stores.

Do I need to type the exact environment name as it appears in Contentstack?

Yes, accuracy is strictly required. Providing the exact environment name (e.g., 'production' or 'staging') matching the internal naming correctly ensures the endpoint filters accurately out published iterations of records belonging only to those targeted distribution layers you are aiming specifically at querying reliably during chat prompts.

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

Name: Contentstack
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

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.

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 Contentstack and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "contentstack": {
      "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 Contentstack MCP Server

Empower your conversational AI with secure and instant read access to your Contentstack headless CMS. Utilizing the Contentstack Delivery API, your agent can efficiently fetch published entries, retrieve asset URLs, and audit content type schema structures in real-time.

GitHub Copilot Agent mode brings Contentstack 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

Entry Retrieval — Instruct the agent to query and read live content entries by searching for specific title tags or matching query filters.
Asset Discovery — Request exact URLs from the media library to find specific images, PDFs, or files needed in your conversational context.
Schema Inspections — Ask for a detailed structural breakdown of any Content Type before utilizing it in an external application.

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

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

Create MCP config

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

Add the server config

Paste the JSON configuration above

Enable Agent mode

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

Start using Contentstack

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

Why Use VS Code Copilot with the Contentstack MCP Server

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

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

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

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

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

Contentstack + VS Code Copilot Use Cases

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

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

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

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

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

Contentstack MCP Tools for VS Code Copilot (9)

These 9 tools become available when you connect Contentstack to VS Code Copilot via MCP:

get_asset_details

Get details for a specific asset

get_content_type_details

Get the schema for a specific content type

get_entry

Get detailed content for a specific entry

get_stack_summary

Get high-level metadata about the current stack

list_assets

List all published assets

list_content_types

List all content types in the stack

list_entries

List published entries for a specific content type

search_entries

Search for entries using a JSON query

sync_content

Retrieve delta of changes since last sync

Example Prompts for Contentstack in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Contentstack immediately.

"Retrieve the published blog post entry with the title 'Future Trends in AI' from our primary environment."

"Describe the content model schema required for 'Hero Banner' items in my stack."

"List the most recent image assets uploaded to our Contentstack library."

Troubleshooting Contentstack MCP Server with VS Code Copilot

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

MCP tools not available

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

Contentstack + VS Code Copilot FAQ

Common questions about integrating Contentstack MCP Server with VS Code Copilot.

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.

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.

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.

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.