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.

DimensionMCP Email ServerA multi-account MCP server for reading, searching, organizing, and sending email via IMAP and SMTPHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS60 / 100 · C77 / 100 · B
Reliability8 / 2012 / 20
Security and permissions11 / 2016 / 20
Maintenance15 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Individuals or teams who want to read/search/organize/send email directly from an MCP client
  • Users with multiple IMAP/SMTP accounts who want unified management
  • Users comfortable with uv/uvx and local credential setup who can configure their own mail accounts
  • 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 unwilling to store email passwords/credentials locally
  • Setups requiring OAuth (e.g., modern Gmail/Outlook auth) rather than username/password login, which the source material does not confirm is supported
  • Users wanting a fully cloud-hosted email service with no local configuration
  • 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
  • Stores and uses email account credentials (username/password) in local keyring or managed SQLite storage
  • Reads and searches mailbox content via IMAP
  • Sends email on the user's behalf via SMTP
  • Local filesystem access to read/write configuration (TOML file or SQLite database)
  • 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
  • Email credentials are stored locally (legacy TOML/keyring, or managed SQLite in V2); exposure of this storage could allow unauthorized mailbox access
  • Granting an AI client the ability to send email creates risk of unintended or malicious sends via prompt misuse
  • Migrating from legacy configuration to V2 involves credential import, which can hit conflicts or missing-credential issues if done incorrectly
  • 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