Agility CMS (BYOK) — connector documentation
- MCP endpoint:
https://byok-agility-cms.connectorbay.com/mcp - REST API:
POST https://byok-agility-cms.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-agility-cms.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Agility CMS Fetch API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-agility-cms.connectorbay.com/health· Tool schemas:https://byok-agility-cms.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-agility-cms · agent@connectorbay.com
What Agility CMS (BYOK) is for
Agility CMS (BYOK) lets an AI assistant read your own Agility CMS data through the Agility CMS API with a key you supply (Fetch API key). Read-only: 7 tools (get_content_list, get_content_item, get_page_by_id, get_page_by_path, get_sitemap_flat, get_content_models, list_url_redirections). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.aglty.io, api-ca.aglty.io, api-eu.aglty.io, api-aus.aglty.io, api-usa2.aglty.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Agility CMS. Agility CMS and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Show the published items of my Agility 'posts' list"
- "Show Agility content item 124"
- "Show Agility page 5"
- "Show the Agility page at /about-us"
- "List the pages of my Agility website by path"
- "What content models does my Agility instance define?"
What it does
get_content_list: Read a content list by its reference name (for example 'posts') from the published content, with each item's ID, state, modified date and fields. Supports paging, sorting and a filter expression.get_content_item: Read one published content item by its numeric content ID, with state, modified date, fields and SEO data.get_page_by_id: Read one published page by its numeric page ID, including its content zones and the modules placed in them.get_page_by_path: Read one published page by its path in a digital channel (for example '/about-us' in 'website'), including its content zones and modules.get_sitemap_flat: Read the flat sitemap of a digital channel: every published page keyed by its path.get_content_models: List the content models and page modules defined in the instance (the shape of each content type). Optionally only those changed since a date.list_url_redirections: List the URL redirections defined in the instance, optionally only those changed since a date.
BYOK key
You bring your own Agility CMS Fetch API key (https://agilitycms.com/docs/training-guide/admin-api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.aglty.io, api-ca.aglty.io, api-eu.aglty.io, api-aus.aglty.io, api-usa2.aglty.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://agilitycms.com/docs/developers/content-fetch-api (the API this connector calls, with a BYOK key)
Live from the Agility CMS API (api.aglty.io, api-ca.aglty.io, api-eu.aglty.io, api-aus.aglty.io, api-usa2.aglty.io) with a BYOK key; documentation: https://agilitycms.com/docs/developers/content-fetch-api. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Agility CMS. Agility CMS and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Agility CMS account.
Built for: Worldwide. Languages: English.