ClawLink

How to connect Cody to Hermes Agent

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.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Cody
Cody
CodyAPI KEYMCP

Cody is an AI-powered assistant that uses the magic of ChatGPT meets the expertise of a custom-made AI assistant trained on your specific business.. Once connected, Hermes Agent can read and act on Cody from chat — pairing, token refresh, and tool wiring handled for you.

21 tools

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. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Cody

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Cody?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

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 — 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:

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.

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, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Cody integration 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

ToolWhat it does
Get conversation cody_get_conversationFetch a conversation by its ID from Cody AI
Get document cody_get_documentRetrieve a specific document by its identifier from Cody AI
Get folder cody_get_folderRetrieve a specific folder by its identifier
Get message cody_get_messageFetch a specific message by its ID from Cody AI
Get uploads signed URL cody_get_uploads_signed_urlGet an AWS S3 signed upload URL for file uploads
List bots cody_list_botsGet all bots with optional keyword filtering
List conversations cody_list_conversationsGet all conversations with optional filtering by bot, keyword, or includes
List documents cody_list_documentsRetrieve all documents from Cody AI account with optional filtering
List folders cody_list_foldersRetrieve all folders with optional keyword filtering
List messages cody_list_messagesRetrieve a paginated list of messages from Cody, optionally filtered by conversation
Create conversation cody_create_conversationCreate a new conversation with a specified bot
Create document cody_create_documentCreate a new document with text or HTML content in Cody AI
Create document from file cody_create_document_from_fileCreate a document by uploading a file (up to 100 MB)
Create document from webpage cody_create_document_from_webpageCreate a document from a publicly accessible webpage URL
Create folder cody_create_folderCreate a new folder in Cody AI for organizing content
Send message cody_send_messageSend a message to Cody AI and receive an AI-generated response
Send message for stream cody_send_message_for_streamSend a message to Cody AI and receive a Server-Sent Events (SSE) stream URL for the AI response
Update conversation cody_update_conversationUpdate a conversation by its ID including name, bot_id, and document_ids
Update folder cody_update_folderUpdate a folder by its ID

Try it: find the Cody tool you need

Browse the 19 Cody tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Cody, summarize it in plain English, and point out anything that needs attention.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou 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.

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 comparison.

Troubleshooting

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.

FAQ

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.