Agility CMS MCP integration for AI agents.
Connect AI agents to Agility CMS through 6 structured actions, including get content item, get content list, and get flat sitemap. Review authentication, inp…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Agility CMS integration exposes
The Agility CMS Agent App exposes 6 provider-backed actions for developer tools and productivity work. Its current contract lets an authorized agent retrieve an agility cms content item by content id for a locale, retrieve an agility cms content list by reference name with optional pagination, filtering, sorting, and linked-content expansion, and retrieve an agility cms flat sitemap keyed by page path for a channel. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Agility CMS account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Agility CMS capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_content_itemREADRetrieve an Agility CMS content item by content ID for a locale.
INPUTS: guid / apiType / locale / id / contentLinkDepth
get_content_listREADRetrieve an Agility CMS content list by reference name with optional pagination, filtering, sorting, and linked-content expansion.
INPUTS: guid / apiType / locale / referenceName / contentLinkDepth
get_flat_sitemapREADRetrieve an Agility CMS flat sitemap keyed by page path for a channel.
INPUTS: guid / apiType / locale / channelName
get_nested_sitemapREADRetrieve an Agility CMS nested sitemap for generating menus or navigation.
INPUTS: guid / apiType / locale / channelName
get_pageREADRetrieve an Agility CMS page by page ID for a locale.
INPUTS: guid / apiType / locale / id / contentLinkDepth
list_content_modelsREADList content models for an Agility CMS instance using the Content Fetch API.
INPUTS: guid / apiType / lastModifiedDate
INPUT CONTRACTS
Know what the action needs before it runs.
get_content_item
guidREQUIRED- The Agility CMS instance GUID from the API Keys section.
apiTypeREQUIRED- The Agility Content Fetch API type to query.
localeREQUIRED- The locale code to retrieve content for.
idREQUIRED- The Agility CMS content ID of the requested item.
contentLinkDepthOPTIONAL- The maximum level to expand linked content.
get_content_list
guidREQUIRED- The Agility CMS instance GUID from the API Keys section.
apiTypeREQUIRED- The Agility Content Fetch API type to query.
localeREQUIRED- The locale code to retrieve content for.
referenceNameREQUIRED- The unique reference name of the content list to retrieve in the current locale.
contentLinkDepthOPTIONAL- The maximum level to expand linked content.
get_flat_sitemap
guidOPTIONAL- The Agility CMS instance GUID from the API Keys section.
apiTypeOPTIONAL- The Agility Content Fetch API type to query.
localeOPTIONAL- The locale code to retrieve content for.
channelNameOPTIONAL- The reference name of the digital channel, such as website.
get_nested_sitemap
guidOPTIONAL- The Agility CMS instance GUID from the API Keys section.
apiTypeOPTIONAL- The Agility Content Fetch API type to query.
localeOPTIONAL- The locale code to retrieve content for.
channelNameOPTIONAL- The reference name of the digital channel, such as website.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Content Item
Retrieve an Agility CMS content item by content ID for a locale. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_content_itemVerify with Get Content List
Retrieve an Agility CMS content list by reference name with optional pagination, filtering, sorting, and linked-content expansion. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_content_listSAFETY BOUNDARY
Operate Agility CMS with explicit limits
- Authorize Agility CMS with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Agility CMS data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Agility CMS rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Agility CMS task completed successfully.
CONNECTION MODEL
API key
Agility CMS API key sent with the APIKey header. Find API keys and instance GUIDs in the API Keys section of your Agility CMS instance: https://agilitycms.com/docs/developers/content-fetch-api
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Agility CMS.