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.

DimensionDataForSEO MCP ServerAccess DataForSEO SEO data through MCP.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS49 / 100 · D77 / 100 · B
Reliability7 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance9 / 2016 / 20
Documentation11 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • SEO teams that want to use DataForSEO APIs through AI assistants
  • Developers who need configurable modules, prompts, or response fields
  • Users needing local, HTTP, or Cloudflare Worker deployment
  • 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
  • General MCP users without a need for DataForSEO APIs
  • Users without DataForSEO API credentials
  • Users seeking browser automation, file storage, or database capabilities
  • 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
  • Requires a DataForSEO API username and password
  • Can access data from the enabled DataForSEO API modules
  • HTTP mode supports Basic Authentication or environment-based credentials
  • 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
  • API credentials must be protected when supplied through environment variables or Cloudflare secrets
  • Enabling many modules or full responses may increase response size and API usage
  • The README marks SSE transport as deprecated
  • Data availability and costs depend on the DataForSEO account and service limits
  • 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 clientsClaudeClaude Desktop, Cursor, Codex, Antigravity
Tools026