How to connect Amplitude to OpenClaw
Connect Amplitude to OpenClaw with ClawLink in one click — 48 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
AmplitudeOAUTH2MCPQuery product analytics, events, and user behavior. Once connected, OpenClaw can read and act on Amplitude from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Amplitude access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Amplitude setup: install one ClawHub skill, connect Amplitude in the browser, and OpenClaw can call real Amplitude actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Amplitude skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Amplitude" (hith3sh/amplitude-analytics) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/amplitude-analytics
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Amplitude.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Amplitude
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Amplitude?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Amplitude in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Amplitude to mcp get agent results and walk me through the result in plain English.
Using a different agent?
The OpenClaw 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 loginlogin 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.
Amplitude MCP for OpenClaw
Looking for a Amplitude MCP server for OpenClaw? ClawLink connects Amplitude to OpenClaw and exposes 48 Amplitude tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Amplitude integration works the same way.
What the OpenClaw Amplitude integration can do
48 Amplitude tools are ready for OpenClaw 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 OpenClaw
| 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 |
Try it: find the Amplitude tool you need
Browse the 30 Amplitude tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Amplitude to mcp get agent results and walk me through the result in plain English.
Use Amplitude to mcp get amp session replay info and walk me through the result in plain English.
Use Amplitude to mcp get amp taxonomy and walk me through the result in plain English.
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 OpenClaw. 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 OpenClaw 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 comparison.
Troubleshooting
OpenClaw installed the Amplitude skill but can't call the tools
The ClawHub skill teaches OpenClaw about Amplitude, but the calls run through the ClawLink plugin and your connected account. Make sure Amplitude is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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.
FAQ
Is there a OpenClaw Amplitude integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Amplitude: link your Amplitude account once in the browser and OpenClaw can call the Amplitude API through 48 ready-made tools — no custom code or token handling.
How do I add Amplitude to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Amplitude skill from ClawHub, then you click Connect in the dashboard to authorize Amplitude. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Amplitude to OpenClaw?
About two minutes. Sign in, click Connect next to Amplitude in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Amplitude working from chat.
OpenClaw installed the Amplitude skill but can't call the tools
The ClawHub skill teaches OpenClaw about Amplitude, but the calls run through the ClawLink plugin and your connected account. Make sure Amplitude is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
