← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionQuickBooks Online MCP ServerAccess QuickBooks Online data and accounting operations through MCP.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS32 / 100 · D77 / 100 · B
Reliability4 / 2012 / 20
Security and permissions7 / 2016 / 20
Maintenance6 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience7 / 2015 / 20
Best for
  • Developers integrating QuickBooks Online data or accounting operations
  • Local integrations using Claude Code or another MCP-compatible client
  • Teams needing sandbox testing or production company access
  • 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 who do not use QuickBooks Online
  • Users unable to register an Intuit app and complete OAuth authorization
  • Teams seeking a hosted service without a local process or credential 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
  • Requires Intuit OAuth 2.0 app credentials
  • Requires access to a QuickBooks Online company and its Realm ID
  • Depending on enabled tools, may require permission to read, create, update, and delete accounting data
  • 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
  • Write, update, and delete tools can change or void accounting records
  • Refresh tokens rotate automatically and are written back to a configuration file
  • Initial production OAuth authorization requires a public HTTPS callback
  • The source contains conflicting license information: Apache-2.0 in repository metadata and MIT in the README
  • 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 CodeClaude Desktop, Cursor, Codex, Antigravity
Tools10026