Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect Agility CMS to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (15)

15 tools

Fifteen 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.

When it helps
you manage three client sites and want Claude to confirm which one it is about to look at.
Watch out
it only shows instances your own Agility access already covers.

Sourceagilitycms.com · June 19, 2026 ↗

get_component_model_details

Returns the full field schema of one component model, always with its numeric model ID, which other calls rely on.

When it helps
a hero module renders oddly and you want to see exactly which fields it expects.
Watch out
it covers component models only; content models have their own schema tool.

Sourceagilitycms.com · June 19, 2026 ↗

get_component_models

Lists the component models, the page modules editors drop into zones, including the built-in components Agility ships with.

When it helps
a designer asks which ready-made blocks already exist before sketching a new one.
Watch out
you get the list of names; the field layout of each needs the schema tool.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
you inherit a site and have no idea whether the testimonials sit in a list or in one shared item.

Sourceagilitycms.com · June 19, 2026 ↗

get_content_item

Retrieves one item, or several at once in a batch, from their IDs, with all their field values.

When it helps
an editor pastes three item IDs from a broken page and you want to see what they contain.
Watch out
you need the IDs up front; to browse without them, use the list tool.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
you want every press release from the newsroom list published this year.
Watch out
big containers arrive page by page; ask Claude to keep going if you need them all.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
you want to know whether the event model already has a registration link field before asking for one.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
an audit of the schema starts and you want the full inventory of models in one answer.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
a colleague set up the connector on a shared machine and you want to be sure the session runs under your name.

Sourceagilitycms.com · June 19, 2026 ↗

get_locales

Returns the language and region codes configured on one instance, such as the English and French variants of a site.

When it helps
before a translation push, you want the exact locale codes Claude should target.
Watch out
it works per instance, so pick the right one first.

Sourceagilitycms.com · June 19, 2026 ↗

get_page

Fetches one page by its ID, including its zones, its SEO fields and its dynamic configuration.

When it helps
a landing page lost its meta description and you want to see what is stored on it right now.
Watch out
it takes a page ID, so Claude may read the sitemap first to find it.

Sourceagilitycms.com · June 19, 2026 ↗

get_page_models

Lists the page models, Agility's page templates, along with the zones each one defines.

When it helps
you plan a new landing and want to know which template offers a two-column zone.
Watch out
zone names matter later: a page saved against the wrong one gets refused.

Sourceagilitycms.com · June 19, 2026 ↗

get_sitemap

Reads a specific sitemap, with filters on depth or path and a flat mode that returns the tree as a single list.

When it helps
you want every page under the product section, three levels deep, before a navigation review.

Sourceagilitycms.com · June 19, 2026 ↗

get_sitemaps

Lists every sitemap of an instance, which Agility also calls channels, so Claude knows how the site tree is split.

When it helps
a site has a main channel and a microsite, and you need to tell them apart before touching pages.

Sourceagilitycms.com · June 19, 2026 ↗

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.

When it helps
the brand team suspects the same logo was uploaded five times under different names.

Sourceagilitycms.com · June 19, 2026 ↗

What Claude changes (12)

12 tools

Twelve tools that write to Agility. Publishing, unpublishing and deleting carry a documented confirmation.

delete_content_item

Asks you first

Removes one or several content items from the instance.

What Claude asks for
Agility requires you to type DELETE to confirm before anything is removed.
When it helps
an expired promotion left a dozen offer cards that should disappear from every list.
Watch out
on clients without that form, your Agility rights are the only barrier.

Sourceagilitycms.com · June 19, 2026 ↗

delete_media

Asks you first

Removes one asset from the media library, identified by its media ID.

What Claude asks for
Agility asks you to type DELETE to confirm the removal.
When it helps
the duplicate logos found earlier should go, keeping only the approved version.

Sourceagilitycms.com · June 19, 2026 ↗

delete_page

Asks you first

Deletes one or several pages from a sitemap.

What Claude asks for
you confirm by typing DELETE before the pages are removed, per Agility's documentation.
When it helps
an old microsite section was replaced and its pages keep showing up in internal search.

Sourceagilitycms.com · June 19, 2026 ↗

initialize_media_upload

Approval: see the rule

Opens a media upload and hands back a temporary signed address where the file must then be posted.

What Claude asks for
nothing tool-specific is described; the general approvals rule applies.
When it helps
a new product shot has to go into the library before a page can use it.
Watch out
it only prepares the upload; the file itself still has to be sent to that address.

Sourceagilitycms.com · June 19, 2026 ↗

manage_content_workflow

Asks you first

Moves items through Agility's workflow: publish, unpublish, approve, decline or request approval.

What Claude asks for
Agility gates publish and unpublish behind a confirmation before they run; approve, decline and request approval go through without one.
When it helps
a batch of articles is ready and you want them live before the newsletter goes out.

Sourceagilitycms.com · June 19, 2026 ↗

manage_page_workflow

Asks you first

Handles the workflow of pages: publish, unpublish, approve, decline or request approval.

