# How to connect Cody to Hermes Agent (paste one key, 21 tools) > Connect Cody to Hermes with ClawLink: paste your Cody key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/cody Most guides for giving Hermes Agent Cody 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 Cody setup: pair once in the browser and your always-on Hermes agent can act on Cody 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 Cody. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Cody** — 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 cody # connect Cody (browser OAuth) npx -y @useclawlink/cli actions cody # list available actions npx -y @useclawlink/cli run cody --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 Cody in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cody API key once. Verify the connection by asking Hermes: > Pull the relevant data from Cody, 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 Cody is connected in the dashboard, that agent calls the same 21 Cody 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). ## Cody MCP for Hermes Looking for a Cody MCP server for Hermes Agent? ClawLink connects Cody to Hermes Agent and exposes 21 Cody 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 Cody integration](https://claw-link.dev/openclaw/cody) works the same way. ## What the Hermes Agent Cody integration can do 21 Cody tools are ready for Hermes Agent once the account is connected. The 19 below are the ones people reach for most; your agent can call all 21. ### 19 of 21 Cody tools for Hermes | Tool | What it does | |---|---| | **Get conversation** `cody_get_conversation` | Fetch a conversation by its ID from Cody AI | | **Get document** `cody_get_document` | Retrieve a specific document by its identifier from Cody AI | | **Get folder** `cody_get_folder` | Retrieve a specific folder by its identifier | | **Get message** `cody_get_message` | Fetch a specific message by its ID from Cody AI | | **Get uploads signed URL** `cody_get_uploads_signed_url` | Get an AWS S3 signed upload URL for file uploads | | **List bots** `cody_list_bots` | Get all bots with optional keyword filtering | | **List conversations** `cody_list_conversations` | Get all conversations with optional filtering by bot, keyword, or includes | | **List documents** `cody_list_documents` | Retrieve all documents from Cody AI account with optional filtering | | **List folders** `cody_list_folders` | Retrieve all folders with optional keyword filtering | | **List messages** `cody_list_messages` | Retrieve a paginated list of messages from Cody, optionally filtered by conversation | | **Create conversation** `cody_create_conversation` | Create a new conversation with a specified bot | | **Create document** `cody_create_document` | Create a new document with text or HTML content in Cody AI | | **Create document from file** `cody_create_document_from_file` | Create a document by uploading a file (up to 100 MB) | | **Create document from webpage** `cody_create_document_from_webpage` | Create a document from a publicly accessible webpage URL | | **Create folder** `cody_create_folder` | Create a new folder in Cody AI for organizing content | | **Send message** `cody_send_message` | Send a message to Cody AI and receive an AI-generated response | | **Send message for stream** `cody_send_message_for_stream` | Send a message to Cody AI and receive a Server-Sent Events (SSE) stream URL for the AI response | | **Update conversation** `cody_update_conversation` | Update a conversation by its ID including name, bot_id, and document_ids | | **Update folder** `cody_update_folder` | Update a folder by its ID | ## Example prompts **Get Conversation** > Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention. **Get Document** > Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention. **Get Folder** > Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention. **Get Message** > Pull the relevant data from Cody, 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 Cody working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cody API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cody 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 Cody. | 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 Cody actions to the runtime in a format your agent can reliably use. | 21 tools for Cody are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cody 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 Cody in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Cody 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 Cody 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 Cody 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 Cody tools Cody 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 Cody 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. ### Cody 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 Cody 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 Cody integration? Yes. ClawLink is the fastest way to connect Hermes to Cody: link your Cody account once in the browser and Hermes Agent can call the Cody API through 21 ready-made tools — no custom code or token handling. ### How do I connect Cody 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 Cody in the dashboard and Hermes can use it from the next message — no config files, and the Cody key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cody to Hermes Agent? About two minutes. Sign in, click Connect next to Cody in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Cody 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 Cody working from chat. ### Hermes paired but still can't use Cody 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 - [Connect DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Hermes Chatbotkit integration](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Hermes Just One API integration](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.