Skip to main content
Glama
personal-mcp
by Snovak99

personal-mcp

A personal MCP server for connecting your own API integrations and exposing them as tools/resources/prompts.

Initial Scope

  • Fitness domain

  • Hevy provider integration

Related MCP server: Hevy MCP Pro

Project Structure

personal-mcp/
├── .github/
│   └── copilot-instructions.md
├── src/
│   ├── core/
│   │   ├── server/
│   │   ├── config/
│   │   ├── types/
│   │   └── utils/
│   ├── domains/
│   │   └── fitness/
│   │       ├── providers/
│   │       │   └── hevy/
│   │       ├── services/
│   │       ├── tools/
│   │       ├── resources/
│   │       ├── prompts/
│   │       └── types/
│   └── index.ts
├── tests/
│   ├── core/
│   └── domains/
│       └── fitness/
├── .env.example
├── package.json
├── tsconfig.json
└── README.md

Quick Start

  1. Install dependencies.

  2. Copy .env.example to .env and set your API key(s).

  3. Start in dev mode.

npm install
npm run dev

Next Steps

  • Implement Hevy API client methods.

  • Add MCP tools for recent workouts, exercise lookup, and training volume summaries.

  • Add domain-focused tests under tests/domains/fitness.

Available Tools

2 tools
hevy_recent_workoutsB

Return a placeholder list of recent Hevy workouts

Inputs: no named parameters.

hevy_statusB

Report whether Hevy API configuration is available

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one reports configuration status, the other returns workout data. There is no overlap in their purposes or expected outputs.

    Naming Consistency5/5

    Both tool names follow a consistent pattern: 'hevy_' prefix followed by a snake_case noun. This makes the naming predictable and easy to understand.

    Tool Count3/5

    With only two tools, the server feels thin and borderline under-scoped. While each tool serves a purpose, a typical server for a domain like workouts would benefit from more coverage.

    Completeness2/5

    The tool set is significantly incomplete for a Hevy workout integration. It only provides a status check and a placeholder list, lacking any real workout retrieval, creation, update, or delete operations.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Garmin Connect data and workout management to AI agents, supporting tools, resources, and prompts for health data, workout creation, and coaching workflows.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A production-ready MCP server for the Hevy fitness API that exposes 27 tools for reading, writing, and analyzing workout data, enabling LLM-driven personal trainer workflows.
      27
      10 npm
      MIT