← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionCrawlbase MCP ServerConnect AI agents to real-time web data with JS rendering and anti-bot protection.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS50 / 100 · D77 / 100 · B
Reliability8 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • AI developers needing real-time web data.
  • Users integrating live data into Claude, Cursor, or Windsurf.
  • Scraping tasks requiring structured outputs (HTML, Markdown, screenshots).
  • Users needing async large-scale crawling with cloud storage.
  • 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
  • Scenarios not requiring real-time data and relying only on training data.
  • Users wanting fully local processing without external API dependencies.
  • Users needing complex custom crawler logic beyond simple fetching.
  • Strict compliance environments that do not allow third-party services.
  • 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 Crawlbase tokens (normal and JS) to access the API.
  • Network access: server must connect to Crawlbase services for crawling.
  • In HTTP mode, tokens can be provided via environment variables or request headers.
  • 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
  • Dependency on Crawlbase service availability and API limits.
  • Traffic to target sites may be blocked or violate their terms of service.
  • Misconfiguration or invalid tokens can cause failures.
  • Free tokens may have rate limits affecting large-scale use.
  • 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, Claude Code, Cursor, WindsurfClaude Desktop, Cursor, Codex, Antigravity
Tools726