Can my agent create new content objects in Cosmic?

Yes. Use the 'create_cms_object' tool. Provide the type slug, title, and a JSON object for metadata. The agent will command the backend to generate a new entry in your specified bucket.

How do I audit the schema of an existing Object Type?

Provide the type slug to the 'get_schema_details' tool. Your agent will analyze the specific localized variables and decode the native boundaries, showing you exactly which fields and metadata parameters the schema requires.

Can I permanently delete media assets via the agent?

Absolutely. The 'wipe_media_asset' tool allows you to irreversibly remove physical media from your Cosmic buckets. This is a powerful way to manage your storage quotas and cleanup dangling files directly from the chat.

Cosmic MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Cosmic
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Cosmic through Vinkius, pass the Edge URL in the `mcps` parameter and every Cosmic tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cosmic Specialist",
    goal="Help users interact with Cosmic effectively",
    backstory=(
        "You are an expert at leveraging Cosmic tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Cosmic "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

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 Cosmic MCP Server

Connect your Cosmic bucket to any AI agent and take full control of your AI-powered headless CMS and digital content workflows through natural conversation.

When paired with CrewAI, Cosmic becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cosmic tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Object Management — List, retrieve, and create CMS objects across your buckets, allowing you to drop formatted JSON payloads feeding strictly verified metadata trees
Content Mutation — Safely update existing objects by patching title and metadata blocks, substituting draft values natively through the REST API
Schema Auditing — Enumerate active object types and retrieve structural extraction of properties to verify exactly what fields and metadata the schema requires
Media Oversight — Inspect deep internal arrays of uploaded media, track imgix endpoints, and resolve explicit file metadata for seamless asset management
Bucket Cleanup — Irreversibly vaporize explicit app nodes and wipe media assets to manage storage quotas and clear up internal database allocations
Environment Navigation — Identify bounded routing spaces inside your headless environments and switch between different content models (type slugs) easily

The Cosmic MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 Cosmic to CrewAI via MCP

Follow these steps to integrate the Cosmic MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Cosmic

Why Use CrewAI with the Cosmic MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Cosmic through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Cosmic + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Cosmic MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Cosmic for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Cosmic, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Cosmic tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Cosmic against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Cosmic MCP Tools for CrewAI (10)

These 10 tools become available when you connect Cosmic to CrewAI via MCP:

create_cms_object

Provision a highly-available JSON Payload generating new Cosmic Drafts

get_media_asset

Retrieve the exact structural matching verifying explicit Media IDs

get_schema_details

Perform structural extraction of properties driving active Fields

get_single_object

Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly

list_bucket_objects

Identify bounded routing spaces inside the Headless Cosmic CMS Environments

list_schema_types

Enumerate explicitly attached structured rules exporting active Types

list_uploaded_media

Inspect deep internal arrays mitigating specific Picture limits

patch_cms_object

Mutate global Web CRM boundaries substituting Draft values via ID

wipe_cms_object

Irreversibly vaporize explicit App nodes dropping live Document rows

wipe_media_asset

Dispatch an automated validation check routing explicit Disk removals

Example Prompts for Cosmic in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Cosmic immediately.

"List all objects of type 'posts' in my Cosmic bucket"

"Create a new 'event' object: Title 'Developer Meetup', Date '2024-05-15'"

"Show me the details for object type 'products'"

Troubleshooting Cosmic MCP Server with CrewAI

Common issues when connecting Cosmic to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Cosmic + CrewAI FAQ

Common questions about integrating Cosmic MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.