Developer · Remote MCP server
Hevy Coach
Training analytics over your Hevy log: e1RM, PRs, volume, consistency, bodyweight.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.gCuadros/hevy-coach-mcp- Version
- 0.4.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- gCuadros (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/gCuadros) · how
- Repository
- github.com/gCuadros/hevy-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://hevy-mcp-alpha.vercel.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | hevy-coach-mcp | 0.4.2 | stdio |
How to connect Hevy Coach
Hevy Coach is a remote MCP server: there is nothing to install. Its endpoint is https://hevy-mcp-alpha.vercel.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: hevy-coach-mcp version 0.4.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y hevy-coach-mcp@0.4.2. It reads the environment variable HEVY_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"hevy-coach-mcp": {
"command": "npx",
"args": [
"-y",
"hevy-coach-mcp@0.4.2"
],
"env": {
"HEVY_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| heropen - AI Agent MemoryPersistent memory for AI agents: local-first MCP server, zero-config. No cloud, no API keys. | Local · stdio |
| HetznerMCP server for the Hetzner Cloud API - servers, networks, volumes, firewalls, and more. | Local · stdio |
| Hetzner CloudServers, volumes, networks, firewalls, load balancers, pricing and safe power operations. | Remote · HTTPLive check: ✓ handshake |
| Hetzner DNSManage DNS zones and records (zonefiles, RRSets, TTL, protection) via the Hetzner Cloud API. | Local · stdio |
| Hex GraphDeterministic layered code graph MCP server with framework overlays and SCIP interop. | Local · stdio |
| Hex LineHash-verified file editing MCP server with token efficiency hook for AI coding agents. | Local · stdio |
| Hex SSHToken-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools. | Local · stdio |
| HeyReachAutomate your HeyReach workspace - manage campaigns, leads, unibox, webhooks, and pull analytics. | Remote · HTTPLive check: sign-in required |