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 AutoGen 9 tools — connect in under 2 minutes

Name: Contentstack
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 9 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Contentstack as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="contentstack_agent",
            tools=tools,
            system_message=(
                "You help users with Contentstack. "
                "9 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Contentstack tools. Connect 9 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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

Follow these steps to integrate the Contentstack MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 9 tools from Contentstack automatically

Why Use AutoGen with the Contentstack MCP Server

AutoGen provides unique advantages when paired with Contentstack through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Contentstack tools to solve complex tasks

Role-based architecture lets you assign Contentstack tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Contentstack tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Contentstack tool responses in an isolated environment

Contentstack + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Contentstack MCP Server delivers measurable value.

Collaborative analysis: one agent queries Contentstack while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Contentstack, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Contentstack data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Contentstack responses in a sandboxed execution environment

Contentstack MCP Tools for AutoGen (9)

These 9 tools become available when you connect Contentstack to AutoGen 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 AutoGen

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

Common issues when connecting Contentstack to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Contentstack + AutoGen FAQ

Common questions about integrating Contentstack MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Contentstack tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.