- Home
- Resources
- Integrations
- Agility CMS
Claude Agility CMS connectorWhat Claude can do in your Agility CMS account.
The Claude Agility CMS connector exposes 27 tools. 15 read your instances, models, pages and media, 12 change them. Below: what Claude can author and publish, which actions Agility gates behind a typed confirmation, and where your own permissions set the limit.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your content team
Instead of clicking through the admin screens of a headless CMS, you describe the change in plain words and Claude calls the right Agility tool. It can read your schema, draft and store items, build pages from templates, and push them through the workflow. Publishing and deleting stop for a confirmation first.
Audit the schema in one conversation. get_content_models and get_content_model_details lay out every model and its fields, so you spot the duplicate author types before a redesign.
Ship a batch of updates. save_content_items stores many items in one call, new ones and existing ones alike, and manage_content_workflow publishes them once you say yes to the prompt.
Assemble a page from a template. get_page_models shows which zones a template offers, save_page builds the page and reorder_page_modules fixes the module order.
What it will not do: nothing runs by itself. No tool fires when an editor saves a draft or a scheduled date arrives; Claude acts only while you talk to it. It cannot exceed your Agility role: a read-only user stays read-only. And the media tool only opens an upload slot, it does not carry the file. For event-driven jobs, look at an automation tool instead; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while plugging Agility CMS in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, revocable anytime.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as your CMS.
Connect Agility CMS to Claude in three steps
- 01
Find Agility CMS in Claude
In Claude's settings, open Customize, then Connectors, and look for Agility CMS in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Agility in the window Agility opens on its side. If the link ever breaks, use Disconnect and connect again from the same row.
- 03
Read the authorization screen
Go through Agility's access screen before approving. It belongs to the service, not to Claude, and it defines what the access covers. That access can be withdrawn later from the Agility side too.
The 27 Claude Agility CMS connector tools, sorted by what they do
Agility CMS gives Claude 27 tools: 15 that read your account, 12 that change something in it.
Two groups: what Claude reads, and what it changes. Names stay exactly as Claude shows them.
- 15 read
- 12 write
Tools index
What Claude reads (15)
15 toolsFifteen tools that look at instances, schema, pages and media without touching them.
get_available_instances
Lists every Agility instance your account can reach, which is the starting point when an agency or a group runs several brands side by side.
get_component_model_details
Returns the full field schema of one component model, always with its numeric model ID, which other calls rely on.
get_component_models
Lists the component models, the page modules editors drop into zones, including the built-in components Agility ships with.
get_containers
Lists the content containers of an instance, both multi-item lists and single items, so Claude knows where each type of content lives.
get_content_item
Retrieves one item, or several at once in a batch, from their IDs, with all their field values.
get_content_items
Pulls a list of items out of a container, with filters and pagination, so large collections come back in pages instead of all at once.
get_content_model_details
Opens one content model and returns its full field schema, field by field, so Claude knows what an item of that type must contain.
get_content_models
Brings back the definitions of your content models, the blueprints that decide which fields a blog post, a product card or an author record carries.
get_current_user
Tells you which Agility user the current connection is signed in as. Agility calls it a read-only check, and it never returns any credential.
get_locales
Returns the language and region codes configured on one instance, such as the English and French variants of a site.
get_page
Fetches one page by its ID, including its zones, its SEO fields and its dynamic configuration.
get_page_models
Lists the page models, Agility's page templates, along with the zones each one defines.
get_sitemap
Reads a specific sitemap, with filters on depth or path and a flat mode that returns the tree as a single list.
get_sitemaps
Lists every sitemap of an instance, which Agility also calls channels, so Claude knows how the site tree is split.
list_media
Browses the media library page by page and returns each asset with its CDN address, handy for finding a media ID or spotting duplicates.
What Claude changes (12)
12 toolsTwelve tools that write to Agility. Publishing, unpublishing and deleting carry a documented confirmation.
delete_content_item
Asks you firstRemoves one or several content items from the instance.
delete_media
Asks you firstRemoves one asset from the media library, identified by its media ID.
delete_page
Asks you firstDeletes one or several pages from a sitemap.
initialize_media_upload
Approval: see the ruleOpens a media upload and hands back a temporary signed address where the file must then be posted.
manage_content_workflow
Asks you firstMoves items through Agility's workflow: publish, unpublish, approve, decline or request approval.
manage_page_workflow
Asks you firstHandles the workflow of pages: publish, unpublish, approve, decline or request approval.
reorder_page_modules
Approval: see the ruleChanges the order of the modules inside one zone of a page, without editing the modules themselves.
save_component_model
Approval: see the ruleCreates or updates a component model, the definition behind a page module editors can place in zones.
save_container
Approval: see the ruleCreates a container or updates one, the list or single item where content of a given model is stored.
save_content_items
Approval: see the ruleStores one or many content items in a single batch, new or existing. Agility returns each item's ID and a direct link to open it in the editor.
save_content_model
Approval: see the ruleCreates a content model or updates an existing one, which changes the fields every item of that type can hold.
save_page
Approval: see the ruleBuilds a new page or updates one, whether static, dynamic, a folder or a link, and checks zone names against the page template.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. Agility adds its own gates on the riskiest moves.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can cap what a connector may do for the whole organization, keeping reads and closing writes. Agility's own layer sits on top: publish and unpublish ask for confirmation, deletes ask you to type DELETE. Picking always allow in your client removes that prompt for the tool. And Claude only reaches what your Agility account already can.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. Connector by connector, the answer is published nowhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the up-to-date state, the Agility CMS sheet in the official directory is the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a draft is saved, a date passes or an editor requests approval.
Only the publisher documents this connector: no Claude help article covers it, so the details here come from Agility's developer page. The tool list is an observed floor, not a promise. The partner badge is not a security audit either, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. For another connector that works on structured records, see the Claude airtable connector.
Need help connecting Agility CMS to Claude?
A person reads every message.