How to integrate Strava MCP with Mastra AI

This guide walks you through connecting Strava to Mastra AI using the Composio tool router. By the end, you'll have a working Strava agent that can get your latest cycling activity stats, list all runs i logged this week, show your longest ride from last month through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Strava account through Composio's Strava MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Strava

Oauth2

Strava is a social fitness network and app for cyclists and runners. It's perfect for tracking workouts, sharing progress, and joining active communities.

33 Tools

Managed auth

Connect Strava without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your Mastra AI agent real control over a Strava account through Composio's Strava MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Strava with

ChatGPT OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Strava tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Strava tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Strava agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Strava MCP server, and what's possible with it?

The Strava MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Strava account. It provides structured and secure access to your fitness data, so your agent can perform actions like fetching activities, analyzing stats, logging workouts, managing routes, and exploring your social fitness feed on your behalf.

Workout tracking and retrieval: Let your agent pull detailed records of your recent runs, rides, and other logged activities, complete with stats, maps, and performance data.
Fitness analytics and progress insights: Have your agent analyze your weekly or monthly trends, highlight PRs, and summarize progress toward your training goals.
Route exploration and management: Ask your agent to list, suggest, or organize your favorite routes and segments for upcoming workouts or challenges.
Social engagement automation: Enable your agent to fetch kudos, summarize comments, or surface activity highlights from friends and clubs in your Strava network.
Activity creation and editing: Allow your agent to log new activities, edit workout details, or update activity metadata for accurate record keeping.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Strava through MCP.

Install dependencies

bash

npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Strava

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["strava"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Strava MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "strava" for Strava access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Strava toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "strava-mastra-agent",
    instructions: "You are an AI agent with Strava tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        strava: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Strava toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Strava and Mastra AI:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["strava"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      strava: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "strava-mastra-agent",
    instructions: "You are an AI agent with Strava tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { strava: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Strava through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

TOOLS

Supported Tools

Every Strava action and event your agent gets out of the box.

Create an Activity

Creates a manual activity for an athlete.

Explore segments

Explore segments within a geographic bounding box.

Export Route as GPX

Exports a Strava route as a GPX (GPS Exchange Format) file.

Export Route as TCX

Exports a Strava route as a TCX (Training Center XML) file.

Get Activity

Retrieves detailed information about a specific activity by its ID.

Get activity streams

Retrieves time-series stream data for a specific activity.

Get Activity Zones

Returns the heart rate and power zones of a given activity.

Get athlete stats

Returns the activity stats of an athlete, including ride, run, and swim totals for recent (last 4 weeks), year-to-date, and all-time periods.

Get authenticated athlete

Retrieves the profile of the currently authenticated Strava athlete.

Get Club

Retrieves detailed information about a specific Strava club by its ID.

Get equipment

Retrieves detailed information about a specific piece of gear/equipment.

Get route

Retrieve detailed information about a specific Strava route.

Get route streams

Get detailed stream data for a route.

Get segment

Retrieve detailed information about a specific Strava segment.

Get segment effort

Retrieves detailed information about a specific segment effort by its unique ID.

Get segment effort streams

Returns stream data for a segment effort completed by the authenticated athlete.

Get segment streams

Get detailed stream data for a segment.

Get Upload Status

Retrieves the status of an upload by its ID.

Get zones

Retrieves the authenticated athlete's heart rate and power zones.

List activity comments

Retrieves comments on a specific Strava activity, sorted oldest first.

List activity kudoers

Returns the athletes who kudoed an activity identified by an identifier.

List activity laps

Retrieves lap data for a specific Strava activity.

List athlete activities

Retrieves a paginated list of activities for the authenticated athlete.

List athlete clubs

Retrieves a paginated list of Strava clubs the authenticated athlete is a member of.

List athlete routes

Lists routes created by a specific athlete.

List club activities

Retrieve recent activities from members of a specific club.

List club administrators

Returns a list of the administrators of a given Strava club.

List club members

Returns a list of the athletes who are members of a given club.

List segment efforts

List the authenticated athlete's efforts on a given segment.

List starred segments

Returns a list of the authenticated athlete's starred segments with summary details including segment name, distance, elevation, grade, and location.

Star segment

Stars/Unstars the given segment for the authenticated athlete.

Update Athlete

Update the currently authenticated athlete's profile.

Upload Activity

Uploads a new activity file (FIT, TCX, or GPX) to create an activity on Strava.

FRAMEWORKS

How to build Strava MCP Agent with another framework

ChatGPT

Use Strava MCP with ChatGPT

OpenAI Agents SDK

Use Strava MCP with OpenAI Agents SDK

Claude Agent SDK

Use Strava MCP with Claude Agent SDK

Claude Code

Use Strava MCP with Claude Code

Claude Cowork

Use Strava MCP with Claude Cowork

Codex

Use Strava MCP with Codex

Cursor

Use Strava MCP with Cursor

OpenClaw

Use Strava MCP with OpenClaw

Hermes

Use Strava MCP with Hermes

CLI

Use Strava MCP with CLI

Google ADK

Use Strava MCP with Google ADK

LangChain

Use Strava MCP with LangChain

Vercel AI SDK

Use Strava MCP with Vercel AI SDK

LlamaIndex

Use Strava MCP with LlamaIndex

CrewAI

Use Strava MCP with CrewAI

OpenCode

Use Strava MCP with OpenCode

VS Code

Use Strava MCP with VS Code

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Twitter

Oauth2

Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide.

Instagram

Oauth2

Instagram is a social platform for sharing photos, videos, and stories with your audience. It helps brands and creators engage, grow, and analyze their online presence.

Ayrshare

Api Key

Ayrshare is a Social Media API for managing, automating, and analyzing posts across multiple platforms. It helps you streamline social media workflows and centralize analytics.

Dotsimple

Api Key

Dotsimple is a social media management platform for planning, creating, and publishing content. It helps teams boost their reach with AI-powered content generation and actionable analytics.

FAQ

Frequently asked questions

With a standalone Strava MCP server, the agents and LLMs can only access a fixed set of Strava tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Strava and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Strava tools.

Yes, absolutely. You can configure which Strava scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Strava data and credentials are handled as safely as possible.

Start with Strava.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Strava tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Strava MCP with Mastra AI

Connect Strava without auth hassles

Introduction

Also integrate Strava with

TL;DR

What is Mastra AI?

What is the Strava MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Strava

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Strava MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

OpenCode

VS Code

Explore Other Toolkits

Twitter

Instagram

Ayrshare

Dotsimple

Frequently asked questions

What are the differences in Tool Router MCP and Strava MCP?+

Can I use Tool Router MCP with Mastra AI?+

Can I manage the permissions and scopes for Strava while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Strava.It takes 30 seconds.

Teams ship real agents on Composio