MusclesWorked

MCP server for musclesworked.com exercise-to-muscle mapping API, enabling client queries for muscles, exercises, and activation data.

javascript

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "csjoblom-musclesworked-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "musclesworked-mcp",
        "--api-key",
        "mw_live_..."
      ],
      "env": {
        "MUSCLESWORKED_API_KEY": "mw_live_...",
        "MUSCLESWORKED_API_URL": "https://staging.musclesworked.com"
      }
    }
  }
}

This MCP server provides access to the musclesworked.com exercise-to-muscle mapping API, enabling MCP clients to query 320+ exercises and 65 muscles with detailed activation data. You can connect tools like Claude Desktop, Claude Code, Cursor, and other MCP clients to retrieve muscle activation information and analyze workouts through the unified MCP interface.

How to use

You integrate this server into your MCP client by configuring a local or remote MCP connection that passes your API key to the server. Use the available tools to discover muscles, map exercises to muscles, analyze workouts, and find suitable alternatives based on muscle overlap.

How to install

Prerequisites: ensure you have Node.js and npm installed on your system.

# Install dependencies for the MCP server
npm install

# Build the MCP server for production or local testing
npm run build

# Test run with MCP Inspector (optional, for development)
MUSCLESWORKED_API_KEY=mw_live_... npx @modelcontextprotocol/inspector node dist/index.js

Configuration and usage notes

Set your API key to authorize requests to musclesworked. You can provide the key either as an environment variable or as a command-line argument when starting the MCP server.

API key options:

Command-line: use the --api-key flag when starting the MCP client integration.
Environment variable: MUSCLESWORKED_API_KEY can be provided to the server to authorize requests.

Optional base URL override:

MUSCLESWORKED_API_URL can be set to override the default base URL (default is https://musclesworked.com).

Typical usage patterns

Connect your MCP client to the musclesworked MCP server using the provided configuration examples. Once connected, you can query which muscles are activated by specific exercises, search for exercises targeting particular muscles, analyze workouts for coverage and gaps, and find alternatives to existing exercises based on muscle overlap.

Security considerations

Keep your API key secure. Do not expose the API key in public code or logs. Use environment variables or secure secret management in your deployment environment.

Examples of common prompts

What muscles does the barbell bench press work?
Find bodyweight exercises for my chest
Analyze my push day: bench press, overhead press, tricep pushdown, lateral raise
What are some alternatives to barbell squats?
Search for exercises that target the hamstrings

Available tools

get_muscles_worked

Retrieve primary, secondary, and stabilizer muscles activated by a specific exercise.

find_exercises

Find exercises that target a given muscle, with optional filters.

analyze_workout

Analyze a workout to assess muscle coverage, gaps, and imbalances.

get_alternatives

Find alternative exercises ranked by muscle overlap.

search_exercises

Search for exercises by name to obtain IDs.

search_muscles

Search muscles by name to obtain IDs.

Built by

VeilStrat

AI signals for GTM teams