Integration

Agility CMS integration

Agility CMS Content Fetch API: read the content of an Agility CMS instance over REST. Get the content models, fetch a content item or a page (by id or by path) with its linked content, read a content list with filters, sorting and paging, read the flat or nested sitemap of a channel, a media gallery, the URL redirections, and sync every content item or page incrementally with a sync token. Read-only: creating, editing and publishing content (the separate Management API) is not included. Authentication is an API key sent in the APIKey header; the instance GUID, the API type (fetch for published content, preview for latest and staging content, each with its own key) and the regional API host are set on the connection.

Connect Agility CMS How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Agility CMS.Built from the 11 Agility CMS tools below, on the connection you add once.

What you can do with Agility CMS

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Page, 3 operations

get_pageGet pageGETReturns a page by its page id: title, name, menu text, template, zones with their modules, SEO, scripts and visibility, with linked content expanded to contentLinkDepth.
get_page_by_pathGet page by pathGETReturns a page by its URL path in a channel: page (title, name, zones with their modules, SEO, scripts, visibility) and sitemapNode (its sitemap entry), with linked content expanded to contentLinkDepth.
sync_pagesSync pagesGETSyncs pages: returns a page of every page (or only those changed since syncToken) in items, and the syncToken to pass next. Start with syncToken 0; a returned syncToken of 0 means you are up to date.

Item, 2 operations

get_content_itemGet content itemGETReturns one content item by its content id in a locale: contentID, properties (state, modified date, version, reference name, definition name) and fields (the item's values), with linked content expanded to contentLinkDepth.
sync_content_itemsSync content itemsGETSyncs content items: returns a page of every content item (or only those changed since syncToken) in items, and the syncToken to pass next. Start with syncToken 0; a returned syncToken of 0 means you are up to date.

Contentmodel, 1 operation

list_content_modelsList content modelsGETLists the content models (definitions) of the instance: each model's id, reference name, display name and fields with their types. Pass lastModifiedDate to get only models changed since then.

Flat, 1 operation

get_sitemap_flatGet sitemap flatGETReturns the sitemap of a channel as one object keyed by page path (for example /about-us), each entry giving the page id, title, name, content id for dynamic pages, redirect and visibility. Suited to page routing.

Gallery, 1 operation

get_galleryGet galleryGETReturns a media gallery by its gallery id: name, description and its media items (url, size, file name, metadata).

List, 1 operation

get_content_listGet content listGETReturns the items of a content list by its reference name, with filters, sorting and paging (Take up to 250, Skip). Returns items and totalCount, the size of the whole filtered list.

Nested, 1 operation

get_sitemap_nestedGet sitemap nestedGETReturns the sitemap of a channel as a nested array (each entry with its children), giving page id, title, name, path, redirect and visibility. Suited to building menus.

Urlredirection, 1 operation

list_url_redirectionsList url redirectionsGETLists the URL redirections set up in the CMS in items, each with id, originUrl, destinationUrl and statusCode (301 or 302), with lastAccessDate. Pass that lastAccessDate on the next call to get only redirections changed since.

Use Agility CMS from Claude Code, Cursor or Codex

Connect Agility CMS in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Agility CMS operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Agility CMS

Create your workspace
Sign up free. Nothing to install.
Connect Agility CMS once
Add your Agility CMS connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.