Nike Run Club MCP Server

A local Model Context Protocol (MCP) server that gives MCP clients read-only access to your Nike Run Club running history.

The server can list running activities and retrieve detailed metrics such as distance, pace, heart rate, and GPS samples. It was inspired by niw's research into the NikePlus API.

Requirements

• Node.js 20 or later

• A Nike API bearer token for your own Nike account

• An MCP client such as Codex

Related MCP server: Strava Training MCP

Installation

git clone https://github.com/tsutsutaku/nike-runclub-mcp.git
cd nike-runclub-mcp
npm install
npm run build

Set the bearer token in the environment that launches your MCP client:

export NIKE_BEARER_TOKEN="YOUR_BEARER_TOKEN"

You can obtain your own token by inspecting requests made by the Nike Run Club app to api.nike.com and locating the Authorization: Bearer ... request header. The exact process depends on the device and app version, so this project does not automate login or token extraction.

Codex setup

This repository includes a project-scoped .codex/config.toml. After exporting the token, launch Codex from the repository:

export NIKE_BEARER_TOKEN="YOUR_BEARER_TOKEN"
codex

Trust the project when prompted. Codex only loads project-scoped configuration for trusted projects. Use /mcp to confirm that nike-runclub is connected.

The configuration forwards NIKE_BEARER_TOKEN from Codex's parent environment. Merely placing the token in a .env file does not load it automatically; export it in your shell or provide it through a secure environment/secret manager.

Other MCP clients

Use the following as a starting point, replacing the path with the absolute path to your clone:

{
  "mcpServers": {
    "nike-runclub": {
      "command": "node",
      "args": ["/absolute/path/to/nike-runclub-mcp/dist/index.js"],
      "env": {
        "NIKE_BEARER_TOKEN": "YOUR_BEARER_TOKEN"
      }
    }
  }
}

Prefer your client's secret-management or environment-forwarding feature over storing the token directly in configuration.

Tools

list_runs

Lists running activities in reverse chronological order.

get_run

Retrieves one activity by the ID returned from list_runs.

Example prompts:

• "List my 10 most recent runs."

• "Analyze the pace and heart-rate data for this activity."

• "Summarize my running distance since the beginning of this month."

Environment variables

Development

npm run check

This command compiles the TypeScript project and runs the test suite. Tests use mocked HTTP responses and do not contact Nike or require a real bearer token.

The activity list currently uses /plus/v3/activities/before_id/v3/, while activity details use /sport/v3/me/activity/. Both are undocumented Nike endpoints and may change without notice.

Privacy and security

• The server communicates directly with api.nike.com; it does not send your activity data to a separate service.

• The MCP server is read-only and exposes no activity mutation or deletion tools.

• .env, build output, and dependencies are excluded from Git.

• Revoke or replace the bearer token if you accidentally expose it.

Disclaimer

This project is independent and is not affiliated with, endorsed by, or sponsored by Nike. Nike and Nike Run Club are trademarks of Nike, Inc.