Tally Workout

io.github.westveghPublished by GitHub account westveghv1.1.0Updated Oct 24, 2026

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

The publisher's own server: Tally

VerifiedStreamable HTTPWeb executableLocation & Lifestyle Productivity & Workflow

Server details

Identifier: io.github.westvegh/tally-workout
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account westvegh for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.westvegh%2Ftally-workout.svg)](https://sourceweft.com/mcp/io.github.westvegh%2Ftally-workout?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server for Tally, a free iPhone strength log, letting an assistant read your training history and plan or edit workouts in the app.

What you can do: Read training context, workout history, single workouts, planned days and saved templates
Check exercise progress, estimated 1RM, exercise details and weekly training summaries
Create or replace planned days, including ranges of up to 31 days, and update, move, skip or delete plans
Log, change, delete or restore finished workouts, and list restorable versions
Send a feedback message to the Tally team
When to use it: Useful if you log lifts in the Tally iPhone app and want an assistant to plan next week's sessions from what you actually lifted, review progress, or make requested changes to finished workouts.
Requirements: Remote Streamable HTTP endpoint; no local install. Needs the Tally iPhone app and a Tally account. Authentication is OAuth 2.1 (scope workouts) or, for clients without OAuth, an API key from the app's Settings sent as an Authorization bearer header. Write access to finished workouts requires a Full access key or an OAuth connection.

Before you install

The server can create, change, move, skip and delete planned days, and log, update, delete or restore finished workouts; changes are kept for 7 days for undo. Keys are read-only, read-and-plan, or full access, and do not expire, so revoke unused ones in the app. Days built or edited in the app are protected unless an override is requested. Version checks reject writes if data changed after reading.

Installation

In SourceWeft

Open Tally Workout 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/io.github.westvegh%2Ftally-workout/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

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.

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.1.0LatestOct 15, 2026
v1.0.0Sep 16, 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 Tally integrations

Tally

markets.tallyOfficial publisher

Tally is a remote MCP server that keeps a private trading journal — theses, evidence, exit criteria and decision history — for AI-assisted trading, with no…

Streamable HTTPWeb executableAuth

FinanceCredential requiredOct 27, 2026

Tally Mcp

Published by GitHub account mrfentmen

Query Tally (key; set TALLY_API_KEY, Bearer): forms, form details, submissions.

STDIODesktop only

Not validated yetOct 24, 2026

ComplyEaze Bridge

Published by GitHub account ComplyEaze

Claude Desktop extension that reads a local TallyPrime book and proposes Payment, Receipt and Contra vouchers from Indian bank statement PDFs.

STDIODesktop only

Files & StorageNot validated · the package type cannot run in the sandboxNov 6, 2026

FabTally Utility Belt

Published by GitHub account zvmzaretsky

A remote MCP server offering 13 deterministic utilities — unit conversion, hashing, encoding, IDs, regex, time zones, cron, RRULE, currency, diff, JSON Schema —

Streamable HTTPWeb executable

Developer Tools13 toolsOct 24, 2026

FabTally Decode

Published by GitHub account zvmzaretsky

Remote MCP server that decodes raw EVM data — event logs, calldata, selectors and contract ABIs — into readable JSON for six chains.

Streamable HTTPWeb executable

Finance4 toolsOct 24, 2026

Tally Workout

Overview

Installation

In SourceWeft

Use with an agent

Other MCP clients

README

Tally Workout MCP server

Endpoint

Setup by agent

Tools

Rules

Links

Tools

Version history

Score

Other Tally integrations

Tally

Tally Mcp

ComplyEaze Bridge

FabTally Utility Belt

FabTally Decode