Fetches content items by ID or reference name, resolves page paths through the flat sitemap, and pulls the change log since the last sync token.
9actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves a paginated list of content items by reference name from Agility CMS. Support agents can search and reference published content during conversations.
Ayro retrieves all page items from Agility CMS with sync tokens for incremental updates. Ayro keeps page data fresh without fetching everything from the CMS each time.
Each card is one request a support team gets, and the Agility cms actions Ayro runs to close it.
Ayro fetches the item by Content ID, or pages through a content list by reference name in the locale the customer is reading, expanding linked content where the answer depends on it.
The flat sitemap maps every page path to its metadata, SEO fields, and routing details, so Ayro resolves the URL for a channel and locale and can open the page to read its content zones.
Before querying, Ayro pulls the content models to find which reference names an instance exposes, checks which page modules are available, and reads the enum values behind status and permission fields.
Ayro walks the sync API with a stored token, taking content changes in pages of up to 500 items and page updates alongside them, until the token comes back as 0 and the view is current.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Agility cms actions it has and picks the ones a request needs.
Authorize the Agility cms account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Agility cms actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeAgility cms · Ayro
What can you do in Agility cms without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Agility cms.
No. All nine actions read: Get Content Item, Get Content List, Get Page, Get Sitemap Flat and the rest fetch from the Management, Content, and Sync APIs without writing back. Editors keep working in Agility, and Ayro answers from whatever they have published.
All 9 actions your agent can call on Agility cms, straight from the live MCP connection.
Retrieve all enum types used throughout the Agility CMS Management API.
Fetch details of a content item by Content ID.
Retrieves a paginated list of content items by reference name from Agility CMS.
Retrieve content models and page modules.
Retrieve sync items (content change logs) from Agility CMS using the Content Sync API.
Retrieve details of a Page, including metadata, content zones, and components.
Retrieves page module definitions from Agility CMS.
Retrieves the flat sitemap for a specific channel and locale in Agility CMS.
Retrieves all page items from Agility CMS in paged format with sync tokens for incremental updates.
Same connection, same setup. Pick the next one your team already uses.
Prices and places transcription orders against the prepay balance, returns finished transcripts in four formats, and cancels unstarted files for refund.
Creates, duplicates, and updates document automations, checks the generation queue, and reports where signing sessions stand.
Sends signature requests, reports where each signer stands, chases the ones still outstanding, and cancels or re-sends what went out wrong.
Merges documents into a print job, posts it as physical mail, tracks its progress, and cancels an unshipped job for a refund.
Parses documents into structured data, generates PDFs from pages and emails, merges and splits files, and finds and removes sensitive text.
Lists the document types configured on the account and reads or updates the authenticated user's profile fields.

Authorize the account and your agent has all 9 actions from the first conversation.
