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

Name: Contentstack
Availability: InStock
Author: Vinkius

ai.pydantic.dev/mcp

Built by Vinkius GDPR 9 Tools SDK

Pydantic AI brings type-safe agent development to Python with first-class MCP support. Connect Contentstack through Vinkius and every tool is automatically validated against Pydantic schemas. catch errors at build time, not in production.

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 pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerHTTP

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    server = MCPServerHTTP(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

    agent = Agent(
        model="openai:gpt-4o",
        mcp_servers=[server],
        system_prompt=(
            "You are an assistant with access to Contentstack "
            "(9 tools)."
        ),
    )

    result = await agent.run(
        "What tools are available in Contentstack?"
    )
    print(result.data)

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.

Pydantic AI validates every Contentstack tool response against typed schemas, catching data inconsistencies at build time. Connect 9 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.

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 Pydantic AI 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 Pydantic AI via MCP

Follow these steps to integrate the Contentstack MCP Server with Pydantic AI.

Install Pydantic AI

Run pip install pydantic-ai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 9 tools from Contentstack with type-safe schemas

Why Use Pydantic AI with the Contentstack MCP Server

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

Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application

Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Contentstack integration code

Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors

Dependency injection system cleanly separates your Contentstack connection logic from agent behavior for testable, maintainable code

Contentstack + Pydantic AI Use Cases

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

Type-safe data pipelines: query Contentstack with guaranteed response schemas, feeding validated data into downstream processing

API orchestration: chain multiple Contentstack tool calls with Pydantic validation at each step to ensure data integrity end-to-end

Production monitoring: build validated alert agents that query Contentstack and output structured, schema-compliant notifications

Testing and QA: use Pydantic AI's dependency injection to mock Contentstack responses and write comprehensive agent tests

Contentstack MCP Tools for Pydantic AI (9)

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

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

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

MCPServerHTTP not found

Update: pip install --upgrade pydantic-ai

Contentstack + Pydantic AI FAQ

Common questions about integrating Contentstack MCP Server with Pydantic AI.

How does Pydantic AI discover MCP tools?

Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.

Does Pydantic AI validate MCP tool responses?

Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.

Can I switch LLM providers without changing MCP code?

Absolutely. Pydantic AI abstracts the model layer. your Contentstack MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.