Musclesworked MCP logo

Musclesworked MCP

by csjoblom

Maps exercises to muscles, analyzes workout coverage, and suggests alternatives using the musclesworked.com API.

Install Musclesworked MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "csjoblom-musclesworked-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "musclesworked-mcp"
      ],
      "env": {
        "MUSCLESWORKED_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y musclesworked-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

csjoblom/musclesworked-mcp MCP server connects MCP clients to the musclesworked.com exercise-to-muscle mapping API. It provides data for 856 exercises, 65 muscles, and 14 muscle groups, including primary, secondary, and stabilizer activation. Use its tools to identify exercise targets, find exercises for a muscle, review workout gaps, or compare alternatives by muscle overlap. An API key from musclesworked.com is required.

Use cases

  • Identify muscles worked by a selected exercise
  • Find exercises targeting a specific muscle
  • Analyze a workout for coverage gaps and imbalances
  • Compare alternative exercises by muscle overlap

Key features

  • Maps 856 exercises to 65 muscles
  • Distinguishes primary, secondary, and stabilizer muscles
  • Analyzes workout coverage and gaps
  • Ranks alternatives by muscle overlap
  • Searches exercises and muscles by name
  • Supports optional API URL overrides

Tools6

What Musclesworked MCP lets your agent do. Expand a tool for its parameters.

Self-reported~100 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · musclesworked-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads131Package downloads in the last 30 days.
Last commit8mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed6Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Musclesworked MCP works

What csjoblom/musclesworked-mcp MCP server does

The csjoblom/musclesworked-mcp MCP server exposes exercise and muscle mapping data from musclesworked.com to MCP-compatible clients. Its dataset covers 856 exercises, 65 muscles, and 14 muscle groups. Exercise results distinguish between primary, secondary, and stabilizer muscles, which makes the server suitable for questions that need more detail than an exercise-name search.

The server supports both individual exercise lookups and broader workout analysis. An agent can identify the muscles involved in an exercise, locate exercises for a selected muscle, inspect a workout for coverage gaps or imbalances, and find alternatives ranked by how much muscle activation they share with the original movement.

How it works

The MCP client starts the local musclesworked-mcp package through npx. The process communicates with the musclesworked.com API and authenticates with an API key. The key can be supplied through the MUSCLESWORKED_API_KEY environment variable or through the server's --api-key option.

Two search tools help discover the identifiers needed for other queries. search_exercises searches exercise names, while search_muscles searches muscle names. Once an exercise or muscle ID is known, the remaining tools can retrieve mappings, filter exercise results, analyze a workout, or rank alternatives.

The base API URL defaults to https://musclesworked.com. It can be changed with MUSCLESWORKED_API_URL, which is useful when the API endpoint needs to be overridden. The provided setup examples show local stdio configuration for Claude Desktop, Claude Code, and Cursor.

Tools and capabilities

The csjoblom/musclesworked-mcp MCP server exposes six tools:

  • get_muscles_worked: Returns the primary, secondary, and stabilizer muscles associated with an exercise.
  • find_exercises: Finds exercises that target a specified muscle, with optional filters.
  • analyze_workout: Reviews a workout for muscle coverage, gaps, and imbalances.
  • get_alternatives: Finds replacement exercises and ranks them by muscle overlap.
  • search_exercises: Searches exercise names to help discover exercise IDs.
  • search_muscles: Searches muscle names to help discover muscle IDs.

These capabilities support prompts such as identifying the muscles used by a barbell bench press, finding bodyweight exercises for the chest, reviewing a push-day exercise list, comparing squat alternatives, or searching for hamstring exercises.

Setup and configuration

Create an API key through the musclesworked.com dashboard before starting the server. A Claude Desktop or Cursor configuration can run npx -y musclesworked-mcp and pass the key in the environment. Claude Code can use the same package and provide the key with --api-key.

For local development, the repository instructions use npm install followed by npm run build. The project is licensed under MIT.

The csjoblom/musclesworked-mcp MCP server does not document a no-key mode. Keep the API key out of prompts and source-controlled configuration files when deploying it for regular use.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Musclesworked MCP

Run it through npx with `npx -y musclesworked-mcp` and provide a musclesworked.com API key through `MUSCLESWORKED_API_KEY` or `--api-key`.

Yes. The README provides a Claude Desktop configuration using the npx package and `MUSCLESWORKED_API_KEY`.

Yes. The README includes a `.cursor/mcp.json` configuration for running the server with Cursor.

It provides tools for muscle lookups, muscle-targeted exercise searches, workout analysis, alternative exercises, exercise-name searches, and muscle-name searches.

It requires an API key from the musclesworked.com dashboard, supplied with `MUSCLESWORKED_API_KEY` or the `--api-key` option.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMusclesworked MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/csjoblom-musclesworked-mcp?style=directory)](https://allmcps.com/mcp/csjoblom-musclesworked-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/csjoblom-musclesworked-mcp"><img src="https://allmcps.com/api/badge/csjoblom-musclesworked-mcp?style=directory" alt="Musclesworked MCP on AllMCPs" /></a>