# How to connect Doppler to Hermes Agent (paste one key, 62 tools) > Connect Doppler to Hermes with ClawLink: paste your Doppler key once and 62 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/doppler Most guides for giving Hermes Agent Doppler 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 Doppler setup: pair once in the browser and your always-on Hermes agent can act on Doppler 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 Doppler. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Doppler** — 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 doppler # connect Doppler (browser OAuth) npx -y @useclawlink/cli actions doppler # list available actions npx -y @useclawlink/cli run doppler --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 Doppler in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Doppler API key once. Verify the connection by asking Hermes: > Use Doppler to activity logs list and walk me through the result in plain English. ### 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 Doppler is connected in the dashboard, that agent calls the same 62 Doppler 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). ## Doppler MCP for Hermes Looking for a Doppler MCP server for Hermes Agent? ClawLink connects Doppler to Hermes Agent and exposes 62 Doppler 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 Doppler integration](https://claw-link.dev/openclaw/doppler) works the same way. ## What the Hermes Agent Doppler integration can do 62 Doppler tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 62. ### 30 of 62 Doppler tools for Hermes | Tool | What it does | |---|---| | **Activity logs list** `doppler_activity_logs_list` | List workplace activity logs with pagination support | | **Activity logs retrieve** `doppler_activity_logs_retrieve` | Retrieve detailed information about a specific activity log entry | | **Auth me** `doppler_auth_me` | Retrieve information about the authenticated user or token | | **Config logs get** `doppler_config_logs_get` | Retrieve a specific config log from Doppler | | **Config logs list** `doppler_config_logs_list` | Retrieve configuration change logs for a specific config in a project | | **Configs get** `doppler_configs_get` | Retrieve a specific Doppler config by project and config name | | **Configs list** `doppler_configs_list` | List configurations from a Doppler project | | **Environments get** `doppler_environments_get` | Retrieves detailed metadata for a specific Doppler environment within a project | | **Environments list** `doppler_environments_list` | List all environments in a Doppler project | | **Get webhook** `doppler_get_webhook` | Retrieve an existing webhook by its slug | | **Get workplace user** `doppler_get_workplace_user` | Retrieve a specific workplace user by their workplace_user id | | **Integrations list** `doppler_integrations_list` | Retrieve all existing integrations in Doppler | | **Invites list** `doppler_invites_list` | List open workplace invites | | **List change requests** `doppler_list_change_requests` | List existing change requests in the Doppler workplace | | **List project members** `doppler_list_project_members` | List all members of a Doppler project including users, groups, service accounts, and invites | | **List service tokens** `doppler_list_service_tokens` | List all service tokens for a specific Doppler config | | **List users** `doppler_list_users` | List all users in the Doppler workplace | | **List webhooks** `doppler_list_webhooks` | List all webhooks configured for a Doppler project | | **Project members get** `doppler_project_members_get` | Retrieve a specific project member's details including their role and environment access | | **Project permissions list** `doppler_project_permissions_list` | List all available project-level permissions in Doppler | | **Project roles get** `doppler_project_roles_get` | Retrieve detailed information about a specific project role in Doppler, including its | | **Project roles list** `doppler_project_roles_list` | List all available project roles in Doppler | | **Projects get** `doppler_projects_get` | Retrieve details of a specific Doppler project by its identifier | | **Projects list** `doppler_projects_list` | List all Doppler projects in your workspace | | **Secrets download** `doppler_secrets_download` | Download secrets from a Doppler config in various formats | | **Secrets get** `doppler_secrets_get` | Retrieve a specific secret from a Doppler project config | | **Secrets list** `doppler_secrets_list` | List all secrets for a specific Doppler config within a project | | **Secrets names** `doppler_secrets_names` | Retrieve the list of secret names from a specific Doppler config | | **Workplace get** `doppler_workplace_get` | Retrieve workplace information from Doppler | | **Workplace roles get** `doppler_workplace_roles_get` | Retrieve workplace role information from Doppler | ## Example prompts **Activity Logs List** > Use Doppler to activity logs list and walk me through the result in plain English. **Activity Logs Retrieve** > Use Doppler to activity logs retrieve and walk me through the result in plain English. **Auth Me** > Use Doppler to auth me and walk me through the result in plain English. **Config Logs Get** > Use Doppler to config logs get and walk me through the result in plain English. ## 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 Doppler working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Doppler API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Doppler 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 Doppler. | 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 Doppler actions to the runtime in a format your agent can reliably use. | 62 tools for Doppler are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Doppler 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 Doppler in the browser, and the 62 tools above work from chat. There is no SDK and no config file, and the Doppler 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 Doppler 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 Doppler 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 Doppler tools Doppler 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 Doppler 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. ### Doppler 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 Doppler 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 Doppler integration? Yes. ClawLink is the fastest way to connect Hermes to Doppler: link your Doppler account once in the browser and Hermes Agent can call the Doppler API through 62 ready-made tools — no custom code or token handling. ### How do I connect Doppler 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 Doppler in the dashboard and Hermes can use it from the next message — no config files, and the Doppler key you paste is stored server-side instead of in your environment. ### How long does it take to connect Doppler to Hermes Agent? About two minutes. Sign in, click Connect next to Doppler in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Doppler 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 Doppler working from chat. ### Hermes paired but still can't use Doppler 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 tools](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.