What Claude asks for
publishing or unpublishing a page asks for your confirmation first; the other three actions are not gated.
When it helps
a seasonal landing page should come offline the day the campaign ends.

Sourceagilitycms.com · June 19, 2026 ↗

reorder_page_modules

Approval: see the rule

Changes the order of the modules inside one zone of a page, without editing the modules themselves.

What Claude asks for
no confirmation is documented for this one; see the general rule in the approvals block.
When it helps
the testimonial strip should sit above the pricing table on the home page.

Sourceagilitycms.com · June 19, 2026 ↗

save_component_model

Approval: see the rule

Creates or updates a component model, the definition behind a page module editors can place in zones.

What Claude asks for
no confirmation specific to this tool is documented; the general approvals rule below covers it.
When it helps
developers need a pricing table module with a highlighted column option.

Sourceagilitycms.com · June 19, 2026 ↗

save_container

Approval: see the rule

Creates a container or updates one, the list or single item where content of a given model is stored.

What Claude asks for
nothing specific is documented for this tool, so the default approvals rule applies.
When it helps
a new podcast section needs its own list before episodes can be added.

Sourceagilitycms.com · June 19, 2026 ↗

save_content_items

Approval: see the rule

Stores 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.

What Claude asks for
no dedicated confirmation is described; the approvals section below explains the default.
When it helps
you have twenty product blurbs rewritten in the chat and want them stored in one go.
Watch out
saving is not publishing: items still need the workflow tool to go live.

Sourceagilitycms.com · June 19, 2026 ↗

save_content_model

Approval: see the rule

Creates a content model or updates an existing one, which changes the fields every item of that type can hold.

What Claude asks for
Agility describes no check of its own for model changes, so Claude's default approval rule is what applies.
When it helps
marketing wants a new case study type with a client quote field.
Watch out
changing a model reaches every item that uses it, so review the field list with care.

Sourceagilitycms.com · June 19, 2026 ↗

save_page

Approval: see the rule

Builds 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 for
Agility documents no dedicated prompt for saving a page; the default rule in the approvals block governs it.
When it helps
you want a new event landing page built from an existing template and filled from the chat.
Watch out
Agility now refuses modules aimed at a zone the template lacks, rather than silently dropping them.

Sourceagilitycms.com · June 19, 2026 ↗

Approvals

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.

Plans

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.

Limits

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

Need help connecting Agility CMS to Claude?

A person reads every message.

FAQ

Claude Agility CMS connector: frequent questions

01What can Claude do with the Agility CMS connector?
Claude can read and author content across your Agility instances from a conversation. Its 27 tools list instances, locales, containers and sitemaps, open content, component and page models, fetch items and pages, and browse the media library. On the writing side, they save models, containers, items and pages, reorder page modules, run the publish and approval workflow, start media uploads, and delete items, pages or assets. It also switches between several instances under one account in the same chat.
02Can Claude publish or delete content in Agility CMS?
Yes, twelve tools write to Agility, including publishing and deleting. The two workflow tools publish, unpublish, approve, decline or request approval for items and pages. Three delete tools remove content items, pages or media assets. The others save models, containers, items and pages, reorder modules and open a media upload. All of them stay within your own Agility permissions, so an account that cannot publish in Agility cannot publish through Claude either.
03Does Claude ask before publishing or deleting in Agility CMS?
Yes for the riskiest actions, according to Agility. Publishing and unpublishing wait for your confirmation, and deleting asks you to type DELETE. Approve, decline and request approval are not gated. For saving items, pages or models, no source describes a specific check, so Claude's default rule applies: it asks before acting on your account. Choosing always allow in your client removes a tool's prompt, and owners on Team or Enterprise decide what members may skip.
04Which Claude plans is the Agility CMS connector available on?
No official source publishes plan availability connector by connector, and no directory sheet displays it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner enabling each connector first on Team and Enterprise workspaces. Agility's own page does not name any Claude plan. The Agility CMS sheet in the official directory is the only place showing the current state for your account.
05Does Claude see every instance in our Agility account?
Claude sees the instances your own Agility account can reach, and nothing beyond that. The connector signs in as you and inherits your existing permissions, so a user with read-only access stays read-only and cannot save or publish through Claude. The identity tool even lets you check which user the session runs as. On the Claude side, a Team or Enterprise owner can further restrict what the connector may do for everyone, and members cannot lift that restriction themselves.
06Why did Claude not ask me before publishing in Agility CMS?
Most likely because always allow was chosen for that tool in your client, a setting that lives on your side. Agility marks publishing and deleting as destructive, so clients prompt before running them, but ticking always allow opts out of that prompt, and the server cannot force it back. Where a client cannot show Agility's confirmation form at all, the action runs with your own sign-in and Agility's API enforces your rights instead.
07Claude or an automation tool for Agility CMS?
They cover different jobs, so it depends on the task. Claude works inside a conversation: you ask, it reads, drafts, saves or publishes, and nothing else happens once you stop typing. It never reacts on its own to a saved draft or an approval request. For a background process that runs whenever something changes in the CMS, an automation tool does that job. For schema audits, batch edits and one-off publishing on demand, the connector fits better.