Xert MCP

What Milofax/xert-mcp MCP server does

Milofax/xert-mcp MCP server exposes selected XERT account and analysis functions through MCP. It is aimed at cyclists who want Claude or another compatible MCP client to query training data without manually navigating the XERT interface.

The server can return a current fitness signature containing FTP, LTP, HIE, and Peak Power. It also provides training status information, including freshness, training load, recommended XSS, and the Workout of the Day. These outputs give an agent access to both longer-term performance indicators and current training context.

Workout support covers saved-workout discovery, detailed interval inspection, and export in ZWO or ERG format. Activity support includes date-range listing and individual activity details with XSS metrics and MPA data. FIT-file uploads are available for sending ride data to XERT for analysis.

How it works

The project is a Node.js MCP server that communicates with the XERT API. The documented prerequisites are Node.js 18 or later and an XERT account; the account may be free or premium. After authentication, the server can be registered as a local process in Claude Desktop using Node and the built server entry point.

Its MCP tools are organized around training information, workouts, activities, and FIT uploads. For example, a client can request recent activities, retrieve one activity’s metrics, inspect a workout’s intervals, or export a selected workout for use in a compatible training application. The server does not describe a separate hosted endpoint in the supplied material.

Setup and configuration

To run Milofax/xert-mcp MCP server, clone the repository, install its npm dependencies, and run the provided authentication setup script. That script prompts for the XERT email address and password and saves authentication data locally. Build the project before starting the production server.

Claude Desktop configuration points to the generated dist/server.js file and starts it with node. The README provides configuration locations for macOS and Windows. A Docker option is also documented: build the image locally, authenticate first, and pass XERT_ACCESS_TOKEN and XERT_REFRESH_TOKEN into the container.

Authentication data is persisted in xert-tokens.json. Access tokens last seven days and refresh tokens last six months according to the README. The server refreshes access tokens after authorization failures and persists replacement tokens. If authentication cannot be recovered, run the setup-auth script again. When environment variables are used alongside the token file, the stored token file takes precedence.

Tools and capabilities

• xert-get-training-info returns fitness signature values, training status, load, and the Workout of the Day.
• xert-list-workouts lists saved XERT workouts.
• xert-get-workout returns workout interval details.
• xert-download-workout exports a workout as ZWO or ERG.
• xert-list-activities lists activities within a requested time range.
• xert-get-activity returns activity details with XSS metrics.
• xert-upload-fit uploads a FIT file for analysis.

Limitations and notes

Milofax/xert-mcp MCP server requires an XERT account and valid authentication. Tokens are not permanent: access-token expiry may require rerunning authentication and updating Docker configuration when refreshed values are needed. The supplied documentation confirms Claude Desktop setup, but does not provide compatibility details for other MCP clients. The project is released under the MIT license.