Agilitycms MCP

Agility CMS MCP Server

The official MCP server for Agility CMS: a hosted, remote server that gives your AI tools real-time access to the content, models, pages and media in the Agility instances you already have access to — through conversation, not APIs.

Connect your client · What you can ask for · Tools · Data and security · Troubleshooting · Support

There is nothing to install. Point your client at https://mcp.agilitycms.com/api/mcp, sign in with your Agility account, and your assistant can work with the instances you already have access to.

• Endpoint: https://mcp.agilitycms.com/api/mcp (streamable HTTP)
• Auth: OAuth 2.0 against your Agility organization — your Agility permissions are the authority
• Tools: 33, covering content, models, components, containers, pages, sitemaps and media
• Setup guide with screenshots: mcp.agilitycms.com/instructions
• Live tool catalog: mcp.agilitycms.com/tools

---

Connect your client

One click

Every supported client

Full walkthroughs are at mcp.agilitycms.com/instructions, and rolling it out to a whole team is covered under For your organization. To wire anything up by hand, the only value you need is the endpoint. Details per client follow.

Claude Code

claude mcp add --transport http "Agility-CMS" https://mcp.agilitycms.com/api/mcp

Claude (desktop & web)

Agility CMS is an official connector in Claude's directory, so there is nothing to paste.

On your own account — open the listing, https://claude.com/marketplace/connectors/agility-cms, or inside Claude go to Customize → Connectors → Discover, search for *Agility CMS*, and hit Connect. Then sign in to Agility when prompted.

Pick Agility CMS. *Agility CMS Knowledgebase* is a separate connector for the documentation site and is marked Custom.

Administering a Team or Enterprise workspace — enable the *Agility CMS* connector for the organization from your admin settings. That makes it available to everyone, but it connects nobody: each member still signs in to Agility themselves, and their own Agility permissions govern every call. There is no shared or service credential.

If the directory entry has not reached you yet, the endpoint still works on its own — Customize → Connectors → Add, then add it as a custom connector:

https://mcp.agilitycms.com/api/mcp

The Agility CMS plugin bundles the connector with nine skills (getting started, editing content, writing an article, brand voice, publishing and workflow, building pages, content modeling, a go-live check and building a front end) and the Agility documentation server. It's published from agility/mcp-server. In Claude Code:

claude plugin marketplace add agility/mcp-server

claude plugin install agility-cms@agility

VS Code (GitHub Copilot)

Command Palette → MCP: Add Server → HTTP, then paste the endpoint. Or add to your MCP config:

{

"servers": { "agility-cms": { "type": "http", "url": "https://mcp.agilitycms.com/api/mcp" } } }

Cursor

Settings → MCP → Add new MCP server → type HTTP, URL as above. Or in ~/.cursor/mcp.json:

{

"mcpServers": { "agility-cms": { "url": "https://mcp.agilitycms.com/api/mcp" } } }

LM Studio

Use the one-click badge above, or add the endpoint under Program → Install → Edit mcp.json:

{

"mcpServers": { "agility-cms": { "url": "https://mcp.agilitycms.com/api/mcp" } } }

Windsurf

Settings → Cascade → MCP servers → add a server with the endpoint above.

Gemini CLI

gemini mcp add --transport http agility-cms https://mcp.agilitycms.com/api/mcp

Or in ~/.gemini/settings.json:

{

"mcpServers": { "agility-cms": { "httpUrl": "https://mcp.agilitycms.com/api/mcp" } } }

ChatGPT

Agility CMS is in ChatGPT's plugin directory: https://chatgpt.com/settings/plugins-settings/plugin_asdk_app_6a67c713303881918a19fde42b09777f. Add it, then sign in to Agility when prompted. On a Business, Enterprise or Edu workspace your admin may need to enable it first.

If the plugin isn't available to you, turn on Settings → Apps → Advanced settings → Developer mode, then Create an app with the endpoint above and OAuth.

Microsoft 365 Copilot

Coming soon. Agility CMS for Microsoft 365 Copilot is in Microsoft's review.

Codex

codex mcp add agility-cms --url https://mcp.agilitycms.com/api/mcp

codex mcp login agility-cms

Goose

Use the one-click link on the setup page, or add a remote (streamable HTTP) extension with the endpoint above. Goose opens the Agility sign-in the first time it connects.

Anything else

Any client that speaks streamable HTTP works. Give it the endpoint and let it run the OAuth flow — there is no API key to paste and nothing to keep in a config file.

If a client only supports local (stdio) servers, bridge to it with mcp-remote:

{

"mcpServers": { "agility-cms": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.agilitycms.com/api/mcp"] } } }

That bridge is a general-purpose client-side shim, not an Agility package. There is no `agility-mcp-server` npm package and there won't be one — a hosted HTTP server has nothing to install, so if you find a config telling you to npx something Agility-named, it's wrong.

For your organization

An admin can make Agility CMS available to everyone, or install it for them. None of these grants content access by itself: every person still signs in to Agility once, and their own Agility permissions decide what the assistant can see and change. There is no shared or service credential.

• Claude Team and Enterprise: an Owner adds Agility CMS under Organization settings → Connectors. To install the plugin for everyone, go to Organization settings → Plugins & skills → Add → Sync from GitHub, enter agility/mcp-server, and set its default access to *Available to install*, *Installed by default* or *Required* (per group on Enterprise). The connector still has to be added under Connectors.
• Claude Code: push the plugin with managed settings (Organization settings → Claude Code → Managed settings, or managed-settings.json from your device-management tool), or put the same keys in a checked-in .claude/settings.json:

  {

"extraKnownMarketplaces": { "agility": { "source": { "source": "github", "repo": "agility/mcp-server" } } }, "enabledPlugins": { "agility-cms@agility": true } }

- **ChatGPT Business, Enterprise and Edu:** a workspace admin opens **Workspace settings →

Plugins, finds Agility CMS**, and sets its installation policy to *Available* or *Installed*, workspace-wide or per role (Enterprise and Edu). The Agility CMS app must be enabled under Workspace settings → Apps too.

• Microsoft 365 Copilot (coming soon): once approved, a Microsoft 365 admin turns it on under Copilot → Connectors in the admin center and rolls it out to everyone or to chosen users and groups.
• VS Code and GitHub Copilot: check the VS Code config into a repository as .vscode/mcp.json. GitHub Enterprise admins who restrict MCP servers can allow https://mcp.agilitycms.com/*, or use the GitHub MCP Registry, where Agility CMS is listed.
• Cursor: check the Cursor config into a repository as .cursor/mcp.json. Enterprise admins using Cursor's MCP allowlist can allow https://mcp.agilitycms.com/*.

---

What you can ask for

Once it's connected, talk to your assistant about your content — it will pick the tools. Most tools take an instanceGuid (which Agility instance) and, for content, a locale; ask it to list your instances first and it will use the right one from then on.

• *"List the Agilit