Paceva MCP Server
Your swim, bike and run training: readiness, HRV, sleep, workouts and race predictions. Read-only.
Paceva scores 52 (Fair), with no SPDX license recorded. It can be reached as a remote MCP endpoint. It does not declare tools yet. Filed under Knowledge. Install configs are generated for 10 clients. Being listed in the registry is not the same as being vendor-official.
Fair trust
52 of 100 from six public signals. Nobody can buy a point.
- Listed in the official MCP registry.
- No license recorded.
License, quality and maintenance
Quality: Grade C
55/100 for listing completeness. Lost points: short README, no listed tools, short summary.
How quality is graded
Where the 52 comes from
22 + 20 + 0 + 0 + 7 + 3 = 52. Each factor is capped, so no single signal can carry a listing.
Active in the official MCP registry, plus a known vendor namespace.
Registry: 22 of 30 points.How recently the repository saw a commit or release.
Maintenance: 20 of 20 points.GitHub stars and weekly downloads, on a log scale.
Popularity: 0 of 20 points.A clear, OSI-style open-source license.
License: 0 of 10 points.Not archived, a secure install path, a pinned version.
Security: 7 of 10 points.A real summary, a README with depth, listed tools.
Docs: 3 of 10 points.Install
Pick your client, copy the config, paste it in.
Needs Cursor or VS Code installed on this device. The button opens the app and asks you to confirm before it adds the server.
{ "mcpServers": { "owenscheuer-paceva-mcp": { "url": "https://paceva.app/api/mcp" } }}
Environment variables
This server does not declare environment variables.
Tools
All capabilitiesTools show up when the registry metadata or the repository README lists them. Public READMEs are read directly. A GitHub token is used only when one is already configured.
About
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.
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.
devicevalues are your watch's own (e.g. Garmin's HRV);pacevavalues 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.
Frequently asked questions
What is Paceva MCP Server?
Your swim, bike and run training: readiness, HRV, sleep, workouts and race predictions. Read-only.
How do I install Paceva MCP Server in Claude Desktop, Cursor, or VS Code?
Pick your client in the Install section on this page and copy the generated config into the client's config file. Step-by-step guides: Claude Desktop, Cursor, and VS Code. Paceva MCP Server connects to the remote endpoint https://paceva.app/api/mcp, so there is nothing to install locally.
Does Paceva MCP Server support remote (HTTP) connections?
Yes. Paceva MCP Server offers a hosted endpoint over Streamable HTTP, so HTTP-capable clients can connect to it without running anything locally.
How is Paceva MCP Server's trust score calculated?
Paceva MCP Server scores 52 out of 100 (Fair). The score adds six capped public signals: registry status, maintenance, popularity, license, documentation, and security. Nobody can pay for points. Read the methodology for the full formula.
Reviews
No reviews yet—Be the first to review
No published reviews yet. Used it? Tell the next person how it went.
Sign inA verified email is required to review this server.
Add badge to your README
Paste either snippet into the repository README. The image links to this listing.
