Filesystem

Created By
chrisdoca year ago
Overview

what is hevy-mcp?

hevy-mcp is a Model Context Protocol (MCP) server that interfaces with the Hevy fitness tracking app, allowing AI assistants to manage workout data, routines, and exercise templates through the Hevy API.

how to use hevy-mcp?

To use hevy-mcp, install it via Smithery or manually clone the repository, install dependencies, and configure your Hevy API key in a .env file. Start the server in development or production mode as needed.

key features of hevy-mcp?

  • Fetch, create, and update workouts
  • Access and manage workout routines
  • Browse available exercise templates
  • Organize routine folders

use cases of hevy-mcp?

  1. Integrating fitness data management into AI applications.
  2. Automating workout tracking and routine management.
  3. Enhancing fitness apps with AI-driven insights and recommendations.

FAQ from hevy-mcp?

  • What is required to run hevy-mcp?

You need Node.js (v20 or higher), npm or yarn, and a Hevy API key.

  • Is there a cost associated with using hevy-mcp?

Accessing the Hevy API requires a PRO subscription to the Hevy app.

  • Can I contribute to hevy-mcp?

Yes! Contributions are welcome, and you can submit a Pull Request.

Server Config

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "hevy-mcp"
      ],
      "env": {
        "HEVY_API_KEY": "{HEVY_API_KEY}"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
chrisdoc
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago