Agility CMS
Agility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms.
Verdict
Common use cases
- Audit published pages before a launch
- List all authors contributing to a locale
- Check which content models are defined
- Review recent sync logs for publishing errors
- Fetch metadata for a specific content item
Integration
- Vendor
- Agility CMS
- Category
- other
- Auth
- API_KEY
- Tools
- 12
- Composio slug
agility_cms
Tools
- Get Authors
Tool to retrieve all authors from an agility cms instance. use when you need the full list of authors for display or processing.
- Get Categories
Tool to get all categories. use when you need to list every category in a given locale.
- Get Content Item
Tool to fetch details of a content item by content id. use when you need item fields and metadata from agility cms.
- Get Content List
Tool to retrieve a list of content items by reference name. use when you need to fetch and page through content list data with optional filtering, sorting, and link expansions.
- Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
- Get Logs
Tool to retrieve sync items (logs) from agility cms. use after initial full sync to fetch updates.
- Get Page
Tool to retrieve details of a page, including metadata, content zones, and components. use after you know the page id to fetch.
- Get Page Modules
Tool to retrieve all page modules defined in the agility instance. use when you need only modular definitions without content models.
- Get Sitemap Flat
Tool to retrieve the flat sitemap as a mapping of page paths to sitemap items. use when you need page routing logic after knowing locale and channel.
- Get Tags
Tool to get all tags. use when you need to list every tag in a given locale.
- Sync Content Items
Tool to retrieve all content items in a paged format with sync tokens. use when you need to synchronize large volumes of content and maintain state across calls.
- Sync Pages
Tool to retrieve all page items in paged format with sync tokens. use when synchronizing local page data after receiving cms change notifications.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Agility CMS in the MCP directory and click Connect. 3. You'll be prompted to paste an API key — generate one in your Agility CMS dashboard under Settings > API Keys with at least read permissions for content and pages. 4. Enter your Agility instance GUID (found in the same API Keys section) so Switchy knows which CMS to query. 5. Click Save and wait for the green confirmation. 6. Open any Space, type '@Agility CMS list all categories in en-us' and hit send — if you see category names appear, the connection works. 7. From now on, @mention Agility CMS in any message to invoke its tools and pull live CMS data into your conversation.
What teammates see: by default, memories from Agility CMS are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Categories
@Agility CMS get all categories in the en-us locale and show me their names and IDs.Open in a Space →
Inspect a Page
@Agility CMS fetch the page with ID 42 and summarize its content zones and attached modules.Open in a Space →
Check Content Models
@Agility CMS retrieve all content models and page modules, then show me which fields each model defines.Open in a Space →
Review Sync Logs
@Agility CMS get the latest sync logs and highlight any errors or warnings in the last 24 hours.Open in a Space →
Find Content by Reference
@Agility CMS retrieve the content list named 'blog-posts', sort by date descending, and show the five most recent entries.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@agility list all blog posts from the last month, sorted by publish date, and show me the author names
Retrieved 23 blog posts from your 'BlogPosts' content list published between December 15, 2024 and January 15, 2025. The list includes post titles, publish dates, and expanded author details. Top recent posts: 'Migrating to Headless CMS' by Sarah Chen (Jan 12), 'Content Modeling Best Practices' by Marcus Rodriguez (Jan 10), and 'API-First Architecture' by Sarah Chen (Jan 8). Each entry includes the content ID, slug, and full author metadata for further processing or display.
This example demonstrates content list retrieval with filtering, sorting, and link expansion (authors). The MCP requires your Agility CMS API key with read access to the specified content list. Response shape depends on your instance's content model schema—field names and structure will vary by your configuration.
@agility fetch the full page structure for the homepage, including all content zones and their modules
Retrieved page details for 'Home' (page ID: 42). The page contains three content zones: 'MainContent' with a Hero module and FeaturedPosts module, 'Sidebar' with a Newsletter module, and 'Footer' with ContactInfo and SocialLinks modules. Each module includes its reference name, content ID, and zone placement order. The page metadata shows it's published in the 'en-us' locale with SEO title 'Welcome to Our Site' and meta description populated.
This read-heavy example showcases the Get Page tool's ability to map content architecture. Useful for debugging layout issues or programmatically rebuilding page structures. The MCP returns structural metadata but not the actual content within each module—you'd need separate Get Content Item calls to fetch module content fields.
@agility analyze our content models and suggest which ones are missing required SEO fields like meta descriptions
Analyzed 8 content models from your Agility instance. Found 3 models lacking dedicated SEO fields: 'BlogPost' has title and body but no metaDescription field; 'CaseStudy' has no metaTitle or metaDescription; 'ProductPage' includes metaTitle but is missing metaDescription and ogImage fields. The 'LandingPage' and 'ArticlePage' models both have complete SEO field sets (metaTitle, metaDescription, ogImage, canonical). Consider adding a reusable 'SEOMetadata' content model that other models can reference.
This synthesis example pairs the Get Content Models tool with AI reasoning to audit your content architecture. The MCP provides schema definitions (field names, types, required flags); the AI interprets gaps based on SEO best practices. This is read-only analysis—the MCP cannot modify content models, only surface their structure for review.
Use-case deep-dives
When Agility CMS wins for quarterly content reviews
A 5-person marketing team runs quarterly audits of their product site—checking which pages reference outdated authors, which categories have stale content, and which modules are still in use. The Get Authors, Get Categories, and Get Page Modules tools let them pull the full inventory in minutes, then cross-reference it against their editorial calendar in a shared Switchy workspace. The Get Logs tool keeps the audit current by syncing only what changed since last quarter. This works best when your site has under 500 pages and a stable content model; beyond that threshold, the sync can lag and you'll want a dedicated CMS analytics layer. If your team already lives in Agility's dashboard, this MCP is overkill—but if you're coordinating audits across Notion, Linear, and Slack, it's the fastest way to surface CMS data where decisions happen.
When this MCP clarifies schema for frontend teams
A 3-person dev team is building a Next.js storefront against Agility's headless API and needs to understand which content models and page modules exist before they write components. The Get Content Models tool pulls the full schema—field types, validation rules, nested references—so the frontend engineer can stub out TypeScript interfaces without waiting for the backend team to document them. Get Page retrieves the actual content zone structure for a given route, which helps the developer see how modules nest in production. This scenario assumes the team has API key access and the CMS instance is already configured; if you're still in the design phase or the content model changes daily, this MCP won't keep pace. For teams shipping a headless site in a 2-week sprint, it's the fastest way to align on data contracts.
When Agility CMS helps support reps find KB articles fast
A 6-person support team fields tickets about product features and needs to reference help articles stored in Agility CMS. The Get Content List tool lets them search by reference name and filter by category, so a rep can pull the latest troubleshooting guide without leaving the Switchy workspace where they're drafting the ticket response. Get Content Item fetches the full article body and metadata when they need to verify publish dates or author attribution. This works when your KB has under 200 articles and a predictable taxonomy; if you're managing thousands of articles or need full-text search, Agility's native search or a dedicated KB tool like Zendesk Guide will be faster. For small teams who already use Agility for marketing content and want to reuse it in support workflows, this MCP closes the loop.
Frequently asked
What does the Agility CMS MCP let me do in Switchy?
It pulls content, pages, authors, categories, and schema definitions from your Agility CMS instance into Switchy conversations. Your team can query live headless CMS data, inspect page structures, and fetch content items without opening the Agility dashboard. Useful for content audits, debugging page builds, or feeding CMS data into AI workflows.
Do I need admin access to connect Agility CMS?
You need an API key with read permissions for the content you want to query. Agility CMS issues keys at the instance level, so whoever generates the key controls which locales and content types Switchy can see. You don't need full admin rights, but the key must have scope to read authors, pages, and content models.
Can the Agility CMS MCP publish or update content?
No. The eight tools are all read-only: they fetch authors, categories, pages, content items, models, and sync logs. If you need to publish or edit content, use Agility's dashboard or their management API directly. This MCP is for querying and inspecting existing content, not writing it.
How is this different from calling the Agility API myself?
You skip writing pagination logic, handling link expansions, and stitching together multi-step queries. The MCP wraps Agility's REST endpoints so your AI can ask "show me all blog posts in French" and get back structured data in one step. Faster for ad-hoc queries; less flexible than a custom integration.
Who on my team should connect the Agility CMS integration?
Whoever manages your Agility instance and can generate a read-scoped API key. Typically a content ops lead or developer. Once connected, anyone in your Switchy workspace can query the CMS data in conversations, so you only need one person to set it up.