Agility CMS MCP. Query your entire content architecture instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Agility CMS MCP lets your agent talk directly to a complex Headless CMS instance. Instead of writing manual API calls or navigating deep UI menus, you can ask it questions about your site architecture, content lists, and page layouts using plain English.
It acts like an ultimate assistant for managing structured content.
What your AI agents can do
Count reference items
Provides the total item count for any specified content list in Agility CMS.
Get media gallery
Retrieves a defined set of media assets or photo galleries associated with a page.
Get page layout
Pulls the structural blueprint, including all UI modules and layout definitions, for a single page ID.
Retrieve either a complete nested sitemap tree or a flat list of every accessible page route.
Quickly get the total number of items within specific content categories, like authors or products.
Find articles or records by searching for keywords inside a defined content reference list.
Fetch the exact UI modules and structural definitions used on any given page ID.
Pull down only the content items or pages that have changed since your last sync token, avoiding full data pulls.
Retrieve specific groups of media assets and tracking galleries for imagery.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Agility CMS: 10 Tools for Content Architecture
These tools let you analyze content structure by listing items, searching keywords, fetching page layouts, and syncing data directly from Agility CMS.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Agility CMS on Vinkius019d7549count reference items
Provides the total item count for any specified content list in Agility CMS.
019d7549get media gallery
Retrieves a defined set of media assets or photo galleries associated with a page.
019d7549get page layout
Pulls the structural blueprint, including all UI modules and layout definitions, for a single page ID.
019d7549get single item
Fetches the full text and content payload of one specific article or record using its unique content ID.
019d7549get site flat router
Returns a comprehensive list of every CMS route or page available on the site, regardless of nesting depth.
019d7549get site tree
Maps out the nested sitemap architecture for a digital channel, showing parent-child relationships.
019d7549list content items
Lists all content records from a specific Agility CMS reference list, such as blog posts or authors.
019d7549search content reference
Searches for defined keywords within any designated content reference list.
019d7549sync incremental items
Downloads only the content items that have been updated since a specified sync token was last used.
019d7549sync incremental pages
Retrieves pages that have changed or been added since the last successful synchronization marker.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Agility CMS, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Agility 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Mapping Content Structures Is a Nightmare
Right now, figuring out your site's entire map means jumping through multiple admin interfaces. You click on the sitemap, then copy-paste URLs into an external tool to check their status. Then you have to manually check content lists to see if related articles even exist, leading to hours of cross-checking and painful context switching.
With this MCP, your agent handles it all in a single chat window. You ask for the full sitemap map, and it returns the complete, nested structure—all ready to be consumed by your code or your report. It's instant visibility into everything.
Getting Full Content Payloads with `get_single_item`
Before, getting the full text of an article meant navigating to that specific record and then manually copying the content payload. If you needed to pass it to another tool or write a component from it, that was half the work.
Now, asking for the content item using `get_single_item` gives your agent the entire, clean data payload in one go. It's raw, ready-to-use information.
What you can do with this MCP connector
This connector turns your Agility CMS into the central data source for any AI agent. You stop wrestling with complex API documentation just to check if a specific page module exists or how many articles are in 'authors'. Instead, you talk naturally: "What's the sitemap structure for our main product line?" Your agent handles the deep queries, retrieving everything from nested site maps and component layouts to full content payloads.
The real power comes when your agent connects this CMS data with other systems; imagine chaining this MCP with a CRM MCP to automatically generate documentation based on customer profiles. Vinkius makes that possible because you connect once, and your single AI client can then use this data alongside billing records or messaging history.
It’s all about getting the right structured information instantly.
019d7549-c125-72dd-825d-0472cad1a35f 
How Agility CMS MCP Works
- 1 Subscribe to this MCP and provide the necessary Agility GUID, target locale, and API key.
- 2 Tell your agent what structure you need—for example, "Show me the full sitemap for the main channel."
- 3 Your agent executes the correct query against the CMS and returns structured data like module layouts or nested routes.
The bottom line is that it lets you treat a complex content management system like a simple database via chat prompts.
Who Is Agility CMS MCP For?
Frontend developers who hate writing boilerplate API code, SEO specialists who need to map out site opportunities fast, or content managers who just want to audit their whole site structure without logging into the admin panel.
Building a new feature page. You ask for the structural modules of a target page ID so you can write the frontend code directly, bypassing manual investigation.
Mapping out content gaps or checking site crawlability. You request the flat router graph to verify every single URL is properly registered and discoverable.
Auditing a large content library. You ask the system to list all articles within a specific reference type, or count how many authors exist before starting an overhaul.
What Changes When You Connect
- Stop guessing about site structure. Use
get_site_flat_routerorget_site_treeto map every single URL and its relationship in minutes, not hours. - Need development assets? Run
get_page_layoutto get the exact UI modules needed for a page ID, saving you from manual inspection of the CMS backend. - Keep data fresh. Instead of massive API calls, use
sync_incremental_itemsandsync_incremental_pagesto pull only what changed since your last sync token. - Audit content scale easily. Use
count_reference_itemsorlist_content_itemsto know the full scope of a data set (e.g., how many products exist) without running complex queries. - Find deep articles fast. Instead of browsing, use
search_content_referenceto pinpoint specific keywords across large content pools.
Real-World Use Cases
Auditing Missing Content
An SEO specialist suspects a section of the site is missing pages. They run get_site_flat_router via their agent to instantly see every registered route and confirm if the expected slug exists in the master list.
Building a New Feature Page
A front-end developer needs to replicate an existing page's look. They use get_page_layout on the target page ID and get the exact module names (Hero Banner, Features Grid) they need to build the component library.
Checking Content Status
A content manager needs to verify if a specific article has been updated. They use sync_incremental_items with the latest token and check the payload for their item ID, confirming its current status.
Researching Product Lines
A product team wants to know how many articles are about 'AI ethics'. They use search_content_reference against the 'blog_posts' list and get a precise count of relevant entries immediately.
The Tradeoffs
Assuming full visibility
The developer assumes that running list_content_items will give them the structured data needed for a component, but it only provides raw payloads.
→
They should first run get_page_layout to understand the structure (e.g., 'Needs: Hero Banner') and then use list_content_items combined with that knowledge to fetch content payloads.
Over-relying on live API access
A user constantly hits the main CMS endpoints, which quickly runs into rate limits or causes unnecessary load.
→
Use sync_incremental_items first. This tool pulls only changes since your last sync token, minimizing calls and keeping operations stable.
Searching without scope
A user asks to search for 'widget' across the entire CMS, getting thousands of irrelevant results.
→
They must use search_content_reference, specifying the exact list (e.g., blog_posts) where they need to find those keywords.
When It Fits, When It Doesn't
Use this MCP if your primary job involves reading, mapping, or auditing existing content structure and data payloads from Agility CMS. It excels at providing a comprehensive view of site architecture—whether that's the deep nested routes (get_site_tree) or the component breakdown of a single page (get_page_layout). Don't use this if you need to write new content, change settings, or manage user permissions; those actions require different MCPs. If your goal is simply to retrieve static site data, stick with get_site_flat_router. But if you need a deep understanding of how the pieces fit together—the relationships between articles, layouts, and media—this is what you need.
Common Questions About Agility CMS MCP
How do I find out all possible routes on my site using get_site_flat_router? +
The get_site_flat_router tool provides a complete, non-nested list of every single accessible URL. This is perfect for quickly auditing the full scope of your published content.
Can I check if an article was updated since yesterday using sync_incremental_items? +
Yes. sync_incremental_items allows you to pull down only the items that have changed since a given synchronization token, making updates efficient and targeted.
What is the difference between get_site_tree and get_site_flat_router? +
get_site_tree shows you the hierarchy—which pages are nested under others. get_site_flat_router just gives you a simple list of every page, regardless of where it lives on the site.
Does get_page_layout help me build components? +
Yes. The tool retrieves the exact structural modules (like 'Hero Banner' or 'Testimonials') used on a specific page ID, giving you the blueprint needed to replicate it.
When should I use `list_content_items` compared to fetching individual pages with `get_single_item`? +
Use list_content_items for batch operations. This tool returns metadata about many items at once, letting you see what's available across a reference list without needing to know every single content ID up front.
How does using `sync_incremental_pages` improve content synchronization speed? +
It uses a sync token system. Instead of pulling your entire page library, it only fetches any pages that have been updated since the last successful query, saving bandwidth and execution time.
If I need to find articles containing a keyword, how does `search_content_reference` work? +
It queries keywords directly within your defined Content Reference List. This is much more precise than just listing all items because it filters the results based on specific text matches you provide.
What information does `get_media_gallery` provide about my site's images? +
It retrieves structured mappings for your media assets. This tool lets you fetch group details and track gallery structures, so you know exactly which photos belong together on a specific page.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.