Can my agent keep track of incremental updates to my CMS items?

Yes. The agent has tools specifically designed to fetch incremental updates using a sync token. It can request only the CMS items or pages that have changed (created, updated, or deleted) since the last automated sync, optimizing fetch latency.

How do I find the correct Reference Name to query content?

Reference Names match the identifiers predefined in your Agility CMS Models architecture (such as 'articles', 'authors', or 'posts'). If you are unsure, ask the agent to scan common variables based on your company's naming conventions.

Can my agent preview unpublished drafting content?

That depends on the API Token you supply during the integration. If you provide a Preview API Key, the agent will have read-access to the staging and drafted documents. If you provide a Fetch API key, it will only see published items.

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

Name: Agility CMS
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Agility CMS through Vinkius, pass the Edge URL in the `mcps` parameter and every Agility CMS 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="Agility CMS Specialist",
    goal="Help users interact with Agility CMS effectively",
    backstory=(
        "You are an expert at leveraging Agility CMS 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 Agility CMS "
        "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 Agility CMS MCP Server

Connect your Agility CMS instance to your AI agent and turn it into the ultimate Headless CMS assistant. Skip manual API queries and interact directly with your content architecture using natural language.

When paired with CrewAI, Agility CMS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Agility CMS 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

Sitemap & Routing — Retrieve nested sitemap trees or flat router architectures to understand how your channels are structured
Content Lists — Search, list, and count items across specific CMS references like articles, authors, or products
Page Layouts — Fetch exact page modules, UI components mapping, and structural layout definitions using Page IDs
Content Operations — Read full content payloads for individual items and synchronize granular CMS updates over time
Media Galleries — Fetch specific media asset groups and tracking galleries for imagery

The Agility CMS 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 Agility CMS to CrewAI via MCP

Follow these steps to integrate the Agility CMS 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 Agility CMS

Why Use CrewAI with the Agility CMS MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Agility CMS 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

Agility CMS + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Agility CMS 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 Agility CMS, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Agility CMS 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 Agility CMS against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Agility CMS MCP Tools for CrewAI (10)

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

count_reference_items

Get the total size/count of items in a specific Reference List

get_media_gallery

Retrieve a specific media gallery mapping containing photos

get_page_layout

Retrieve the layout and structural modules of a single Page

get_single_item

g., an article body) knowing its numeric content ID. Retrieve a single Agility CMS content item by its ID

get_site_flat_router

Retrieve the exact flat list of all CMS routes/pages

get_site_tree

Requires the target channel name. Retrieve the nested sitemap architecture of a digital channel

list_content_items

g. blog posts, articles, authors). The items are retrieved from the Headless CMS environment. List content items from an Agility CMS Reference list

search_content_reference

Search for specific keywords inside a Content Reference List

sync_incremental_items

Start with 0 for full backup. Get incrementally updated items since the last sync token

sync_incremental_pages

Start with 0 for a full fetch. Get incrementally updated pages since the last sync token

Example Prompts for Agility CMS in CrewAI

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

"Get the flat sitemap for our website to see all registered routes."

"Search the 'blog_posts' reference list for the keyword 'announcement'."

"Retrieve the full page layout and modules for page ID 12."

Troubleshooting Agility CMS MCP Server with CrewAI

Common issues when connecting Agility CMS 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.

Agility CMS + CrewAI FAQ

Common questions about integrating Agility CMS 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.