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 AutoGen 10 tools — connect in under 2 minutes

Name: Agility CMS
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Agility CMS as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="agility_cms_agent",
            tools=tools,
            system_message=(
                "You help users with Agility CMS. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Agility CMS tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the Agility CMS MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from Agility CMS automatically

Why Use AutoGen with the Agility CMS MCP Server

AutoGen provides unique advantages when paired with Agility CMS through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Agility CMS tools to solve complex tasks

Role-based architecture lets you assign Agility CMS tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Agility CMS tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Agility CMS tool responses in an isolated environment

Agility CMS + AutoGen Use Cases

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

Collaborative analysis: one agent queries Agility CMS while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Agility CMS, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Agility CMS data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Agility CMS responses in a sandboxed execution environment

Agility CMS MCP Tools for AutoGen (10)

These 10 tools become available when you connect Agility CMS to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

Common issues when connecting Agility CMS to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Agility CMS + AutoGen FAQ

Common questions about integrating Agility CMS MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Agility CMS tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.