# How to connect Mezmo to Hermes Agent (paste one key, 36 tools) > Connect Mezmo to Hermes with ClawLink: paste your Mezmo key once and 36 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/mezmo Most guides for giving Hermes Agent Mezmo 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 Mezmo setup: pair once in the browser and your always-on Hermes agent can act on Mezmo 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 Mezmo. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Mezmo** — 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 mezmo # connect Mezmo (browser OAuth) npx -y @useclawlink/cli actions mezmo # list available actions npx -y @useclawlink/cli run mezmo --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 Mezmo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mezmo API key once. Verify the connection by asking Hermes: > Pull the relevant data from Mezmo, 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 Mezmo is connected in the dashboard, that agent calls the same 36 Mezmo 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). ## Mezmo MCP for Hermes Looking for a Mezmo MCP server for Hermes Agent? ClawLink connects Mezmo to Hermes Agent and exposes 36 Mezmo 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 Mezmo integration](https://claw-link.dev/openclaw/mezmo) works the same way. ## What the Hermes Agent Mezmo integration can do 36 Mezmo tools are ready for Hermes Agent once the account is connected. The 29 below are the ones people reach for most; your agent can call all 36. ### 29 of 36 Mezmo tools for Hermes | Tool | What it does | |---|---| | **Get alert** `mezmo_get_alert` | Retrieve details of a specific preset alert by its ID | | **Get category** `mezmo_get_category` | Retrieve a category configuration by its type and ID | | **Get index rate alert** `mezmo_get_index_rate_alert` | Retrieve current index rate alert settings for the Mezmo account | | **Get ingestion exclusion** `mezmo_get_ingestion_exclusion` | Retrieve an ingestion exclusion rule by its ID | | **Get ingestion status** `mezmo_get_ingestion_status` | Get the current ingestion status for the Mezmo account | | **Get key** `mezmo_get_key` | Retrieve an API key configuration by its ID | | **Get member** `mezmo_get_member` | Retrieve member information by their ID | | **Get stream config** `mezmo_get_stream_config` | Retrieve the current event streaming configuration for the Mezmo account | | **Get view** `mezmo_get_view` | Retrieve details of a specific view by its ID | | **List alerts** `mezmo_list_alerts` | List all preset alerts configured for the Mezmo account | | **List keys** `mezmo_list_keys` | List all API keys and ingestion keys configured for the account | | **List members** `mezmo_list_members` | List all team members in the Mezmo account configuration | | **List pipelines** `mezmo_list_pipelines` | List all telemetry pipelines configured for the account | | **List views** `mezmo_list_views` | List all views configured for the account | | **Create category** `mezmo_create_category` | Create a new category for views, boards, or screens in Mezmo | | **Create ingestion exclusion** `mezmo_create_ingestion_exclusion` | Create an exclusion rule for log ingestion to control costs | | **Create key** `mezmo_create_key` | Create a new API key (ingestion or service key) in Mezmo | | **Create member** `mezmo_create_member` | Invite a new member to the Mezmo organization with a specified role | | **Create preset alert** `mezmo_create_preset_alert` | Create a new preset alert in Mezmo with specified name and notification channels | | **Create view** `mezmo_create_view` | Create a new Mezmo view with filtering and alert configuration | | **Ingest logs** `mezmo_ingest_logs` | Ingest log lines into Mezmo Log Analysis | | **Resume ingestion** `mezmo_resume_ingestion` | Resume log ingestion for the account after it has been stopped | | **Update category** `mezmo_update_category` | Update a category name by its type and ID | | **Update index rate alert** `mezmo_update_index_rate_alert` | Configure index rate alerting settings including thresholds and notification channels | | **Update ingestion exclusion** `mezmo_update_ingestion_exclusion` | Update an existing exclusion rule by its ID | | **Update key** `mezmo_update_key` | Update an API key name by its ID | | **Update member** `mezmo_update_member` | Update a member's role and group assignments by their email address | | **Update preset alert** `mezmo_update_preset_alert` | Update an existing preset alert by ID | | **Update view** `mezmo_update_view` | Update an existing Mezmo view by its ID | ## Example prompts **Get Alert** > Pull the relevant data from Mezmo, summarize it in plain English, and point out anything that needs attention. **Get Category** > Pull the relevant data from Mezmo, summarize it in plain English, and point out anything that needs attention. **Get Index Rate Alert** > Pull the relevant data from Mezmo, summarize it in plain English, and point out anything that needs attention. **Get Ingestion Exclusion** > Pull the relevant data from Mezmo, 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 Mezmo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Mezmo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mezmo 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 Mezmo. | 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 Mezmo actions to the runtime in a format your agent can reliably use. | 36 tools for Mezmo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Mezmo 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 Mezmo in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the Mezmo 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 Mezmo 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 Mezmo 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 Mezmo tools Mezmo 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 Mezmo 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. ### Mezmo 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 Mezmo 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 Mezmo integration? Yes. ClawLink is the fastest way to connect Hermes to Mezmo: link your Mezmo account once in the browser and Hermes Agent can call the Mezmo API through 36 ready-made tools — no custom code or token handling. ### How do I connect Mezmo 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 Mezmo in the dashboard and Hermes can use it from the next message — no config files, and the Mezmo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Mezmo to Hermes Agent? About two minutes. Sign in, click Connect next to Mezmo in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Mezmo 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 Mezmo working from chat. ### Hermes paired but still can't use Mezmo 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 - [Hermes GitHub integration](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](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.