Memory.fit
fit.memoryPublished by memory.fitOfficial publisherv1.0.0Updated Oct 29, 2026
Your training, sleep, recovery and fuel for the AI you use: it reads your week and plans the next.
Overview
Hosted Memory.fit server that lets an AI read your training, sleep, recovery and nutrition data and write back weekly plans, targets and meal plans.
- What you can do
- Read workouts from watches and apps, sleep, HRV, resting heart rate, body composition, food and drink logs, races and goals
- Write training sessions sent to your watch, daily targets, meal plans, logged meals and notes for other AIs, with your permission
- Check in for only the data that arrived since the last look
- When to use it
- Useful if you already track training, sleep and nutrition in Memory.fit and want the AI you use to plan your week from that data and push sessions and targets back into the app.
- Requirements
- A remote Streamable HTTP endpoint; nothing to install or build. Needs a Memory.fit account set up in the app first. Sign-in is OAuth 2.1 with dynamic client registration; clients without OAuth can use a personal key from the app sent as an Authorization Bearer header.
Installation
In SourceWeft
- Open Memory.fit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/fit.memory%2Fmemory-fit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"memory-fit": {
"type": "http",
"url": "https://api.memory.fit/mcp"
}
}
}README
Memory.fit MCP
[Memory.fit]Memory.fit keeps your training, sleep, recovery and fuel in one place for the AI you already use. Your AI reads workouts from your watch and apps, sleep and HRV, and what you ate, then writes your week back: sessions, daily targets and meal plans, which show in the Memory.fit app on iPhone and Android.
This repository holds only the connection settings for Memory.fit MCP, a hosted server. There is nothing to run or build.
- Address:
https://api.memory.fit/mcp(Streamable HTTP) - Sign-in: OAuth 2.1 with dynamic client registration. Your AI opens the Memory.fit sign-in page; you choose what it may do. No key needed. AIs without sign-in can use a personal key from the app (Settings › AI agents › Use a key instead), sent as
Authorization: Bearer mem_pat_…. - Needs: a Memory.fit account, set up in the app first.
Connect
Step-by-step pages for each AI: memory.fit/ai-coaches.
Cline, or any client with a JSON settings file
The first call opens the Memory.fit sign-in (OAuth 2.1). A client without OAuth can use a personal key from the app (Settings › AI agents › Use a key instead) as a header:
What your AI can do
- Read: workouts (Garmin, Wahoo, COROS, Polar, Suunto, Apple Health, Health Connect and more), sleep, HRV and resting heart rate, body composition, what you ate and drank, your races and goals.
- Write, with your permission: training sessions (sent to your watch), daily targets, meal plans, logged meals, notes for your other AIs.
- Check in:
get_updatesreturns only what arrived since it last looked.
Memory.fit recommends nothing itself: the plans are your AI's, the data is yours. It is not medical advice.
Links
- Website: https://memory.fit
- Privacy: https://memory.fit/privacy
- Terms: https://memory.fit/terms
- Support: [email protected]
The connection settings in this repository are MIT licensed. Memory.fit, the server and the app are not.
Source: README.md at commit e75f2ac
Tools
0Version history
1- v1.0.0LatestOct 29, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Memory integrations
pg.ddx.io: the PostgreSQL community's memory
io.ddx.pgOfficial publisher
pg.ddx.io: the PostgreSQL community's memory's hosted MCP server, published by pg.ddx.io; no sign-in required; Streamable HTTP; 29 tools.
var.gg Naming Memory
gg.varOfficial publisher
Remote MCP server that suggests and searches code identifier names from domain concepts in Korean, Japanese, Chinese, Vietnamese and English, and exposes ERD…
Counterparts
ai.counterparts
Local-first long-term memory for Claude Code and Claude Desktop: the assistant writes notes about you and your projects and recalls them in later sessions.
LAHZE - Persian AI Memory Platform
Published by GitHub account pedramgholizadeh
LAHZE - Persian AI Memory Platform's hosted MCP server; no sign-in required; Streamable HTTP; 13 tools.
Manwe — Memory, Decisions & Agent Tasks
Published by GitHub account lemberalla
Shared local memory, decisions and approved agent tasks. Requires the installed Manwe Mac app.