Agility CMS MCP. Query your entire CMS structure in natural language.
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 Server connects your AI client directly to your Agility CMS instance. You can query, list, and structure content using natural language.
This server lets your agent retrieve nested sitemaps, count content items in specific references, and fetch exact page layouts by ID, skipping manual API calls.
What your AI agents can do
Count reference items
Counts the total number of items available in a specified content reference list.
Get media gallery
Retrieves a specific media gallery mapping containing grouped photos.
Get page layout
Retrieves the module breakdown and structural layout for a single page ID.
Get the full sitemap tree or a flat list of every registered CMS route for a channel.
Search for keywords or count the total number of items within a specific content reference list (e.g., all blog posts).
Retrieve the exact module breakdown and structural layout definitions for a specific page ID.
Read the full content data for a single item or list content items from a reference list.
Pull only the content items or pages that have changed since a specified sync token.
Fetch specific media asset groups and tracking galleries used for site imagery.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Agility CMS MCP Server: 10 Tools for Content Architecture
These tools let your agent analyze, list, search, and synchronize content data directly from your Agility CMS instance.
019d7549count reference items
Counts the total number of items available in a specified content reference list.
019d7549get media gallery
Retrieves a specific media gallery mapping containing grouped photos.
019d7549get page layout
Retrieves the module breakdown and structural layout for a single page ID.
019d7549get single item
Fetches the full content payload for one specific content item using its ID.
019d7549get site flat router
Retrieves the complete, flat list of all registered CMS routes and pages.
019d7549get site tree
Gets the nested sitemap architecture for a defined digital channel.
019d7549list content items
Lists all content items from a designated Agility CMS Reference list (e.g., all blog posts).
019d7549search content reference
Searches for specific keywords inside a designated content reference list.
019d7549sync incremental items
Gets content items that have been updated since a specified sync token, minimizing data transfer.
019d7549sync incremental pages
Gets pages that have been updated since a specified sync token, ensuring content freshness.
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,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
Agility CMS MCP Server connects your AI client straight to your Agility CMS. You can query, list, and structure your content using natural language. Your agent gets the data it needs without running manual API calls. get_site_tree pulls the nested sitemap architecture for any channel. get_site_flat_router gives you a complete, flat list of every CMS route and page. list_content_items pulls all content items from a designated CMS reference list, like all blog posts.
You can search_content_reference for specific keywords inside those reference lists. count_reference_items tells you the total item count for any specified content reference list. get_single_item fetches the entire content payload for one item using its ID, while get_page_layout retrieves the module breakdown and structural layout for a single page ID. You'll also get specific media asset groups and grouped photos using get_media_gallery.
To keep things current, sync_incremental_items fetches content items updated since a sync token, and sync_incremental_pages gets pages updated since that token.
How Agility CMS MCP Works
- 1 Subscribe to the server and provide the required credentials (Agility GUID, Locale, API Key).
- 2 Direct your AI agent to perform a query (e.g., 'Show me the layout for Page ID 12' or 'List all authors').
- 3 The server executes the necessary tool calls and returns the structured data payload to your agent.
The bottom line is: you tell your agent what content you need, and it handles the complexity of talking to Agility CMS.
Who Is Agility CMS MCP For?
Frontend developers building UIs need quick access to page modules and sitemaps. Content managers need to audit content lists and check page structures without clicking through the UI. SEO specialists need to map the entire site router graph to find content gaps.
Gets an instant breakdown of page modules and sitemaps while building a new frontend component.
Audits content lists, searches for specific entries, and checks page structures directly via natural language queries.
Analyzes the flat site router graph to map out content opportunities and identify missing pages.
What Changes When You Connect
- Map the full site structure with
get_site_treeorget_site_flat_router. See every nested sitemap or every single route, making content gaps obvious. - Instantly audit content volume using
count_reference_items. Know exactly how many products or authors exist without running manual reports. - Debug page components with
get_page_layout. See the exact UI modules (Hero Banner, Features Grid) mapped to a specific Page ID. - Keep data current by running
sync_incremental_itemsorsync_incremental_pages. Only pull what changed, cutting down on API payload size. - Find content fast. Use
search_content_referenceto find specific keywords across large collections of items, like articles or products. - Manage media assets with
get_media_gallery. Fetch specific groups of photos and galleries needed for front-end development.
Real-World Use Cases
Auditing Content Gaps
The SEO specialist needs to know if the 'Pricing' page has a dedicated sitemap entry. They ask their agent to run get_site_flat_router. The agent returns the full list, showing if the route exists or if it's missing from the CMS map.
Building a New Product Page
The frontend developer needs to know the exact components for a product detail page. They prompt the agent to use get_page_layout with the page ID. The agent returns a list of modules (e.g., 'Image Carousel', 'Specs Table'), allowing the developer to code the structure immediately.
Finding a Specific Article
A content manager needs to verify if an old press release exists. They tell their agent to search_content_reference in the 'Press Releases' list for the keyword 'Q3'. The agent finds the item ID and can then use get_single_item to pull the full text payload.
Syncing Content Changes
A developer needs to update the app's content cache. Instead of downloading every item, they ask the agent to run sync_incremental_items using the last known sync token. The agent pulls only the updated records, saving bandwidth and time.
The Tradeoffs
Running full data dumps
Trying to manually query the entire CMS content list every time to check for changes. This is slow, expensive, and risks hitting API rate limits.
→
Always use the incremental sync tools. Use sync_incremental_items or sync_incremental_pages with your last sync token. This gets only what changed, keeping the data flow fast and efficient.
Treating content as one blob
Attempting to pull all site structure and content data with a single, generic API call. This fails because site structure (sitemap) and content details (article body) have different data models.
→
Break the task down. First, use get_site_tree to map the structure. Then, use list_content_items or get_page_layout to pull specific content details for the nodes you found.
Guessing page modules
Assuming a page uses a standard 'Hero' component without checking the actual configuration. This leads to broken frontends and manual debugging.
→
Use get_page_layout with the specific Page ID. This tool returns the precise module mapping (e.g., 'Testimonial Block' and 'CTA Footer'), so you build exactly what's configured.
When It Fits, When It Doesn't
Use this if you need to understand the relationship between your content pieces—if you need to know the structure (sitemap) or the specific components (page layout). You need the answer to questions like, 'What pages exist?' or 'What modules does this page use?'
Don't use this if you only need to write content or manage user accounts (use a dedicated content writing tool). Also, don't use it if you need to write or publish content; these tools are purely for reading and querying. For simple data lookup that doesn't involve structure, get_single_item works, but for anything involving site architecture, this server is necessary.
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.
Available Capabilities
Manually mapping site structure is a nightmare of clicks and tabs.
Right now, understanding your CMS structure means logging into the admin dashboard, navigating the sitemap tool, and clicking through nested folders until you find the page you need. You're constantly cross-referencing IDs and trying to figure out if a route is live or just drafted. It's slow, and you'll miss things.
With the Agility CMS MCP Server, you just ask your agent: 'What are all the routes under the /products section?' The agent runs `get_site_tree` and gives you the complete, nested map immediately. You get the whole picture in one go.
Agility CMS MCP Server: Fetch Page Layouts with `get_page_layout`
Before, if you wanted to build a new page, you'd have to look at a live example, guess which modules were used, and then manually verify the component mapping in a separate UI tool. It was guesswork, and it was slow.
Now, you ask your agent to use `get_page_layout` and give it the Page ID. It returns a precise list of modules—like 'Hero Banner' and 'Testimonials'—so you know exactly what code to write. No more guessing.
Common Questions About Agility CMS MCP
How do I check if a specific page exists using the `get_site_flat_router` tool? +
The get_site_flat_router tool retrieves a simple, flat list of every registered CMS route. If the route you are looking for is not in that list, it doesn't exist on the site.
What is the difference between `list_content_items` and `search_content_reference`? +
list_content_items gives you every item in a list (like all authors). search_content_reference lets you filter that list by keyword (e.g., finding authors who wrote about 'AI').
Can I get the full content using `get_single_item`? +
Yes. get_single_item fetches the full content payload for a single item, giving you all the data fields, not just the title or summary.
How do I update my content cache efficiently? +
Use the sync tools. Run sync_incremental_items or sync_incremental_pages with your last sync token. This only pulls data that changed, which is much faster and less resource-intensive than a full pull.
Do I need to use `get_site_tree` or `get_site_flat_router` for general site mapping? +
It depends on the format you need. Use get_site_tree if you need the nested, hierarchical map (like a folder structure). Use get_site_flat_router if you just need a simple, list of every single URL.
When should I use `get_page_layout` versus `get_single_item`? +
You use get_page_layout to understand the structure of a page, not its content. It shows the modules (like Hero Banner or Features Grid) mapped to a Page ID. get_single_item fetches the actual text and media payload for a specific content piece, like an article body.
If I need to track content changes, how do I use `sync_incremental_items`? +
You use sync_incremental_items to get only the content that changed since your last check. Just provide the last sync token (or 0 for a full pull). This saves bandwidth and speeds up large-scale content audits.
What should I pass to `get_site_tree` if I want to map a specific department's section? +
You must pass the exact channel name to get_site_tree. This tool retrieves the nested sitemap architecture for that specific channel, letting you map out a department's content tree.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Portable.io
Manage your Portable ETL pipelines directly via your AI agent — monitor flows, sync runs, and destination details seamlessly.
IPQualityScore (IPQS)
Detect fraud, proxies, and malicious activity via IPQS API.
CrewAI Platform
Orchestrate multi-agent workflows via CrewAI — list crews and agents, kickoff autonomous runs, and monitor task execution directly from any AI agent.
You might also like
GivingFuel
Retrieve donation orders, track registrants, and oversee fundraising pages via AI agents with GivingFuel.
Open Brewery DB
Discover breweries across the United States — search by name, city, state, or type with addresses, phone numbers, and websites for every location.
Mod.io
Manage game mods, browse titles, and handle subscriptions via mod.io — discover, rate, and organize game content directly from any AI agent.