How to Use the Cockpit (Self-hosted Headless CMS API) MCP in CrewAI

Q: Can a CrewAI crew handle bulk media optimization in Cockpit (Self-hosted Headless CMS API)?

Yes, a media agent can use getasset to find unoptimized files and call getassetimage to generate resized thumbnails. The crew then updates the respective content entries autonomously.

Deploy specialized CrewAI teams to manage your Cockpit (Self-hosted Headless CMS API) content pipelines autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cockpit (Self-hosted Headless CMS API) MCP to CrewAI

Create your Vinkius account to connect Cockpit (Self-hosted Headless CMS API) 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 Cockpit (Self-hosted Headless CMS API) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative content moderation in CrewAI

The `list_content_items` and `create_or_update_content_item` tools let your CrewAI agents collaborate on draft reviews. A researcher agent pulls raw drafts, while an editor agent reviews the content and updates the fields in Cockpit. Because CrewAI uses shared memory, the editor agent remembers previous feedback. This ensures your self-hosted CMS content stays consistent across all published entries.

Autonomous sitemap and routing audits

This MCP Server provides `get_sitemap` and `list_routes` to let your crew audit your site's structure. A specialized auditor agent crawls the active routes, identifies dead links, and flags errors. The auditor then coordinates with a manager agent to queue fixes. They can update metadata or restructure parent menus without requiring manual developer intervention.

Automated search index synchronization

The `search_detektivo` and `get_page_by_route` tools allow your crew to keep external search indices aligned with your CMS. A sync agent monitors page changes and updates the Detektivo index dynamically. This setup runs entirely in the background, using hierarchical execution to coordinate between content fetching and indexing. Your search experience stays accurate to your latest Cockpit edits.

Setup guide

Set up Cockpit (Self-hosted Headless CMS API) 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 Cockpit (Self-hosted Headless CMS API) tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

    task = Task(
        description="List recent Cockpit (Self-hosted Headless CMS API) 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 Cockpit CMS. 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 Cockpit (Self-hosted Headless CMS API) 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 Cockpit (Self-hosted Headless CMS API) MCP in CrewAI

You use the tool filter option in the MCP server configuration to expose only what that agent needs. For example, give your writer agent access to create_or_update_content_item while blocking delete_content_item.

Yes, a media agent can use get_asset to find unoptimized files and call get_asset_image to generate resized thumbnails. The crew then updates the respective content entries autonomously.

They use CrewAI's shared memory system to pass IDs and slugs between tasks. An agent fetching a sitemap passes the route list directly to the next agent in the sequence.

It supports stdio, SSE, and Streamable HTTP. For Vinkius-hosted MCP servers, you typically configure the HTTP transport with your secure endpoint token.

Every request for asset metadata or page content runs in an isolated, single-use V8 sandbox. Your self-hosted Cockpit access tokens are processed securely and never stored, keeping your backend entirely private.

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