Skip to main content
Glama
Snovak99
by Snovak99
README.md
# 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

## Project Structure

```text
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.

```bash
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`.

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

ActivitySlowing
ResponsivenessNo issues