Agility CMS MCPサーバー
コミット 2026年11月14日自然言語での対話を通じて、AIクライアントがAgility CMSインスタンス内のコンテンツ、モデル、ページ、メディアにアクセスし、管理できるようにします。
別名 agility/mcp-server
- スター
- 0
- ツール
- 33
- ダウンロード数(30日間)
- —
- 最新バージョン
- 2.12.13
- 最終コミット
- 2026年11月14日
- ライセンス
- Apache-2.0
Agility CMS MCPとは
自然言語での対話を通じて、AIクライアントがAgility CMSインスタンス内のコンテンツ、モデル、ページ、メディアにアクセスし、管理できるようにします。 33個のツールを提供しており、get_available_instances, get_current_user, get_containersなどがあります。
プロジェクトのREADMEから生成された概要
Agility CMS MCP server について
このホストされたMCP serverは、Agility CMSのユーザーが自然言語を通じてデジタル資産やコンテンツ構造を管理することを可能にします。AIクライアントをリモートエンドポイントに接続することで、開発者やコンテンツマネージャーは、手動でAPIコールを記述することなく、既存のAgilityインスタンスと対話してコンテンツ、モデル、ページ、メディアを操作できます。
サーバーはstreamable HTTPを介して動作し、認証にはOAuth 2.0を使用します。つまり、ユーザーは個別のAPIキーを管理するのではなく、自身のAgilityアカウントでサインインします。この構成により、AIアシスタントは組織内で各ユーザーに既に割り当てられている特定の権限を遵守します。
33個の異なるツールが利用可能で、サーバーはコンポーネント、コンテナ、サイトマップなどの管理のための深い統合を提供します。Claude、Cursor、VS Code、ChatGPT、LM Studioを含む幅広いクライアントと互換性があり、CMSデータとの直接的な対話インターフェースを実現します。
できること
- 1Agilityインスタンスの調査利用可能なAgilityインスタンスを特定するようAIアシスタントに依頼できます。
- 2コンテンツとメディアの管理自然言語を使用して、既存のコンテンツ、モデル、メディアファイルにアクセスし、整理できます。
- 3CMSワークフローの自動化ページの構築や、公開準備ができているかのコンテンツ確認など、複雑なタスクをAIクライアントに指示できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
Agility CMS MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにAgility CMS MCPをインストール
$ claude mcp add --transport http mcp-server https://mcp.agilitycms.com/api/mcpCursorにAgility CMS MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.agilitycms.com/api/mcp"
}
}
}VS CodeにAgility CMS MCPをインストール
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://mcp.agilitycms.com/api/mcp"
}
}
}VS Code CLIにAgility CMS MCPをインストール
$ code --add-mcp '{"name":"mcp-server","type":"http","url":"https://mcp.agilitycms.com/api/mcp"}'CodexにAgility CMS MCPをインストール
$ codex mcp add mcp-server --url https://mcp.agilitycms.com/api/mcpCodex config.tomlにAgility CMS MCPをインストール
~/.codex/config.toml
[mcp_servers.mcp-server] url = "https://mcp.agilitycms.com/api/mcp"
Gemini CLIにAgility CMS MCPをインストール
$ gemini mcp add -s user --transport http mcp-server https://mcp.agilitycms.com/api/mcpGemini settings.jsonにAgility CMS MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.agilitycms.com/api/mcp",
"type": "http"
}
}
}Agility CMS MCPツール 33
READMEから検出get_available_instancesget_current_userget_containerssearch_instanceget_content_modelsget_component_modelsget_content_model_detailsget_component_model_detailsget_localesget_content_itemsget_content_itemsave_content_items
| get_available_instances | — | |
| get_current_user | — | |
| get_containers | — | |
| search_instance | — | |
| get_content_models | — | |
| get_component_models | — | |
| get_content_model_details | — | |
| get_component_model_details | — | |
| get_locales | — | |
| get_content_items | — | |
| get_content_item | — | |
| save_content_items | — |
33個のツールをすべて表示ツールを折りたたむ
publish_contentunpublish_contentmanage_content_workflowdelete_content_itemget_sitemapsget_sitemapget_pageget_page_modelssave_page_modelsave_pagereorder_page_modulespublish_pageunpublish_pagemanage_page_workflowdelete_pageinitialize_media_uploadlist_mediadelete_mediasave_content_modelsave_component_modelsave_container
| publish_content | — | |
| unpublish_content | — | |
| manage_content_workflow | — | |
| delete_content_item | — | |
| get_sitemaps | — | |
| get_sitemap | — | |
| get_page | — | |
| get_page_models | — | |
| save_page_model | — | |
| save_page | — | |
| reorder_page_modules | — | |
| publish_page | — | |
| unpublish_page | — | |
| manage_page_workflow | — | |
| delete_page | — | |
| initialize_media_upload | — | |
| list_media | — | |
| delete_media | — | |
| save_content_model | — | |
| save_component_model | — | |
| save_container | — |
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能agility/mcp-server is public and reachablegithub.com/agility/mcp-server ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-14github.com/agility/mcp-server ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない33 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答HTTPS endpoint answered 401 (sign-in required)合格
README
GitHubで見る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
| Client | How to add it |
|---|---|
| VS Code (GitHub Copilot) | One-click badge above, or Command Palette → MCP: Add Server → HTTP |
| Cursor | One-click badge above, or Settings → MCP → Add new MCP server → HTTP |
| LM Studio | One-click badge above |
| Claude Code | claude mcp add --transport http "Agility-CMS" https://mcp.agilitycms.com/api/mcp |
| Claude (desktop & web) | Official connector — Customize → Connectors → Discover → search Agility CMS → Connect |
| Claude plugin (connector + skills) | claude plugin marketplace add agility/mcp-server then claude plugin install agility-cms@agility |
| ChatGPT | Agility CMS in ChatGPT's plugin directory — add it and sign in |
| Microsoft 365 Copilot | Coming soon — in Microsoft's review |
| Codex | codex mcp add agility-cms --url https://mcp.agilitycms.com/api/mcp then codex mcp login agility-cms |
| Goose | Settings → Extensions → add a remote (streamable HTTP) extension with the endpoint |
| Windsurf | Settings → Cascade → MCP servers → add the endpoint |
| Gemini CLI | gemini mcp add --transport http agility-cms https://mcp.agilitycms.com/api/mcp |
| Anything else | Any client that speaks streamable HTTP — or bridge a stdio-only client with mcp-remote |
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.jsonfrom 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 allowhttps://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 allowhttps://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 Agility instances I can access, then show me the content models in the marketing site."
- "Add a
Subtitletext field to the Blog Post model, under the existing SEO tab." - "Build a Team Member model — name, photo, bio, and a link to their posts — and a container for it."
- "Create a blog post in
en-usfrom this outline and give me the editor link." - "Which pages in the main channel are still unpublished?"
- "Find everything that mentions the spring sale, and open the newest blog post."
- "Publish the three posts I just created."
Data and security
Authentication is OAuth 2.0 against your Agility organization, over HTTPS. There is no API key to paste and nothing to keep in a config file — tokens are held by your MCP client, not by this repo's configuration or any file you edit.
Your Agility permissions are the ceiling. Every call runs as you: the Management API refuses anything you personally can't do, so the server cannot exceed the access you already have. It follows that the practical way to limit what an assistant can reach is to sign in as an Agility user that only has the access you're willing to give it.
Actions that overwrite data or change the live site are marked. The save tools,
reorder_page_modules, delete_*, publish_* and unpublish_* carry destructiveHint: true, so
interactive clients can ask before running them.
Non-interactive clients don't prompt at all — they require each write tool to be allow-listed instead.
Treat content as untrusted input. This is structural to MCP, not specific to Agility: an assistant reads content items, page text and field descriptions, and any of that can contain text that reads like an instruction (prompt injection). A client that acts on it does so with your permissions. Use clients you trust, leave confirmation prompts on for destructive tools, and don't hand a broadly-privileged Agility account to an unattended agent.
What gets logged. The hosted server records operational telemetry to Agility's Application
Insights: the tool or API method called, duration, success or failure, the Agility instance GUID and
your Agility user ID. Request and response payloads are recorded in truncated form for debugging
(capped, 2 KB by default), so small content values can appear in those logs. There is no client-side
opt-out on the hosted server; self-host without APP_INSIGHTS_CONNECTION_STRING to collect nothing.
Available MCP Tools
The Agility CMS MCP Server provides 33 powerful tools organized into categories:
🔍 Discovery Tools
get_available_instances- List all Agility CMS instances you have access toget_current_user- Identify the user the current token authenticates as (read-only whoami)get_containers- Access content containers organized by categorysearch_instance- Search an instance's content, pages, components, assets, models and containers by text or ID
📋 Model Listing Tools
get_content_models- Retrieve all content models for an instanceget_component_models- Access page component models, with each component's thumbnail URL when it has one
🔍 Detail Tools
get_content_model_details- Get detailed field definitions for a content modelget_component_model_details- Get detailed field definitions for a component model, and its thumbnail (a picture of what the component looks like on a page)
📝 Content Management Tools
get_locales- Retrieve available locales for multilingual contentget_content_items- Fetch multiple content items with filtering and paginationget_content_item- Retrieve a single content item by IDsave_content_items- Create or update content items (returns an editor URL per item)publish_content- Publish one or more content itemsunpublish_content- Unpublish (take offline) one or more content items (destructive)manage_content_workflow- Approve, decline, or request approval for content itemsdelete_content_item- Delete content items (destructive)
📄 Page Management Tools
get_sitemaps- List all digital channels (sitemaps)get_sitemap- Retrieve complete page hierarchy for a channelget_page- Retrieve a page by IDget_page_models- List available page models (templates)save_page_model- Create or update a page model (template) and its content zonessave_page- Create or update a pagereorder_page_modules- Reorder modules within a page zonepublish_page- Publish one or more pagesunpublish_page- Unpublish (take offline) one or more pages (destructive)manage_page_workflow- Approve, decline, or request approval for pagesdelete_page- Delete pages (destructive)
🖼️ Media & Asset Tools
initialize_media_upload- Get signed upload URLs for media fileslist_media- List media library assets (paged)delete_media- Delete a media asset by ID (destructive)
⚡ Model Creation & Management Tools
save_content_model- Create or update content modelssave_component_model- Create or update component modelssave_container- Create and configure content containers
🔒 Destructive actions are marked. The save tools,
reorder_page_modules,delete_*,publish_content/publish_pageandunpublish_content/unpublish_pagecarrydestructiveHint: true, so interactive MCP clients prompt before running them ("Allow this tool to run?" — choosing "always allow" opts out). Publishing is marked because it replaces what the live site serves. The approval workflow (approve, decline, request approval) changes nothing live and is not flagged destructive. See Data and security for how permissions and prompting work, and the documentation for the per-tool detail.
📚 Full tool documentation and examples: mcp.agilitycms.com/tools
Supported Field Types
The Agility CMS MCP Server supports 20+ field types for building comprehensive content models:
- 📝 Basic Fields: Text, Long Text, HTML, Boolean, Integer, Decimal, Date
- 🎯 Selection Fields: Dropdown List, Link, Search Listbox, Checkboxes
- 🎨 Media Fields: Image Attachment, File Attachment
- 🔗 Content Relationships: Shared Grid/Link, Nested Grid/Link
- 📂 Organization: Tab Field, Custom Section
- ⚡ Advanced: Complex Object Fields, Custom Field Types, Rich Text Editor
📚 Complete field type documentation: mcp.agilitycms.com/tools
Troubleshooting
| Symptom | Usually means |
|---|---|
An instance is missing from get_available_instances |
Your Agility user doesn't have access to it, or it isn't on the production Agility tenant this server talks to. |
| Calls start failing with an authorization error | The OAuth token expired or was revoked — reconnect the server in your client. |
| The assistant says it can't write, or silently only reads | Non-interactive clients require each write tool to be allow-listed by name. Check your client's tool permissions. |
| A one-click install link does nothing | The editor wasn't running, or it blocked the handoff — add the endpoint by hand instead. |
| A tool rejects a field setting | Agility validates model changes server-side; the error text is passed through verbatim. Linked-content fields, for example, have no required, unique or copyAcrossAllLanguages setting. |
Still stuck: support@agilitycms.com or our Slack community.
Support and feedback
- 🌐 Website: mcp.agilitycms.com
- 📖 Setup Instructions: mcp.agilitycms.com/instructions
- 🛠️ Tool Catalog: mcp.agilitycms.com/tools
- 📚 Agility CMS Docs: agilitycms.com/docs
- 💬 Support: support@agilitycms.com
- 👥 Community: Join our Slack
About this repository
This repository is the public home of the Agility CMS MCP Server — the documentation, the licence
and the security policy for the hosted service at https://mcp.agilitycms.com — and of the
Agility CMS plugin for Claude.
The Claude plugin
plugins/agility-cms bundles the MCP server with skills for
writing and editing content, building pages, publishing, content modeling and front-end development.
Install it in Claude Code:
claude plugin marketplace add agility/mcp-server
claude plugin install agility-cms@agility
The server is a hosted, remote MCP server: there is nothing to install and no package to pull, so there is no build to reproduce here. Its source is maintained by Agility CMS and is not currently published. Everything you need in order to use the server is above.
License
The documentation in this repository is licensed under the Apache License 2.0.
Two things that licence deliberately does not cover:
- The hosted service.
https://mcp.agilitycms.comis operated by Agility CMS under Agility's own terms of service. Your use of the service, and of the Agility CMS Management API behind it, is governed by those terms and your Agility subscription. - The Agility name and marks. Apache 2.0 §6 grants no trademark rights. See NOTICE.
Security reports: SECURITY.md.
Built with ❤️ by Agility CMS — The fastest headless CMS for developers and marketers
Agility CMS MCPのよくある質問
Agility CMS MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --transport http mcp-server https://mcp.agilitycms.com/api/mcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
Agility CMS MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
Agility CMS MCPが提供するツールは
33個のツールを提供しており、get_available_instances, get_current_user, get_containers, search_instance, get_content_modelsなどがあります。
Agility CMS MCP serverを使用するために、何かをインストールする必要がありますか?
いいえ、これはホストされたサーバーであり、URL経由でクライアントを接続するだけで利用可能です。
サーバーは認証と権限をどのように処理しますか?
サーバーはOAuth 2.0を使用します。既存のAgility組織の権限が、すべての操作の権限として適用されます。
このサーバーを使用して、AIはどのようなタスクを実行できますか?
サーバーは33個のツールを提供しており、AIがコンテンツ、モデル、コンポーネント、コンテナ、ページ、サイトマップ、メディアを管理することを可能にします。