How to integrate Strava MCP with LangChain

This guide walks you through connecting Strava to LangChain 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 LangChain 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 LangChain 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 Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Connect your Strava project to Composio
Create a Tool Router MCP session for Strava
Initialize an MCP client and retrieve Strava tools
Build a LangChain agent that can interact with Strava
Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

Agent Framework: Build agents that can use tools and make decisions
MCP Integration: Connect to external services through Model Context Protocol adapters
Memory Management: Maintain conversation history across interactions
Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 step10 STEPS

Prerequisites

Before starting this tutorial, make sure you have:

Python 3.10 or higher installed on your system
A Composio account with an API key
An OpenAI API key
Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

@composio/langchain provides Composio integration for LangChain
@langchain/mcp-adapters enables MCP client connections
@langchain/core is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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's API
COMPOSIO_USER_ID identifies the user for session management
OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();

What's happening:

We're importing LangChain's MCP adapter and Composio SDK
The dotenv/config import loads environment variables from your .env file
This setup prepares the foundation for connecting LangChain with Strava functionality through MCP

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

What's happening:

We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
Creating a Composio instance that will manage our connection to Strava tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['strava']
    }
);

const url = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Strava tools
The create method takes the user ID and specifies which toolkits should be available
The returned session.mcp.url is the MCP server URL that your agent will use
This approach allows the agent to dynamically load and use Strava tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "strava-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });

What's happening:

We're creating a MultiServerMCPClient that connects to our Strava MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Strava tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Strava related question or task to the agent.\n");

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

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;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });

What's happening:

We initialize an empty conversationHistory list to maintain context across interactions
A readline interface is used to continuously accept user input from the command line
When a user types a message, it's added to the conversation history and sent to the agent
The agent processes the request using the invoke() method with the full conversation history
Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

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

What's happening:

We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['strava']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "strava-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Strava related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

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

Conclusion

You've successfully built a LangChain agent that can interact with Strava through Composio's Tool Router.

Key features of this implementation:

Dynamic tool loading through Composio's Tool Router
Conversation history maintenance for context-aware responses
Async Python provides clean, efficient execution of agent workflows

You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-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

Vercel AI SDK

Use Strava MCP with Vercel AI SDK

Mastra AI

Use Strava MCP with Mastra AI

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. LangChain 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 LangChain

Connect Strava without auth hassles

Introduction

Also integrate Strava with

TL;DR

What is LangChain?

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 dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

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

Vercel AI SDK

Mastra AI

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 LangChain?+

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