Skip to main content
Glama
OwenScheuer

Paceva MCP Server

by OwenScheuer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Paceva for developers

Paceva turns an endurance athlete's watch data into honest race predictions: ranges, checked against their own history. This repository documents the public surface: the Paceva MCP server, the OAuth 2.1 sign-in in front of it, and how Paceva connects to Intervals.icu.

The Paceva app itself is closed source. This repo is documentation and examples only.

Connect in one minute

Server URL: https://paceva.app/api/mcp

App

How

Claude (claude.ai, desktop, mobile)

Settings → Connectors → Add custom connector, paste the URL, sign in to Paceva, approve.

ChatGPT

Settings → Apps & Connectors → add a custom connector with the URL (some plans need developer mode).

Claude Code

claude mcp add --transport http paceva https://paceva.app/api/mcp, then /mcp to sign in.

Cursor / VS Code

One-click buttons on paceva.app/dashboard/ai, or add it as a Streamable HTTP server.

Anything else

Any MCP client that supports Streamable HTTP and OAuth 2.1 with PKCE.

Then ask things like "Should I go hard today?", "What could I swim a 1500 in right now?" or "How did my last block of riding go?".

Full walkthrough: docs/connect.md.

Related MCP server: intervals.icu MCP Server

What's here

Doc

For

docs/connect.md

Connecting each AI app, and what to expect

docs/tools.md

Every MCP tool, its arguments and what it returns

docs/oauth.md

The OAuth 2.1 server: discovery, PKCE, client registration, tokens

docs/intervals-icu.md

How watch data gets in: the Intervals.icu sign-in, step by step

docs/data-and-privacy.md

What the AI app can and can't see

docs/listing.md

The MCP Registry entry (server.json) and directories to submit to

examples/

curl discovery, a raw JSON-RPC call, client config snippets

Ground rules

  • Read-only. One scope, paceva:read. No tool writes anything.

  • Only your own data. A token is bound to one Paceva account; it can never read anyone else's.

  • Every number is labelled. device values are your watch's own (e.g. Garmin's HRV); paceva values are computed by Paceva.

  • Predictions are ranges. Tools return a low–high range and how often that range holds for you. Quote the range, not a single time.

  • Revocable. Disconnect any app from Paceva → Use with AI; its tokens stop working on the next call.

Status

Piece

Status

MCP server + OAuth

Live

Intervals.icu sync (Garmin, Coros, Wahoo, Polar, Suunto)

Live

Paceva web dashboard

Coming soon, join the waitlist

iPhone app (Apple Health)

Coming soon

Security

Found a problem? Please email privacy@paceva.app rather than opening a public issue. See SECURITY.md.

License

Docs and examples in this repository are MIT licensed. The Paceva name and logo are not.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Resources

Related MCP Connectors

Related MCP Servers

  • intervals.mcp

    ryansheppard
    F
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to access and analyze intervals.icu training data including activities, fitness metrics (CTL/ATL/TSB), wellness stats, and calendar events. Supports natural language querying of athletic performance for training insights and workout planning.
    6
    -

  • intervals-mcp

    VictorForV
    A
    license
    A
    quality
    B
    maintenance
    Provides AI assistants with read-only access to an athlete's Intervals.icu training data, including activities, wellness metrics, zones, and planned events, for use with MCP clients like ChatGPT and Claude.
    15
    MIT