How to Use the Contentstack MCP in CrewAI

Q: How does CrewAI interact with Contentstack?

You pass the server URL to the agent's mcps list. This enables the entire crew to share the tools, allowing specialized agents to pull data from your CMS as needed.

Q: Can CrewAI agents search Contentstack entries effectively?

Yes, the search agent uses searchentries with JSON queries to find specific records. It then passes these results to other agents in the crew for analysis.

Q: Is Contentstack tool filtering supported in CrewAI?

You can selectively expose tools by using the toolfilter in your CrewAI configuration. This allows you to hide sensitive tools from agents that only need read access.

Deploy a specialized crew of agents to manage your Contentstack repository with autonomous research and analysis.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Contentstack MCP to CrewAI

Create your Vinkius account to connect Contentstack to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Contentstack with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Contentstack Teams with CrewAI

Assign a 'Researcher' agent to call `search_entries` while a 'Writer' agent uses `get_entry` to format the findings. CrewAI coordinates these agents so they share context and work toward a single goal. This is for operations that need to scan thousands of entries without human help. The agents divide the labor, ensuring deep coverage of your CMS content.

Autonomous CMS Monitoring

Set up a monitor agent that periodically runs `get_stack_summary` to track the health and size of your Contentstack environment. If the agent detects an unexpected change, it can alert your team or trigger a fix. You move from manual oversight to automated management. It keeps your CMS state visible and predictable.

Granular Tool Exposure

Use the CrewAI `tool_filter` to limit which agents see which CMS tools. You can give your analyst access to `list_content_types` while restricting write-heavy tools to a specific supervisor agent. This keeps your agent roles tight and secure. You control exactly how the team interacts with your digital assets.

Setup guide

Set up Contentstack MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Contentstack tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Contentstack Analyst",
    goal="Access and analyze Contentstack data via MCP.",
    backstory="Expert analyst with direct Contentstack access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Contentstack transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Contentstack Analyst",
        goal="Access and analyze Contentstack data via MCP.",
        backstory="Expert analyst with direct Contentstack access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Contentstack transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Contentstack. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Contentstack now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Contentstack MCP in CrewAI

You pass the server URL to the agent's `mcps` list. This enables the entire crew to share the tools, allowing specialized agents to pull data from your CMS as needed.

Yes, the search agent uses `search_entries` with JSON queries to find specific records. It then passes these results to other agents in the crew for analysis.

You can selectively expose tools by using the `tool_filter` in your CrewAI configuration. This allows you to hide sensitive tools from agents that only need read access.

Yes, the manager agent can delegate tasks to subordinates that use these tools. This allows for complex workflows where the manager breaks down the request and delegates the CMS lookup.

Data is processed only within the memory allocated to the ephemeral Vinkius container. We enforce strict isolation, ensuring that no Contentstack entry metadata persists once the crew finishes its current task.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript