# How to connect Amplitude to Hermes Agent (no API keys) > Connect Amplitude to Hermes with ClawLink in one click — 48 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/amplitude Most guides for giving Hermes Agent Amplitude 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 Amplitude setup: pair once in the browser and your always-on Hermes agent can act on Amplitude 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 Amplitude. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Amplitude** — 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 amplitude # connect Amplitude (browser OAuth) npx -y @useclawlink/cli actions amplitude # list available actions npx -y @useclawlink/cli run amplitude --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 Amplitude in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Amplitude to mcp get agent results 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 Amplitude is connected in the dashboard, that agent calls the same 48 Amplitude 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). ## Amplitude MCP for Hermes Looking for a Amplitude MCP server for Hermes Agent? ClawLink connects Amplitude to Hermes Agent and exposes 48 Amplitude 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 Amplitude integration](https://claw-link.dev/openclaw/amplitude) works the same way. ## What the Hermes Agent Amplitude integration can do 48 Amplitude 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 48. ### 30 of 48 Amplitude tools for Hermes | Tool | What it does | |---|---| | **Mcp get agent results** `amplitude_mcp_get_agent_results` | Retrieve results from AI agents that have analyzed your dashboards or session replays | | **Mcp get amp session replay info** `amplitude_mcp_get_amp_session_replay_info` | Unified entry point for session replay data: find replays and inspect what happened in them | | **Mcp get amp taxonomy** `amplitude_mcp_get_amp_taxonomy` | Read a project's tracking plan: the events it defines, the properties on them, what a branch | | **Mcp get amp user data** `amplitude_mcp_get_amp_user_data` | Look up Amplitude users | | **Mcp get amplitude agent analytics info** `amplitude_mcp_get_amplitude_agent_analytics_info` | Single read entry point for Amplitude Agent Analytics (AI/LLM session investigation) | | **Mcp get amplitude charts** `amplitude_mcp_get_amplitude_charts` | Read saved Amplitude charts by ID, or look up the chart-type schema | | **Mcp get amplitude context** `amplitude_mcp_get_amplitude_context` | Unified entry point for Amplitude context | | **Mcp get data warehouse destinations** `amplitude_mcp_get_data_warehouse_destinations` | List the Data Warehouse export destinations configured for a project | | **Mcp get from URL** `amplitude_mcp_get_from_url` | Retrieve objects from Amplitude URLs WHEN TO USE: - CRITICAL: Only use this tool for full | | **Mcp get group types** `amplitude_mcp_get_group_types` | List available group types for a project | | **Mcp get session replay duration** `amplitude_mcp_get_session_replay_duration` | APP SUPPORT ONLY | | **Mcp get session replay stream** `amplitude_mcp_get_session_replay_stream` | APP SUPPORT ONLY | | **Mcp get session replay timeline** `amplitude_mcp_get_session_replay_timeline` | APP SUPPORT ONLY | | **Mcp get tracking plan sources** `amplitude_mcp_get_tracking_plan_sources` | List the sources configured on a project's tracking plan (e.g | | **Mcp get transformations** `amplitude_mcp_get_transformations` | Retrieve data transformations from a project | | **Mcp query amplitude data** `amplitude_mcp_query_amplitude_data` | Run analytics queries to answer data questions about users, events, funnels, and retention — | | **Mcp render amp session replay** `amplitude_mcp_render_amp_session_replay` | Render an interactive session replay player UI for one or more session replays | | **Mcp render amplitude chart** `amplitude_mcp_render_amplitude_chart` | Render an interactive Amplitude chart UI for a saved chart or a chart edit by ID | | **Mcp search amp data taxonomy** `amplitude_mcp_search_amp_data_taxonomy` | Semantic search over a project's data taxonomy: discover events, properties, and property | | **Mcp search amp entities** `amplitude_mcp_search_amp_entities` | Search for dashboards, charts, notebooks, experiments, docs, and other content in Amplitude | | **Mcp track ui render response** `amplitude_mcp_track_ui_render_response` | Internal telemetry tool used by MCP UI components to report render latency and errors | | **Mcp use amp guides surveys** `amplitude_mcp_use_amp_guides_surveys` | List Guides and Surveys or get one by ID | | **Mcp use amp skill** `amplitude_mcp_use_amp_skill` | Load an Amplitude skill — a workflow playbook describing the optimal sequence of Amplitude | | **Mcp use amplitude AI feedback** `amplitude_mcp_use_amplitude_ai_feedback` | Read Amplitude AI Feedback (customer VoC) for a project — surveys, support tickets, app | | **Mcp use amplitude data connections** `amplitude_mcp_use_amplitude_data_connections` | Unified entry point for everything to do with a project's data connections — ingestion sources | | **Mcp create group types** `amplitude_mcp_create_group_types` | Create one or more group types in a project, OR add already-ingested group types with status | | **Mcp create properties** `amplitude_mcp_create_properties` | Create one or more properties in a project's tracking plan | | **Mcp manage amp entities** `amplitude_mcp_manage_amp_entities` | Create a shared (team) space, rename a space or change its members, or move charts, dashboards | | **Mcp manage amp taxonomy** `amplitude_mcp_manage_amp_taxonomy` | Read Data workspace governance settings and manage tracking-plan branches for a project | | **Mcp share amp entities** `amplitude_mcp_share_amp_entities` | Manage sharing and org invites for Amplitude entities | ## Example prompts **Mcp Get Agent Results** > Use Amplitude to mcp get agent results and walk me through the result in plain English. **Mcp Get Amp Session Replay Info** > Use Amplitude to mcp get amp session replay info and walk me through the result in plain English. **Mcp Get Amp Taxonomy** > Use Amplitude to mcp get amp taxonomy and walk me through the result in plain English. **Mcp Get Amp User Data** > Use Amplitude to mcp get amp user data and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Amplitude working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Amplitude app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Amplitude through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Amplitude. | 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 Amplitude actions to the runtime in a format your agent can reliably use. | 48 tools for Amplitude are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Amplitude 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 Amplitude in the browser, and the 48 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Amplitude 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 Amplitude 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 Amplitude tools Amplitude 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 Amplitude 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. ### Amplitude 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Amplitude and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent Amplitude integration? Yes. ClawLink is the fastest way to connect Hermes to Amplitude: link your Amplitude account once in the browser and Hermes Agent can call the Amplitude API through 48 ready-made tools — no custom code or token handling. ### How do I connect Amplitude 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 Amplitude in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Amplitude to Hermes Agent? About two minutes. Sign in, click Connect next to Amplitude in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Amplitude up myself? The alternative to ClawLink is usually manual OAuth app 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 Amplitude working from chat. ### Hermes paired but still can't use Amplitude 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 - [PostHog tools](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.