Strava MCP

Created By
JonoCXa year ago
A Strava MCP
Overview

What is Strava MCP?

Strava MCP is a tool that integrates with the Claude Desktop client, allowing users to query their Strava activities directly through the app.

How to use Strava MCP?

To use Strava MCP, you need to set up a Strava developer app, clone the repository, and configure your environment variables. After installation, you can interact with your Strava data using Claude.

Key features of Strava MCP?

  • Integration with Claude Desktop for easy access to Strava activities.
  • Ability to query recent activities and get detailed information.
  • Simple setup process with clear instructions.

Use cases of Strava MCP?

  1. Asking Claude about your latest Strava activity.
  2. Getting insights into your workout history.
  3. Managing your Strava data through a conversational interface.

FAQ from Strava MCP?

  • What do I need to use Strava MCP?

You need a Strava account, Claude Desktop, and the necessary dependencies installed.

  • How do I install Strava MCP?

Follow the setup instructions in the repository, including creating an .env file with your Strava app credentials.

  • Can I modify the server?

Yes, you can make changes to the server, but you will need to restart the Claude client to apply them.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JonoCX
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago