# How to connect Agility CMS to Hermes Agent (paste one key, 9 tools) > Connect Agility CMS to Hermes with ClawLink: paste your Agility CMS key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/agility-cms Most guides for giving Hermes Agent Agility CMS access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Agility CMS setup: pair once in the browser and your always-on Hermes agent can act on Agility CMS for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Agility CMS. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Agility CMS** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect agility-cms # connect Agility CMS (browser OAuth) npx -y @useclawlink/cli actions agility-cms # list available actions npx -y @useclawlink/cli run agility-cms --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Agility CMS in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Agility CMS API key once. Verify the connection by asking Hermes: > Pull the relevant data from Agility CMS, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Agility CMS is connected in the dashboard, that agent calls the same 9 Agility CMS tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Agility CMS MCP for Hermes Looking for a Agility CMS MCP server for Hermes Agent? ClawLink connects Agility CMS to Hermes Agent and exposes 9 Agility CMS tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Agility CMS integration](https://claw-link.dev/openclaw/agility-cms) works the same way. ## What the Hermes Agent Agility CMS integration can do 9 Agility CMS tools are ready for Hermes Agent once the account is connected. ### All 9 Agility CMS tools for Hermes | Tool | What it does | |---|---| | **Get API types** `agility_cms_get_api_types` | Retrieve all enum types used throughout the Agility CMS Management API | | **Get content item** `agility_cms_get_content_item` | Fetch details of a content item by Content ID | | **Get content list** `agility_cms_get_content_list` | Retrieves a paginated list of content items by reference name from Agility CMS | | **Get content models** `agility_cms_get_content_models` | Retrieve content models and page modules | | **Get logs** `agility_cms_get_logs` | Retrieve sync items (content change logs) from Agility CMS using the Content Sync API | | **Get page** `agility_cms_get_page` | Retrieve details of a Page, including metadata, content zones, and components | | **Get page modules** `agility_cms_get_page_modules` | Retrieves page module definitions from Agility CMS | | **Get sitemap flat** `agility_cms_get_sitemap_flat` | Retrieves the flat sitemap for a specific channel and locale in Agility CMS | | **Sync pages** `agility_cms_sync_pages` | Retrieves all page items from Agility CMS in paged format with sync tokens for incremental | ## Example prompts **Get Api Types** > Pull the relevant data from Agility CMS, summarize it in plain English, and point out anything that needs attention. **Get Content Item** > Pull the relevant data from Agility CMS, summarize it in plain English, and point out anything that needs attention. **Get Content List** > Pull the relevant data from Agility CMS, summarize it in plain English, and point out anything that needs attention. **Get Content Models** > Pull the relevant data from Agility CMS, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Agility CMS working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Agility CMS API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Agility CMS account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Agility CMS. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Agility CMS actions to the runtime in a format your agent can reliably use. | 9 tools for Agility CMS are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Agility CMS to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Agility CMS in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Agility CMS key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Agility CMS Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect Agility CMS from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Agility CMS tools Agility CMS tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Agility CMS call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Agility CMS returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Agility CMS has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Agility CMS integration? Yes. ClawLink is the fastest way to connect Hermes to Agility CMS: link your Agility CMS account once in the browser and Hermes Agent can call the Agility CMS API through 9 ready-made tools — no custom code or token handling. ### How do I connect Agility CMS to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Agility CMS in the dashboard and Hermes can use it from the next message — no config files, and the Agility CMS key you paste is stored server-side instead of in your environment. ### How long does it take to connect Agility CMS to Hermes Agent? About two minutes. Sign in, click Connect next to Agility CMS in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Agility CMS up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Agility CMS working from chat. ### Hermes paired but still can't use Agility CMS Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [GitHub tools](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.