What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
Vibe Coding
Give coding agents Agility knowledge with the Agility CMS MCP server, the Knowledgebase MCP server, llms.txt and AGENTS.md. Agility doesn't publish an official skills package.
Coding agents such as Claude Code, Cursor, GitHub Copilot and Gemini CLI do better work on an Agility project when they know how Agility behaves: that saves land in Staging, that lists return 10 items unless you ask for more, that some reference names need exact case. This page shows the ways to give an agent that knowledge today, and what to put in a skill of your own.
There is no official Agility skills package. Agility doesn't publish an installable skills package for coding agents. Use the tools below instead.
Don't install a package or skill that presents itself as an official Agility skill. An unofficial package under an Agility-like name could contain anything, and an agent follows the instructions it loads.
| Tool | What it gives your agent | Setup |
|---|---|---|
| Agility CMS MCP server | Live access to your instances: work with models, content, pages and media, as you, within your Agility permissions | Add the server to your agent and sign in with OAuth |
| Agility Knowledgebase MCP server | Search and read the Agility documentation from inside the agent | Add the server URL to your agent |
llms.txt and Markdown pages | A map of the docs and a clean Markdown copy of every article, for agents that fetch URLs | Nothing to install |
AGENTS.md | Your project's rules, conventions and instance facts, read at the start of every session | A file in your repo |
Use them together. The MCP servers let the agent act and look things up. AGENTS.md and your own skills tell it how to behave in your project.
The Agility CMS MCP server lets an agent work with your Agility instances directly. It is hosted at https://mcp.agilitycms.com/api/mcp, uses OAuth 2.0, and acts only within your existing Agility permissions.
For Claude Code:
claude mcp add --transport http "Agility-CMS" https://mcp.agilitycms.com/api/mcp
For one-click installs and setup steps for other clients, see mcp.agilitycms.com/instructions and Agility CMS MCP Server.
Two things to tell your agent:
save_content_items always saves to the instance's default workflow state, usually Staging, and ignores any state you pass. Saved items are not live until they are published.AGENTS.md.The Knowledgebase MCP server is a separate, read-only server that searches this documentation. For Claude Code:
claude mcp add agility-knowledgebase --transport http https://docs.agilitycms.com/docs/api/mcp
It has two tools, search_docs and fetch_doc. For other clients, see Agility Knowledgebase MCP Server.
If your agent can fetch URLs, it doesn't need an MCP server to read the docs:
https://agilitycms.com/docs/llms.txt lists the documentation pages, with links to their Markdown copies..md to its URL, for example https://agilitycms.com/docs/developers/content-fetch-api.md.Add a line to AGENTS.md such as "For Agility questions, read https://agilitycms.com/docs/llms.txt and fetch the .md version of the relevant article" so the agent uses the docs instead of guessing.
AGENTS.md is where your agent learns your project's rules and your instance's facts. Keep one canonical file and make tool-specific files such as CLAUDE.md point to it.
Some coding agents can load a skill: a folder of instructions, and optionally scripts or reference files, that the agent uses when a task calls for it. Claude Code, for example, loads a skill from a SKILL.md file in a folder under .claude/skills/ (Claude Code skills). Check your agent's documentation for its format.
Skills suit tasks you repeat, such as "create a news article through the MCP server" or "add a component model and its React component". Link each skill from AGENTS.md. These Agility facts are worth including in any skill that reads or writes content:
| Rule | Why | Source |
|---|---|---|
Pass take explicitly on list requests, and page with skip | Content Fetch API lists return 10 items by default, with a maximum of 250 per request | Fetch API reference: get list |
| Saves go to Staging. Publish only when your project allows it | save_content_items ignores state and saves to the default workflow state | Agility CMS MCP Server |
| Publishing a page doesn't publish its components | Publish the component content too, then check the live page | MCP and Agility Gotchas |
| On an update, send every field | An update replaces the whole item, so fields you leave out are wiped | MCP and Agility Gotchas |
Use reference names exactly as get_containers returns them | The read API returns container reference names lowercased. When writing a User Selectable linked-content field, use the exact case get_containers returns | MCP and Agility Gotchas |
Send null for release and pull dates unless you mean to schedule | A pull date that is already past takes an item down as soon as it would go live | MCP and Agility Gotchas |
| Read back what you saved | Confirms nothing was lost in the save | MCP and Agility Gotchas |
Keep instance-specific facts, such as your instance GUID, container IDs and reference names, in AGENTS.md rather than in a skill, so one skill works across projects.