Fix, merge, split and join FIT, TCX and GPX activity files: heart-rate repair, multisport.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use when a recording opens fine but has wrong data in it ("fix my run", an odd heart-rate spike, the watch kept running at the start or end). It cleans up what is wrong inside a readable file; it does not fix a file that fails to open or is corrupt. Finds heart-rate spikes (one repair_hr step each; a low-confidence spike is proposed unticked) and an idle stretch at the start or end (one crop step), and reports heart-rate dropouts, which cannot be filled. If the user points at a time ("around minute 20"), pass suspectRanges in elapsed seconds from the start. One activity. Nothing is changed by this call, and nothing that alters heart rate or any other data is applied without the user's confirmation. Show the user every step whose needsUserConfirmation is true, with its title, reason and changes, and get an explicit yes; then call apply_plan with exactly the confirmed step ids. Relay findings and notes in plain words. If refusal is set, tell the user why and do not offer a workaround the answer does not give.
The activity to check, from upload_activity / POST /activities.
Spike detector sensitivity, 1 (only obvious spikes) to 5 (anything suspicious). Default 3.
Up to 10 stretches the user thinks are wrong, in elapsed seconds from the activity's first record ("around minute 20" is fromSec 1140, toSec 1260). Each must be 1 to 3600 s long (toSec - fromSec).
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http mcp https://thesplit.fit/mcp
Use when a recording opens fine but has wrong data in it ("fix my run", an odd heart-rate spike, the watch kept running at the start or end). It cleans up what is wrong inside a readable file; it does not fix a file that fails to open or is corrupt. Finds heart-rate spikes (one repair_hr step each; a low-confidence spike is proposed unticked) and an idle stretch at the start or end (one crop step), and reports heart-rate dropouts, which cannot be filled. If the user points at a time ("around minute 20"), pass suspectRanges in elapsed seconds from the start. One activity. Nothing is changed by this call, and nothing that alters heart rate or any other data is applied without the user's confirmation. Show the user every step whose needsUserConfirmation is true, with its title, reason and changes, and get an explicit yes; then call apply_plan with exactly the confirmed step ids. Relay findings and notes in plain words. If refusal is set, tell the user why and do not offer a workaround the answer does not give.
| Argument | Type | Description |
|---|---|---|
| activityId* | string | The activity to check, from upload_activity / POST /activities. |
| sensitivity | integer | Spike detector sensitivity, 1 (only obvious spikes) to 5 (anything suspicious). Default 3. |
| suspectRanges | array | Up to 10 stretches the user thinks are wrong, in elapsed seconds from the activity's first record ("around minute 20" is fromSec 1140, toSec 1260). Each must be 1 to 3600 s long (toSec - fromSec). |
{
"type": "object",
"required": [
"activityId"
],
"properties": {
"activityId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1,
"description": "The activity to check, from upload_activity / POST /activities."
},
"sensitivity": {
"type": "integer",
"default": 3,
"maximum": 5,
"minimum": 1,
"description": "Spike detector sensitivity, 1 (only obvious spikes) to 5 (anything suspicious). Default 3."
},
"suspectRanges": {
"type": "array",
"items": {
"type": "object",
"required": [
"fromSec",
"toSec"
],
"properties": {
"toSec": {
"type": "number"
},
"fromSec": {
"type": "number",
"minimum": 0
}
},
"additionalProperties": false
},
"maxItems": 10,
"description": "Up to 10 stretches the user thinks are wrong, in elapsed seconds from the activity's first record (\"around minute 20\" is fromSec 1140, toSec 1260). Each must be 1 to 3600 s long (toSec - fromSec)."
}
},
"additionalProperties": false
}Use to combine two recordings of one workout: a watch or bike computer plus a heart-rate-only recording that overlaps it, or a device plus a virtual-platform recording of one indoor ride. Works out which file is the base and the clock offset (pass offsetSec only if the user knows it) and previews what the single merge step will change, including the heart rate it would take from the other file. If the other file does not cover the start or end of the base, it also offers one optional crop step (never ticked) that cuts the result to the time both recorded. Merges have been checked on a limited set of device combinations; other combinations have not been tested, so tell the user to look at the result. Two activities, in any order. If they do not overlap but follow each other, use analyze_interrupted_workout. Nothing is changed by this call, and nothing that alters heart rate or any other data is applied without the user's confirmation. Show the user every step whose needsUserConfirmation is true, with its title, reason and changes, and get an explicit yes; then call apply_plan with exactly the confirmed step ids. Relay findings and notes in plain words. If refusal is set, tell the user why and do not offer a workaround the answer does not give.
| Argument | Type | Description |
|---|---|---|
| offsetSec | number | Seconds to add to the clock of activityIds[1]. Omit to let the server estimate it. |
| activityIds* | array | The two recordings of one workout (for example a watch file and a heart-rate strap file), in any order. |
{
"type": "object",
"required": [
"activityIds"
],
"properties": {
"offsetSec": {
"type": "number",
"maximum": 3600,
"minimum": -3600,
"description": "Seconds to add to the clock of activityIds[1]. Omit to let the server estimate it."
},
"activityIds": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
},
"maxItems": 2,
"minItems": 2,
"description": "The two recordings of one workout (for example a watch file and a heart-rate strap file), in any order.",
"uniqueItems": true
}
},
"additionalProperties": false
}Use when the watch stopped and restarted and one workout is in 2 to 5 files. Orders the pieces by time, checks they follow each other, proposes trimming a piece that overlaps the one before (the join depends on it), and proposes one join; one recording lying inside another is refused (try analyze_dual_recording). Pieces of different sports export as one multisport file. Nothing is changed by this call, and nothing that alters heart rate or any other data is applied without the user's confirmation. Show the user every step whose needsUserConfirmation is true, with its title, reason and changes, and get an explicit yes; then call apply_plan with exactly the confirmed step ids. Relay findings and notes in plain words. If refusal is set, tell the user why and do not offer a workaround the answer does not give.
| Argument | Type | Description |
|---|---|---|
| activityIds* | array | The 2 to 5 pieces of one workout, in any order. |
{
"type": "object",
"required": [
"activityIds"
],
"properties": {
"activityIds": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
},
"maxItems": 5,
"minItems": 2,
"description": "The 2 to 5 pieces of one workout, in any order.",
"uniqueItems": true
}
},
"additionalProperties": false
}Use for a triathlon or other multisport recording. Lists the legs, checks whether a separate recording (for example a bike computer file, legActivityIds) matches a leg and proposes splicing it in, and proposes moving transitions to official split times the user gives (officialBoundaries, elapsed seconds from the start) or to a matched leg's own start or end (never ticked: a late start press is as likely as a late lap press). The engine cannot split one session into several. Nothing is changed by this call, and nothing that alters heart rate or any other data is applied without the user's confirmation. Show the user every step whose needsUserConfirmation is true, with its title, reason and changes, and get an explicit yes; then call apply_plan with exactly the confirmed step ids. Relay findings and notes in plain words. If refusal is set, tell the user why and do not offer a workaround the answer does not give.
| Argument | Type | Description |
|---|---|---|
| activityId* | string | The multisport (triathlon) recording. |
| legActivityIds | array | Up to 3 separate recordings of single legs (for example a bike computer file). Must not include activityId. |
| officialBoundaries | array | Up to 8 official transition times: each moves the boundary between session sessionIndex and the next to atSec, elapsed seconds from the file's first record. At most one per sessionIndex. |
{
"type": "object",
"required": [
"activityId"
],
"properties": {
"activityId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1,
"description": "The multisport (triathlon) recording."
},
"legActivityIds": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
},
"maxItems": 3,
"description": "Up to 3 separate recordings of single legs (for example a bike computer file). Must not include activityId.",
"uniqueItems": true
},
"officialBoundaries": {
"type": "array",
"items": {
"type": "object",
"required": [
"sessionIndex",
"atSec"
],
"properties": {
"atSec": {
"type": "number",
"exclusiveMinimum": 0
},
"sessionIndex": {
"type": "integer",
"minimum": 0
}
},
"additionalProperties": false
},
"maxItems": 8,
"description": "Up to 8 official transition times: each moves the boundary between session sessionIndex and the next to atSec, elapsed seconds from the file's first record. At most one per sessionIndex."
}
},
"additionalProperties": false
}Run exactly the steps of an analyze_* plan that the user confirmed (every step with needsUserConfirmation true must have been shown and agreed). The inputs are never changed: the result is a new activity with download urls and a before/after validation to relay. If the answer is an error with retryAfterSec (rate_limited, plan_incomplete, capacity_exceeded, server_busy), wait that long and call again with the same confirmedStepIds to continue; calling a completed plan again returns the same result. The answer carries supportUrl and supportNote: you may mention the support link once, after delivering the file. Call delete_activity for the inputs and the result when the user is done.
| Argument | Type | Description |
|---|---|---|
| planId* | string | The planId an analyze_* call returned. |
| confirmedStepIds* | array | Exactly the step ids the user confirmed. Only these run; a step's dependsOn must be confirmed too. |
{
"type": "object",
"required": [
"planId",
"confirmedStepIds"
],
"properties": {
"planId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1,
"description": "The planId an analyze_* call returned."
},
"confirmedStepIds": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
},
"maxItems": 120,
"minItems": 1,
"description": "Exactly the step ids the user confirmed. Only these run; a step's dependsOn must be confirmed too.",
"uniqueItems": true
}
},
"additionalProperties": false
}Discard an activity from the server's memory now instead of waiting for it to expire. Do this for every activity you are done with, results included.
| Argument | Type | Description |
|---|---|---|
| activityId* | string |
{
"type": "object",
"required": [
"activityId"
],
"properties": {
"activityId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
}
},
"additionalProperties": false
}Get the download url of an activity as fit, tcx or gpx (the file itself is not returned; gpx needs GPS positions). Give the user the url; it works until expiresAt. The answer carries supportUrl and supportNote: you may mention the support link once, after delivering the file. Call delete_activity when the user has the file.
| Argument | Type | Description |
|---|---|---|
| format* | string | |
| activityId* | string |
{
"type": "object",
"required": [
"activityId",
"format"
],
"properties": {
"format": {
"enum": [
"fit",
"tcx",
"gpx"
],
"type": "string"
},
"activityId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
}
},
"additionalProperties": false
}What an uploaded or produced activity is: format, sport, start, duration, sessions, data streams, warnings, expiresAt, and figures (elapsed and moving time, distance, max and average heart rate, calories, per-session figures). Read-only.
| Argument | Type | Description |
|---|---|---|
| activityId* | string |
{
"type": "object",
"required": [
"activityId"
],
"properties": {
"activityId": {
"type": "string",
"pattern": "^[A-Za-z0-9_-]{1,64}$",
"maxLength": 64,
"minLength": 1
}
},
"additionalProperties": false
}Upload a FIT, TCX or GPX file (base64, at most 15 MB decoded) and get its activityId and expiresAt. Files are held in memory only and expire (30 minutes after last use, 2 hours at most); originals are never changed. Base64 costs a lot of context: an agent with a shell should upload with curl to POST https://thesplit.fit/api/v1/activities (multipart field file) and use the returned activityId here. Call delete_activity for every activity you are done with.
| Argument | Type | Description |
|---|---|---|
| filename* | string | The file's name, ending .fit, .tcx or .gpx (it selects the parser). |
| contentBase64* | string | The whole file, standard base64 with padding (length a multiple of 4). At most 15 MB decoded. |
{
"type": "object",
"required": [
"filename",
"contentBase64"
],
"properties": {
"filename": {
"type": "string",
"pattern": "\\.(?:[fF][iI][tT]|[tT][cC][xX]|[gG][pP][xX])$",
"maxLength": 255,
"minLength": 1,
"description": "The file's name, ending .fit, .tcx or .gpx (it selects the parser)."
},
"contentBase64": {
"type": "string",
"pattern": "^[A-Za-z0-9+/]*={0,2}$",
"minLength": 4,
"description": "The whole file, standard base64 with padding (length a multiple of 4). At most 15 MB decoded."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 17, 2026.