Can my agent keep track of incremental updates to my CMS items?

Yes. The agent has tools specifically designed to fetch incremental updates using a sync token. It can request only the CMS items or pages that have changed (created, updated, or deleted) since the last automated sync, optimizing fetch latency.

How do I find the correct Reference Name to query content?

Reference Names match the identifiers predefined in your Agility CMS Models architecture (such as 'articles', 'authors', or 'posts'). If you are unsure, ask the agent to scan common variables based on your company's naming conventions.

Can my agent preview unpublished drafting content?

That depends on the API Token you supply during the integration. If you provide a Preview API Key, the agent will have read-access to the staging and drafted documents. If you provide a Fetch API key, it will only see published items.

Agility CMS MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Agility CMS
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Agility CMS and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "agility-cms": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Agility CMS MCP Server

Connect your Agility CMS instance to your AI agent and turn it into the ultimate Headless CMS assistant. Skip manual API queries and interact directly with your content architecture using natural language.

Claude Desktop is the definitive way to connect Agility CMS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Sitemap & Routing — Retrieve nested sitemap trees or flat router architectures to understand how your channels are structured
Content Lists — Search, list, and count items across specific CMS references like articles, authors, or products
Page Layouts — Fetch exact page modules, UI components mapping, and structural layout definitions using Page IDs
Content Operations — Read full content payloads for individual items and synchronize granular CMS updates over time
Media Galleries — Fetch specific media asset groups and tracking galleries for imagery

The Agility CMS MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Agility CMS to Claude Desktop via MCP

Follow these steps to integrate the Agility CMS MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Agility CMS

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Agility CMS MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Agility CMS through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Agility CMS + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Agility CMS MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Agility CMS MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Agility CMS to Claude Desktop via MCP:

count_reference_items

Get the total size/count of items in a specific Reference List

get_media_gallery

Retrieve a specific media gallery mapping containing photos

get_page_layout

Retrieve the layout and structural modules of a single Page

get_single_item

g., an article body) knowing its numeric content ID. Retrieve a single Agility CMS content item by its ID

get_site_flat_router

Retrieve the exact flat list of all CMS routes/pages

get_site_tree

Requires the target channel name. Retrieve the nested sitemap architecture of a digital channel

list_content_items

g. blog posts, articles, authors). The items are retrieved from the Headless CMS environment. List content items from an Agility CMS Reference list

search_content_reference

Search for specific keywords inside a Content Reference List

sync_incremental_items

Start with 0 for full backup. Get incrementally updated items since the last sync token

sync_incremental_pages

Start with 0 for a full fetch. Get incrementally updated pages since the last sync token

Example Prompts for Agility CMS in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Agility CMS immediately.

"Get the flat sitemap for our website to see all registered routes."

"Search the 'blog_posts' reference list for the keyword 'announcement'."

"Retrieve the full page layout and modules for page ID 12."

Troubleshooting Agility CMS MCP Server with Claude Desktop

Common issues when connecting Agility CMS to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Agility CMS + Claude Desktop FAQ

Common questions about integrating Agility CMS MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.