使用说明
mcp-wger
Wger MCP — wraps wger Workout Manager REST API (free, no auth for read)
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tools
| Tool | Description |
|---|---|
list_exercises |
List fitness exercises from the wger database in English; optionally limit count (default 20). Returns exercise name, description, category, primary and secondary muscles, and required equipment per entry. |
get_exercise |
Get detailed information for a specific exercise by its numeric ID. |
list_muscles |
List all muscles tracked in the wger database. Returns each muscle's numeric ID, English name, and whether it is located on the front of the body. |
list_equipment |
List all gym equipment types in the wger database. Returns each item's numeric ID and name (e.g., 'Barbell', 'Dumbbell', 'Kettlebell'). |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"wger": {
"url": "https://gateway.pipeworx.io/wger/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/wger/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/list_exercises \
-H 'Content-Type: application/json' \
-d '{"limit":20}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_exercises. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"wger": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-wger"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-wger
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Wger data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT