Tally Workout

Name: Tally Workout
Author: westvegh

作者：westvegh版本 1.1.0i★ –i在云端运行

注册名称io.github.westvegh/tally-workout

安装

概览

作者提供的说明（英文原文）

iPhone strength log. Any MCP agent reads your training and plans workouts in the Tally app.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 诊所与健康
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http tally-workout https://mcp.tallyworkout.app/api/mcp --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "tally-workout": {
      "url": "https://mcp.tallyworkout.app/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "tally-workout": {
      "type": "http",
      "url": "https://mcp.tallyworkout.app/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密 HTTP header
Optional. OAuth 2.1 is the default. For clients without OAuth: Bearer .

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

服务器要求先登录，才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 westvegh 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 266 毫秒内响应（HTTP 401）
✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1026 个服务器的 0%
发布到注册中心的时间比此分类中其他 1026 个服务器的 56% 更新
基础检查结果等于或优于此分类中其他 1026 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Tally Workout 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.1.0）于23天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

作者：thetahealth正在增长↓ 290/周★ 1408昨天更新

在你的电脑上运行✓ thetahealth.ai

安装

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

作者：wso2正在增长↓ 823/周★ 13710天前更新

在你的电脑上运行

安装

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

作者：davidmosiah正在增长↓ 1024/周★ 794个月前更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Tally Workout MCP server

Docs for the remote Model Context Protocol server of Tally Workout, a free iPhone strength log. Your AI agent reads your training history and plans workouts in the Tally app. You log every set at the gym. Next week, the agent plans from what you actually lifted. When you ask, the agent can also log, change or delete a finished workout, and you can undo each change for 7 days.

It works with Claude, Claude Code, Codex, ChatGPT, Muse, Hark, Perplexity, Dots and any MCP client that supports OAuth 2.1 or a bearer token.

This repo holds the public docs. The server is first-party and closed source. It runs

as part of the Tally backend.

Endpoint

https://mcp.tallyworkout.app/api/mcp

Transport: Streamable HTTP. No SSE-only mode.
Auth, option 1: OAuth 2.1, authorization code + PKCE (S256), public client, dynamic client registration (RFC 7591). Scope: workouts.
Auth, option 2: an API key, for clients without OAuth. Create it in the Tally app under Settings → API keys. Send it as Authorization: Bearer tally_ct_…. A key is Read only, Read and plan, or Full access. Only a Full access key or an OAuth connection can change finished workouts. Keys do not expire. Revoke a key in the app.
Discovery: /.well-known/mcp-server, agent brief (llms.txt).

Setup by agent

You need the Tally iPhone app and a Tally account. Each link has the full steps.

Agent	Auth	Steps
Claude (web, desktop, phone)	OAuth	Add Tally Workout from Claude's directory. Steps
Claude Code	OAuth or API key	`claude mcp add --scope user --transport http tally https://mcp.tallyworkout.app/api/mcp`, then `/mcp`. Steps
Codex	API key	Three lines in `~/.codex/config.toml`. Steps
ChatGPT	OAuth	Developer mode. Pro reads only. Business, Enterprise and Edu can plan. Steps
Muse	OAuth	Client ID `tally-muse`. Steps
Hark	API key	Steps
Perplexity	API key	Steps
Dots	API key	Not tested yet. Steps
Any MCP client	OAuth or API key	Steps

Tools

21 tools: 10 read, 11 write.

Tool	Type	What it does
`get_training_context`	read	Returns planned days from today, the weight unit and, with `historyWeeks`, recent workouts.
`get_workout_history`	read	Returns logged workouts, newest first, set by set. Each workout has a stable id.
`get_workout`	read	Returns one logged workout by its id, set by set.
`get_exercise_progress`	read	Returns progress for up to 10 exercises over the last 365 days, with top sets and estimated 1RM.
`get_planned_workout`	read	Returns one planned day in full, with its version.
`search_exercises`	read	Matches exercise names to the user's recent exercises and the Tally library.
`get_exercise`	read	Returns one exercise by its id: muscles, equipment and instructions, or the user's custom exercise.
`get_training_summary`	read	Returns weekly totals for up to 12 weeks: workouts, sets, volume, time, volume by muscle, and missed or skipped plans.
`get_saved_workouts`	read	Returns the user's saved and favorite workout templates.
`get_workout_versions`	read	Lists the restorable versions of one finished workout, also a deleted one.
`plan_workout_day`	write	Creates or replaces one planned day.
`plan_workout_range`	write	Creates or replaces up to 31 planned days in one call.
`update_planned_workout`	write	Changes part of one planned day: add, remove or change exercises.
`move_planned_workout`	write	Moves a planned day to an empty date.
`skip_planned_workout`	write	Marks a planned day as skipped, or restores it. Only the status changes.
`delete_planned_workout`	write	Removes a planned day and returns it, so you can undo.
`log_workout`	write	Logs a finished workout to the user's history. Full access.
`update_workout`	write	Changes one finished workout at its current version: fields, exercises or sets. Full access.
`delete_workout`	write	Deletes one finished workout at its current version. Full access.
`restore_workout`	write	Makes an earlier version of a finished workout current again, within 7 days, also after a delete. Full access.
`send_feedback`	write	Sends a message from the user to the Tally team. Limit: 5 messages a day.

Rules

Finished workouts change only when the user asks. log_workout, update_workout, delete_workout and restore_workout need a Full access key or an OAuth connection. update_workout and delete_workout need the workout's version from get_workout as expectedVersion. Each change keeps the earlier content for 7 days: get_workout_versions lists it and restore_workout brings it back. All except restore_workout need a phone on the current Tally app.
Some days are protected. A day the user built in the app, or edited, is protected. The plan, update, move and delete tools skip it unless the user asks for an override.
Edits check the version. If a day or a finished workout changed after the agent read it, nothing is written and the result reports a conflict.
Each user sees only their own data. OAuth tokens and API keys are scoped to one account. The user can revoke them at any time.