Koskamo

Memory.fit MCP

Memory.fit MCP provides an AI with access to an athlete's training, sleep, recovery, and nutrition data. It allows the AI to read historical data and write personalized training plans, targets, and fuel strategies, which are then sent as structured workouts to compatible wearables like Garmin, COROS, Wahoo, and Suunto.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Memory.fit MCP logo, by Fun-Management-SRLVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Fun-Management-SRL
You need:Sign in with Memory.fit
MCP endpoint (Streamable HTTP)
https://api.memory.fit/mcp
Vendor documentation

What you can do with it

  • Read weekly training, sleep, and fuel data for AI analysis
  • Generate personalized training plans and targets
  • Send structured workouts to compatible wearables
  • Track recovery and nutrition metrics

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: fit.memory/memory-fit@1.0.0Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
722 ms
95th percentile latency
722 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 722 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http memory-fit-mcp https://api.memory.fit/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add memory-fit-mcp --url https://api.memory.fit/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable memory-fit-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "memory-fit-mcp": {
      "url": "https://api.memory.fit/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "memory-fit-mcp": {
      "type": "streamableHttp",
      "url": "https://api.memory.fit/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start memory-fit-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "memory-fit-mcp": {
      "type": "http",
      "url": "https://api.memory.fit/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http memory-fit-mcp https://api.memory.fit/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "memory-fit-mcp": {
      "url": "https://api.memory.fit/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "memory-fit-mcp": {
      "serverUrl": "https://api.memory.fit/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Memory.fit MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 3,921

Do you run Memory.fit MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing