# Agility CMS MCP for AI Agents AI Agent Connect > Agility CMS MCP lets you query and manage your headless CMS content using natural language. Skip the manual API calls and let your AI agent navigate sitemaps, fetch page layouts, and search content lists directly. It turns your content architecture into a conversational interface for faster development and content auditing. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_5eswiSmSUebcV9cwXlY54rj1CtGkp8fDqrTfU030/ai-agent-connect - **Tags:** api-first, content-architecture, sitemap-management, digital-experience, content-delivery ## Description Agility CMS MCP lets you query and manage your headless CMS content using natural language. Instead of digging through complex API documentation or manually clicking through the Agility CMS dashboard to find a specific page layout, you can just ask your agent to do the heavy lifting. This gives your AI client a direct line to your content architecture. You can have it map out your entire site structure, find specific content blocks, or pull the exact media gallery for a new landing page without ever leaving your workspace. It makes managing a headless CMS feel like talking to a teammate who knows the system inside out. By connecting this through Vinkius, you get a reliable way to bridge the gap between your content data and your development workflow. It's about getting the right data at the right time so you can focus on building instead of hunting for IDs. You don't have to worry about keeping track of numeric IDs or navigating deep nested folders just to see how a page is structured. Your agent handles the navigation and returns the specific payloads you need to keep moving. It turns your content into a searchable resource that works for you, not the other way around. ## Tools ### count_reference_items See the total number of items in a specific content list. This helps you quickly check the size of your data sets. ### get_media_gallery Pull a specific group of photos and media assets. Use it to grab all the imagery for a specific section. ### get_single_item Fetch the full content payload for one specific item using its ID. This is the fastest way to grab a single article or product. ### get_page_layout Get the structural modules and UI components for a single page. Use this to see exactly how a page is built. ### get_site_flat_router Fetch a complete list of every route and page in your CMS. It is perfect for getting a high-level view of your site map. ### get_site_tree Get the nested sitemap architecture for a specific channel. It helps you understand how your content is organized hierarchically. ### list_content_items Pull a list of items from a specific CMS reference list. Use this to browse through your blog posts or products. ### search_content_reference Look for specific keywords inside a content reference list. This makes finding specific entries much faster than manual filtering. ### sync_incremental_items Get only the items that have changed since your last sync. It is the most efficient way to keep your local data fresh. ### sync_incremental_pages Fetch only the updated pages since your last sync token. Use this to keep your site router up to date without re-downloading everything. ## Prompt Examples **Prompt:** ``` What modules are on the home page? ``` **Response:** ``` The home page (Page ID 1) uses the 'StandardTemplate' and contains the following 4 UI modules: | Module Name | Type | Description | | :--- | :--- | :--- | | Hero Banner | Image | Main header section | | Features Grid | List | 3-column feature highlights | | Testimonials | Carousel | Customer reviews | | Call to Action | Button | Newsletter signup | ``` **Prompt:** ``` Search for 'summer' in the products list. ``` **Response:** ``` I found 4 items in the 'products' list that match 'summer': * **Summer Sale Banner** (ID 902) * **Beach Towel Set** (ID 1045)* **Sunscreen Bundle** (ID 1120) * **Summer Hat Collection** (ID 1205) Would you like me to fetch the full content for any of these? ``` **Prompt:** ``` Give me a list of all the URLs on the site. ``` **Response:** ``` I have retrieved the flat router map. Here are the registered routes for the 'website' channel: * /home * /about * /products * /blog * /contact * /summer-sale * /support Total routes found: 7 ``` ## Capabilities ### Map sitemap trees Retrieve nested sitemap architectures to see how your channels are organized. ### Search content lists Find specific entries within your CMS references using keywords. ### Fetch page layouts Get the exact UI modules and component mappings for any page ID. ### Sync content updates Pull incrementally updated pages and items to keep your data fresh. ### Retrieve media galleries Get specific asset groups and imagery mappings for your pages. ## Use Cases ### Quick Layout Checks A developer asks for the modules on the home page. The agent uses get_page_layout to show the Hero and Feature blocks. This helps them understand the structure before they start writing the frontend code. ### Content Audits A manager searches for 'summer' in the blog list. The agent uses search_content_reference to find all matching posts. This makes it much faster to verify that the correct content is live. ### SEO Mapping An SEO lead asks for a list of all URLs. The agent uses get_site_flat_router to provide a full site map. This helps them identify content gaps and plan new URL structures. ### Local Data Sync A developer needs to update their local cache of content. The agent uses sync_incremental_items to pull only the newest entries, keeping the local environment accurate without heavy API calls. ## Benefits - Stop hunting for IDs: Use get_single_item to pull content payloads instantly without navigating the dashboard. This saves you from having to remember or copy-paste specific content IDs every time you need to verify a layout. - Faster frontend builds: Use get_page_layout to see exact UI module mappings while you code. You can understand the structure of a page before you even start building the frontend components. - Easier content audits: Use search_content_reference to find keywords across your entire content library. This makes it easy to find specific posts or products without manual filtering in the CMS. - Efficient data syncing: Use sync_incremental_pages to keep your local data fresh without full re-downloads. This saves on API overhead and keeps your local environment accurate. - Clearer site architecture: Use get_site_tree to see how your channels are organized in a nested structure. It gives you a clear picture of how your content is grouped. - Rapid sitemap analysis: Use get_site_flat_router to get a full list of routes for navigation planning. This is a huge time saver for SEO audits and site mapping. ## How It Works The bottom line is you get a conversational interface for your headless CMS data. 1. Provide your Agility CMS GUID, Locale, and API Key to connect the Connector. 2. Grant your AI client permission to access your specific content references. 3. Ask your agent to fetch sitemaps, layouts, or content lists in plain English. ## Frequently Asked Questions **Can I use Agility CMS MCP to create new content?** No, this Connector is designed for querying and fetching existing content. You can use it to read layouts, sitemaps, and lists, but you should use the Agility CMS dashboard to create or edit content. **How does Agility CMS MCP help with SEO?** It helps SEO specialists quickly map out the site's URL structure and sitemaps. You can ask your agent to list all routes or show the nested site tree to find content gaps. **Can my agent find specific page layouts with this Connector?** Yes, your agent can pull the exact structural modules and UI component mappings for any page. This is great for developers who need to see how a page is built while they are coding. **Does Agility CMS MCP support media galleries?** Yes, it can retrieve specific media gallery mappings. This allows your agent to find and list specific groups of photos or images for your pages. **Is Agility CMS MCP good for syncing content?** Yes, it includes tools to sync only the updated pages or items. This makes it efficient for keeping your local environment in sync with the CMS without downloading everything every time. **Can I search for keywords in my content lists?** Yes, you can ask your agent to search for specific keywords inside any content reference list. It will return the matching items from your headless CMS environment. **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.