PumpX
app.pumpxPublished by pumpx.appOfficial publisherv1.0.0Updated Oct 24, 2026
Read-only access to your PumpX workout log: sessions, lift history, PRs, routines, measurements.
Overview
Read-only access to a PumpX workout log, letting an assistant look up training sessions, lift history, personal records, routines and measurements.
- What you can do
- Connects an assistant to a PumpX account through a remote MCP endpoint and exposes the workout log for reading. According to the registry description, it covers training sessions, lift history, personal records (PRs), routines and body measurements. No individual tool names or parameters are published, so the exact queries available are not documented.
- When to use it
- Useful when you want an assistant to answer questions about your own training data, such as reviewing recent sessions, tracking progress on a lift, checking PRs, or looking at saved routines and measurements. It is a read-only view, so it is not intended for logging or editing workouts.
- Requirements
- A remote MCP endpoint at mcp.pumpx.app over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and is required, so you need a PumpX account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open PumpX 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/app.pumpx%2Fpumpx/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": {
"pumpx": {
"type": "http",
"url": "https://mcp.pumpx.app/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.