Povver — Strength Training
ai.povverPublished by povver.aiOfficial publisherv2.0.0Updated Oct 28, 2026
Your strength-training data for any AI assistant: workouts, progress, muscle volume, routines.
Overview
Hosted MCP server that connects an AI assistant to a Povver account's strength-training data: workouts, progress, muscle volume and routines.
- What you can do
- Read training context, plans, finished workouts, live session state, memory and periodization
- Analyze strength progress, weekly volume and fatigue, adherence, single-lift trends and pending recommendations
- Search the exercise catalog and read muscles, equipment and execution notes
- Create or edit routines and templates, set the active routine, log or correct workouts
- Act on the in-progress workout: log sets, swap or add exercises, pair supersets, finish the session
- Manage periodization policies and training memory, and permanently delete workouts, routines or templates
- When to use it
- Useful for lifters with a Povver account who want an assistant to review training history, spot plateaus or under-trained muscle groups, and adjust programs or log sessions conversationally.
- Requirements
- Remote Streamable HTTP endpoint with OAuth 2.1 sign-in; nothing to install. Requires a Povver account with a premium subscription (iOS app). For automation, an API key created in the app's developer access settings is sent as a Bearer token.
Installation
In SourceWeft
- Open Povver — Strength Training 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/ai.povver%2Fmcp-server/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": {
"povver-strength-training": {
"type": "http",
"url": "https://mcp.povver.ai/mcp"
}
}
}README
Povver MCP Server
Connect your AI assistant to your Povver strength-training data — Claude, Claude Code, Cursor, or any MCP-compatible client. Read workout history, track strength progress, analyze muscle-group volume, and manage routines and templates from a conversation.
Endpoint: https://mcp.povver.ai/mcp (Streamable HTTP, OAuth 2.1)
Docs: https://mcp.povver.ai/ · /llms.txt · /llms-full.txt
Requires: a Povver account with a premium subscription (iOS app)
This is a hosted, remote server — there is nothing to install. Sign in with your Povver account when your client prompts you.
Povver also publishes strength calculators: RPE and RIR, one rep max, DOTS, FFMI, strength standards and weekly sets, each with its method and sources.
Listed on: Official MCP Registry (ai.povver/mcp-server) · Glama · Smithery · awesome-remote-mcp-servers
[Glama score] [smithery badge]
Connect
Claude (Desktop / web)
Settings → Connectors → Add custom connector → URL https://mcp.povver.ai/mcp. Claude opens a browser window to sign in with your Povver account.
Claude Code
Cursor / other clients
API key (automation, scripts, n8n)
In the Povver app: More → Integrations → Developer access → create a key, then send it as a Bearer token:
Example prompts
- "Act as my strength coach: review my recent training, find my biggest weakness, and update my program to fix it."
- "How's my bench press trending over the last 8 weeks — am I still progressing or have I plateaued?"
- "Break down my weekly training volume by muscle group. Where am I under-training?"
- "What should I train today?"
Available tools
One tool per kind of thing (your context, plans, workouts, the session in progress, analysis, exercises, memory, periodization). Each takes a view (reads) or an action (writes) and only that choice's fields. Every tool carries a display title and readOnlyHint / destructiveHint annotations, and delete is the only destructive one.
Changed in 2.0.0: the single-purpose tools of 1.x were consolidated into these (get_workout is now read_workouts with view: detail, create_template is save_plan with action: create_template, and so on), and explain_rule became the resource povver://rules/{rule_id}. The old names are not kept as aliases: a saved prompt that names one needs the new name. Clients pick up the new list when they reconnect.
Read (safe to call freely)
Write (change your data)
Resources
Attachable as context from a client's "+" menu:
- Training Status — weekly adherence, next workout, days since training
- Active Routine — current program structure
- Recent Workouts — last 10 session summaries
- Training Analysis — AI insights and weekly review
- Individual workouts and templates — browsable by ID
- Tool guide (
povver://guide/tools) and Periodization guide (povver://guide/periodization) — how to import history, edit templates without erasing them, run a live session, read volume - Training rules (
povver://rules/{rule_id}) — the evidence behind each of Povver's training rules, the same cards the in-app coach answers from
Prompts
- Analyze my training week — volume, adherence, and recommendations
- What should I train today? — next workout recommendation
- Review exercise progress — strength trends for a specific lift
- Review my training program — full program structure evaluation
Security & privacy
- OAuth 2.1 with PKCE and dynamic client registration; API keys are hashed at rest and revocable from the app.
- Every request is scoped to the signed-in user; tools only ever touch that user's data.
- Privacy policy: https://povver.ai/privacy · Terms: https://povver.ai/tos
- Support: mailto:[email protected]
The server source is part of Povver's private codebase; this repository holds the public documentation and the MCP Registry manifest (server.json).
Source: README.md at commit 87da559
Tools
0Version history
3- v2.0.0LatestOct 19, 2026
- v1.0.1Sep 21, 2026
- v1.0.0Sep 17, 2026
Score
75% 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
Declare a license in the repository or the registry entry.