M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionWitsyDesktop AI assistant and universal MCP client for many model providersHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS45 / 100 · D77 / 100 · B
Reliability6 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance11 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Desktop users who want one interface for many model providers
  • Users who want to run Ollama models locally
  • Users needing desktop shortcuts, document retrieval, or agent features
  • Developers integrating desktop AI actions through a localhost HTTP API
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Users seeking a standalone MCP server that provides tools to other MCP clients
  • Users seeking a confirmed client-specific MCP server configuration
  • Users who do not want to configure cloud API keys or install a local model runtime
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • Cloud models, search, generation, and speech services require the relevant API keys
  • Ollama requires a local installation and model files
  • Local-file RAG and the local filesystem plugin require access to selected files
  • Prompt Anywhere, AI commands, and global shortcuts interact with other desktop applications
  • The local HTTP API listens on localhost port 8090 by default, or the next available port
  • CLI installation may require creating system-level symlinks on macOS or Linux
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • User-provided API keys are used with configured third-party services; costs and data handling depend on those providers
  • Local files, prompts, and conversations may be sent to the selected cloud models or services
  • The HTTP API is localhost-only by default; exposing it through a reverse proxy requires user-configured authentication
  • MCP servers, Python execution, agents, and local-file features can expand the actions or data accessible to the model
  • The software is licensed under AGPL-3.0
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude Desktop, Cursor, Codex, Antigravity
Tools026