Skip to main content

Alpha Progression MCP

Connect Claude (or any MCP client) to your Alpha Progression gym data: analyse your training and adjust your plan.

  • "Am I doing enough sets per week for each muscle?"
  • "Which lifts have stalled in the last 3 months?"
  • "Add a hamstring exercise to Day 2 and lower bench to 4 × 6."

Unofficial, not affiliated with Alpha Progression. Use it only with your own account.

Setup

Requires uv.

  1. Log in once. Your email and password are not saved, only an access token (~/.config/alpha-progression-mcp/token.json):
    uvx alpha-progression-mcp login
    
  2. Add it to Claude Code:
    claude mcp add alpha-progression -- uvx alpha-progression-mcp
    
    Other clients:
    {
      "mcpServers": {
        "alpha-progression": {
          "command": "uvx",
          "args": ["alpha-progression-mcp"]
        }
      }
    }
    
  3. Restart your client.

Tools

Tool Returns
get_weekly_training Sets and training days per muscle, per week
get_progress Lifts improving or stalled, by muscle group (e1RM)
get_sessions / get_session Recent workouts / every set of one workout
get_exercise_history One exercise over time
find_exercises Exercises by name or muscle
get_plans Your current plan with set and rep targets
get_measurements Bodyweight and other measurements
get_document Any single record
set_plan_targets / add_plan_exercise / swap_plan_exercise / remove_plan_exercise Change one thing in your plan

Plan editing makes one targeted change per call, previews it first and only saves after you approve. Workout history is never touched; a backup of the plan is saved to ~/.config/alpha-progression-mcp/backups/ before each change, and it only changes what the free version of the app can (no RIR targets, deloads or periodisation). Changes appear in the app after it syncs. To turn editing off, set ALPHA_PROGRESSION_READ_ONLY=1.

Names can be partial ("bench press", "day 2"); unclear ones return suggestions.

Metrics: working sets exclude warm-ups (lighter sets before the first heavy set) and stretches. Sets per muscle count 1 for the target muscle and 0.5 for its main secondary muscles (fractional counting, Pelland et al. 2024). e1RM uses Epley, weight × (1 + reps / 30), up to 15 reps.

Troubleshooting

  • "Not logged in" / "login has expired": run the login command again.
  • "Too many login attempts": wait a few minutes; Alpha Progression locks login after wrong passwords.
  • Check the connection: uvx alpha-progression-mcp status
  • Log out: delete ~/.config/alpha-progression-mcp/token.json.

Development

uv sync && uv run pytest && uv run ruff check . && uv run ruff format .

The sync protocol is described in docs/api.md. MIT license.

Metadata

Release files for alpha-progression-mcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for alpha-progression-mcp 0.1.1
File Size Uploaded Provenance
alpha_progression_mcp-0.1.1.tar.gz 196.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for alpha-progression-mcp 0.1.1
File Interpreter ABI Platform
alpha_progression_mcp-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 225.9 kB

Release files / alpha_progression_mcp-0.1.1.tar.gz

Download URL alpha_progression_mcp-0.1.1.tar.gz
Size 196.7 kB
Tags Source
SHA-256 checksum
How to use checksums
073f13f08b401d5dafae9bdf03eb20b3d7e74f6ec5064a80dd1d916959565f32
BLAKE2b-256 checksum
How to use checksums
7b91a2d8c64aafbb035f0834cedd9736ce11f3ba7cf1e1b5698eb44044e2bb92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / alpha_progression_mcp-0.1.1-py3-none-any.whl

Download URL alpha_progression_mcp-0.1.1-py3-none-any.whl
Size 29.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0d00f9b429254411822d2f76688fcc543a55d6b6e8c965c9413c1017276ce235
BLAKE2b-256 checksum
How to use checksums
20fce46193be1d96bb9e87fc8cca7e064ce8e968d7f45c653b848d5db14d091b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for alpha-progression-mcp 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page