How to Use the Kentico (CMS & DXP) MCP in CrewAI

Q: How do I prevent agents from deleting Kentico (CMS & DXP) objects?

Use the toolfilter option in your agent config. Explicitly exclude deletesystemobject to ensure your agents can only read or update data.

Deploy autonomous crews to monitor and manage your Kentico (CMS & DXP) environment using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Kentico (CMS & DXP) MCP to CrewAI

Create your Vinkius account to connect Kentico (CMS & DXP) 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 Kentico (CMS & DXP) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Kentico (CMS & DXP) agents

Assign a dedicated agent to watch your system objects. It uses `list_system_objects` to track changes and reports anomalies back to your central moderator. This removes the need for manual oversight. Your crew continuously checks the health of your configuration and takes corrective action when required.

Role-based document management

Create specialized agents for different tasks. One agent focuses on content updates via `update_site_document`, while another audits permissions using `get_user`. This hierarchy prevents any single agent from having too much control. You define the scope, and the crew collaborates to maintain your site state.

Real-time system synchronization

Keep your various environments in sync by having your crew compare objects. They use `get_single_object` to verify settings and apply fixes if they find drift. This is a powerful way to manage multiple instances. Your agents work in the background to ensure consistency across your infrastructure.

Setup guide

Set up Kentico (CMS & DXP) 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 Kentico (CMS & DXP) tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Kentico (CMS & DXP) 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="Kentico (CMS & DXP) Analyst",
        goal="Access and analyze Kentico (CMS & DXP) data via MCP.",
        backstory="Expert analyst with direct Kentico (CMS & DXP) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Kentico (CMS & DXP) 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 Kentico Xperience. 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 Kentico (CMS & DXP) 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 Kentico (CMS & DXP) MCP in CrewAI

Pass the MCP server URL directly to the agent definition. You can filter the tools to give specific agents access only to what they need.

Yes. You can set up a manager agent that delegates content update tasks to specialized worker agents using the provided tools.

CrewAI handles stdio, SSE, and HTTP. The Vinkius endpoint works with all of these, giving you flexibility in how your crew communicates with the server.

Use the tool_filter option in your agent config. Explicitly exclude `delete_system_object` to ensure your agents can only read or update data.

All data flows through a secure, isolated Vinkius container. No raw credentials are ever exposed to the agents; the server handles all authentication internally.

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