# How to connect Strava to OpenClaw (no API keys) > Connect Strava to OpenClaw with ClawLink in one click — 33 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/strava The usual route to Strava 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 Strava setup: install one ClawHub skill, connect Strava in the browser, and OpenClaw can call real Strava actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/strava ## Setup It takes three steps to connect OpenClaw to Strava. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Strava** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw 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 strava # connect Strava (browser OAuth) npx -y @useclawlink/cli actions strava # list available actions npx -y @useclawlink/cli run strava --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Strava in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Create it in Strava for me, then confirm the important fields before you finish. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Strava is connected in the dashboard, that agent calls the same 33 Strava 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). ## Strava MCP for OpenClaw Looking for a Strava MCP server for OpenClaw? ClawLink connects Strava to OpenClaw and exposes 33 Strava 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 Hermes instead? The [Hermes Strava integration](https://claw-link.dev/hermes/strava) works the same way. ## What the OpenClaw Strava integration can do 33 Strava 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 33. ### 30 of 33 Strava tools for OpenClaw | Tool | What it does | |---|---| | **Create an activity** `strava_create_an_activity` | Create a manual activity | | **Explore segments** `strava_explore_segments` | Explore segments in an area | | **Get activity** `strava_get_activity` | Get activity details by ID | | **Get activity streams** `strava_get_activity_streams` | Get activity time-series data | | **Get activity zones** `strava_get_activity_zones` | Get heart rate and power zones | | **Get athlete stats** `strava_get_athlete_stats` | Get athlete activity stats | | **Get authenticated athlete** `strava_get_authenticated_athlete` | Get authenticated athlete profile | | **Get club** `strava_get_club` | Get club details | | **Get route** `strava_get_route` | Get route details | | **Get segment** `strava_get_segment` | Get segment details | | **List activity laps** `strava_list_activity_laps` | List activity laps | | **List athlete activities** `strava_list_athlete_activities` | List authenticated athlete's activities | | **List athlete clubs** `strava_list_athlete_clubs` | List athlete's clubs | | **List athlete routes** `strava_list_athlete_routes` | List athlete's routes | | **List club activities** `strava_list_club_activities` | List club activities | | **Upload activity** `strava_upload_activity` | Upload an activity file | | **Export route gpx** `strava_export_route_gpx` | Exports a Strava route as a GPX (GPS Exchange Format) file | | **Export route tcx** `strava_export_route_tcx` | Exports a Strava route as a TCX (Training Center XML) file | | **Get equipment** `strava_get_equipment` | Retrieves detailed information about a specific piece of gear/equipment | | **Get route streams** `strava_get_route_streams` | Get detailed stream data for a route | | **Get segment effort** `strava_get_segment_effort` | Retrieves detailed information about a specific segment effort by its unique ID | | **Get segment effort streams** `strava_get_segment_effort_streams` | Returns stream data for a segment effort completed by the authenticated athlete | | **Get segment streams** `strava_get_segment_streams` | Get detailed stream data for a segment | | **Get upload** `strava_get_upload` | Retrieves the status of an upload by its ID | | **Get zones** `strava_get_zones` | Retrieves the authenticated athlete's heart rate and power zones | | **List activity comments** `strava_list_activity_comments` | Retrieves comments on a specific Strava activity, sorted oldest first | | **List activity kudoers** `strava_list_activity_kudoers` | Returns the athletes who kudoed an activity identified by an identifier | | **List club administrators** `strava_list_club_administrators` | Returns a list of the administrators of a given Strava club | | **List club members** `strava_list_club_members` | Returns a list of the athletes who are members of a given club | | **List segment efforts** `strava_list_segment_efforts` | List the authenticated athlete's efforts on a given segment | ## Example prompts **Create An Activity** > Create it in Strava for me, then confirm the important fields before you finish. **Explore Segments** > Use Strava to explore segments and walk me through the result in plain English. **Get Activity** > Pull the relevant data from Strava, summarize it in plain English, and point out anything that needs attention. **Get Activity Streams** > Pull the relevant data from Strava, summarize it in plain English, and point out anything that needs attention. ## 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 Strava working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Strava app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Strava 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 Strava. | 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 Strava actions to the runtime in a format your agent can reliably use. | 33 tools for Strava are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Strava 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 Strava in the browser, and the 33 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. ### OpenClaw installed the Strava skill but can't call the tools The ClawHub skill teaches OpenClaw about Strava, but the calls run through the ClawLink plugin and your connected account. Make sure Strava 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 Strava 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 Strava tools Strava 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 Strava 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. ### Strava 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 Strava 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 OpenClaw Strava integration? Yes. ClawLink is the fastest way to connect OpenClaw to Strava: link your Strava account once in the browser and OpenClaw can call the Strava API through 33 ready-made tools — no custom code or token handling. ### How do I add Strava to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Strava skill from ClawHub, then you click Connect in the dashboard to authorize Strava. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Strava to OpenClaw? About two minutes. Sign in, click Connect next to Strava in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Strava 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 Strava working from chat. ### OpenClaw installed the Strava skill but can't call the tools The ClawHub skill teaches OpenClaw about Strava, but the calls run through the ClawLink plugin and your connected account. Make sure Strava 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. ## Related - [OpenClaw Exist integration](https://claw-link.dev/openclaw/exist) — Track and analyze personal health, fitness, and lifestyle data