Health Data (your own… vs Read Only Local Postg… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Health Data (your own Supabase) vs Read Only Local Postgres MCP Server
In-depth architectural comparison of the Health Data (your own Supabase) and Read Only Local Postgres MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Health Data (your own Supabase)
Databases · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Read Only Local Postgres MCP Server
Databases · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Health Data (your own Supabase) if you need specialized Databases tools running via a local process. Choose Read Only Local Postgres MCP Server if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Health Data (your own Supabase) when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
The Postgres schema (two tables) and the metric registry (names, units, classes). Call before writing SQL for the query tool.
get_sync_status
Latest date, row count, and days-since-last-entry per metric. Use to detect a stalled daily sync before trusting an analysis.
get_recent
Rows for the last N days (default 30), optionally one metric. Daily totals and individual measurements in one date-sorted list.
get_daily_summary
All metrics for one day (default: the most recent day with any data): totals plus every weigh-in/measurement.
get_stats
Min/max/avg plus a rolling-average series for one metric over a date range (daily/weekly/monthly rollup).
query
Escape hatch: run one read-only SQL statement (SELECT or WITH…SELECT) against the schema from get_schema. Writes/DDL rejected; LIMIT 500 enforced.
get_energy_inputs
Daily (date, weight, kcal) entries for days with both a calorie total and a weigh-in — shaped exactly for fitness-tools' `adaptive-tdee`.
Read Only Local Postgres MCP Server Tools (3)
connect
Connect to a PostgreSQL database using a connection string. The connection persists for subsequent queries until changed or disconnected. The target must be `DB_HOST:DB_PORT` or listed in `DB_ALLOWED_HOSTS`.
disconnect
Disconnect from the current runtime database and revert to the default environment-configured connection.
query
Run a read-only SQL query against the currently connected database. Optionally override the connection for a single query.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Health Data (your own Supabase) is categorized under Databases and uses a local stdio subprocess. In contrast, Read Only Local Postgres MCP Server belongs to Databases using local stdio subprocess. Select Health Data (your own Supabase) when you need capabilities focused on databases and Read Only Local Postgres MCP Server when you require tools for databases.