Tally Workout

io.github.westvegh由 GitHub 帳號 westvegh 發布v1.1.0更新於 Oct 24, 2026

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

發布方自己的服務:Tally

已驗證Streamable HTTP可網頁執行位置與生活效率與工作流

概覽

AI 產生的概覽

Tally 這款免費 iPhone 重量訓練紀錄的遠端 MCP 伺服器,讓助理讀取你的訓練歷史,並在應用程式中規劃或修改訓練。

可以做什麼
  • 讀取訓練脈絡、訓練歷史、單次訓練、預定日與已儲存範本
  • 查看動作進度、估算 1RM、動作詳細資料與每週訓練彙總
  • 建立或取代預定日(單次最多 31 天),並更新、移動、略過或刪除計畫
  • 記錄、修改、刪除或還原已完成的訓練,並列出可還原的版本
  • 向 Tally 團隊傳送意見回饋訊息
適用情境
適合在 Tally iPhone 應用程式中記錄重量訓練,並希望助理依實際舉重情況規劃下週訓練、回顧進度,或依你的要求修改已完成訓練的使用者。
執行需求
遠端 Streamable HTTP 端點,無需本機安裝。需要 Tally iPhone 應用程式與 Tally 帳號。驗證方式為 OAuth 2.1(範圍 workouts),或不支援 OAuth 的用戶端使用應用程式設定中建立的 API 金鑰,透過 Authorization 標頭以 Bearer 方式傳送。修改已完成訓練需要 Full access 金鑰或 OAuth 連線。
安裝前請注意
此伺服器可建立、修改、移動、略過與刪除預定日,也可記錄、更新、刪除或還原已完成訓練;變更保留 7 天可復原。金鑰分為唯讀、唯讀加規劃、完整存取三種,且不會過期,請在應用程式中撤銷不再使用的金鑰。在應用程式中建立或編輯過的預定日受保護,除非明確要求覆寫。若資料在讀取後有變動,版本檢查會拒絕寫入。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Tally Workout,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.westvegh%2Ftally-workout/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "tally-workout": {
      "type": "http",
      "url": "https://mcp.tallyworkout.app/api/mcp"
    }
  }
}

README

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.

AgentAuthSteps
Claude (web, desktop, phone)OAuthAdd Tally Workout from Claude's directory. Steps
Claude CodeOAuth or API keyclaude mcp add --scope user --transport http tally https://mcp.tallyworkout.app/api/mcp, then /mcp. Steps
CodexAPI keyThree lines in ~/.codex/config.toml. Steps
ChatGPTOAuthDeveloper mode. Pro reads only. Business, Enterprise and Edu can plan. Steps
MuseOAuthClient ID tally-muse. Steps
HarkAPI keySteps
PerplexityAPI keySteps
DotsAPI keyNot tested yet. Steps
Any MCP clientOAuth or API keySteps

Tools

21 tools: 10 read, 11 write.

ToolTypeWhat it does
get_training_contextreadReturns planned days from today, the weight unit and, with historyWeeks, recent workouts.
get_workout_historyreadReturns logged workouts, newest first, set by set. Each workout has a stable id.
get_workoutreadReturns one logged workout by its id, set by set.
get_exercise_progressreadReturns progress for up to 10 exercises over the last 365 days, with top sets and estimated 1RM.
get_planned_workoutreadReturns one planned day in full, with its version.
search_exercisesreadMatches exercise names to the user's recent exercises and the Tally library.
get_exercisereadReturns one exercise by its id: muscles, equipment and instructions, or the user's custom exercise.
get_training_summaryreadReturns weekly totals for up to 12 weeks: workouts, sets, volume, time, volume by muscle, and missed or skipped plans.
get_saved_workoutsreadReturns the user's saved and favorite workout templates.
get_workout_versionsreadLists the restorable versions of one finished workout, also a deleted one.
plan_workout_daywriteCreates or replaces one planned day.
plan_workout_rangewriteCreates or replaces up to 31 planned days in one call.
update_planned_workoutwriteChanges part of one planned day: add, remove or change exercises.
move_planned_workoutwriteMoves a planned day to an empty date.
skip_planned_workoutwriteMarks a planned day as skipped, or restores it. Only the status changes.
delete_planned_workoutwriteRemoves a planned day and returns it, so you can undo.
log_workoutwriteLogs a finished workout to the user's history. Full access.
update_workoutwriteChanges one finished workout at its current version: fields, exercises or sets. Full access.
delete_workoutwriteDeletes one finished workout at its current version. Full access.
restore_workoutwriteMakes an earlier version of a finished workout current again, within 7 days, also after a delete. Full access.
send_feedbackwriteSends 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.

Links

來源:README.md,提交 775cec5

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

2
  1. v1.1.0最新Oct 15, 2026
  2. v1.0.0Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Tally 整合