← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionNeo ChatA local-first AI chat workspace for models, agents, skills, plugins, search, RAG, voice, memory, and artifacts.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS58 / 100 · C77 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance14 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Individuals or teams who want control over their data and need a self-hosted AI chat workspace
  • Developers familiar with Next.js, React, and TypeScript
  • Users needing multi-provider integration and plugin extensibility
  • 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
  • Public multi-user services requiring a turnkey SaaS security boundary (accounts, tenant isolation)
  • Users who do not want to manage their own deployment and configuration
  • Users needing native agent orchestration (only limited Agent mode in browser)
  • 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
  • Browser storage access (localStorage, IndexedDB, OPFS)
  • Network access to connect to model providers, search, RAG, voice, and MCP servers
  • Server-side API routes execute plugins, MCP, and proxy requests
  • Optional server environment variables for deployment defaults and security
  • Docker deployments may expose port 3000
  • 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
  • Self-hosting entails security responsibilities; public exposure requires additional hardening
  • User-entered provider credentials are encrypted in the browser, but server misconfiguration could expose them
  • Hosted mode depends on shared stores like Upstash and restricts network policies
  • Remote MCP servers can execute tools; configure carefully
  • Data is stored in the browser by default; clearing browser data may cause loss unless backed up or synced
  • 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