PostgreSQL vs Read Only Local Postgres MCP Server

A side-by-side look at the PostgreSQL and Read Only Local Postgres MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

PostgreSQL logoPostgreSQLDatabases · Local subprocess (stdio)MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.64GoodAuth: not declaredRead Only Local Postgres MCP Server logoRead Only Local Postgres MCP ServerDatabases · Local subprocess (stdio)MCP server for read-only PostgreSQL database queries in Claude Desktop52GoodAuth: not declared

Verdict: choose PostgreSQL for databases work as a local process; choose Read Only Local Postgres MCP Server for databases as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

PostgreSQL logoChoose PostgreSQL when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like query, execute, list_schemas.
Explore PostgreSQL

Read Only Local Postgres MCP Server logoChoose Read Only Local Postgres MCP Server when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like connect, disconnect, query.
Explore Read Only Local Postgres MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPostgreSQL logoPostgreSQLRead Only Local Postgres MCP Server logoRead Only Local Postgres MCP Server
CategoryDatabasesDatabases
Quality signal64/100 · Good52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars242
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools53

Tools & capabilities

PostgreSQL tools 5

  • queryRun one read-only SQL statement against the connected PostgreSQL database and get rows back as JSON. Send exactly one statement per call (SELECT, WITH, EXPLAIN, or SHOW). It runs inside an engine-enforced read-only transaction, so any write is refused by the database. Use this tool for all data reading, aggregation, and query planning. Returns {rows, rowCount, returnedRows, truncated}, plus hint when truncated is true. Prefer $1, $2 placeholders with the params array over interpolating values. Results are capped at ~32768 bytes; truncated:true means rows were dropped - add LIMIT/WHERE or select fewer columns.
  • executeRun a data-modifying SQL statement (INSERT/UPDATE/DELETE or DDL). Currently DISABLED: the server is read-only, so this returns an error and changes nothing. To enable writes, the operator must start the server with PG_ALLOW_WRITE=true.
  • list_schemasList every schema in the connected database. Start here when exploring an unfamiliar database, then call list_tables for the schema you care about. Returns {schemas: [name, ...]}.
  • list_tablesList all tables in a schema (default: 'public'). Use this before querying tables you have not seen yet, then call describe_table for column details. Returns {tables: [name, ...]}.
  • describe_tableShow the structure of one table: column names, data types, nullability, defaults, and primary-key membership. Call this before writing non-trivial queries against a table. Returns {columns: [{column, type, nullable, default, is_primary_key}, ...]}.

Read Only Local Postgres MCP Server tools 3

  • connectConnect 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`.
  • disconnectDisconnect from the current runtime database and revert to the default environment-configured connection.
  • queryRun a read-only SQL query against the currently connected database. Optionally override the connection for a single query.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

PostgreSQL

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "postgresql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-postgres-server"
      ]
    }
  }
}

Read Only Local Postgres MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "read-only-local-postgres-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@hovecapital/read-only-postgres-mcp-server"
      ]
    }
  }
}

Frequently asked questions

PostgreSQL is categorized under Databases and uses a local stdio subprocess. Read Only Local Postgres MCP Server belongs to Databases and uses a local stdio subprocess. Pick PostgreSQL for databases work and Read Only Local Postgres MCP Server for databases.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

PostgreSQL has no declared pricing — check the project's own site. Read Only Local Postgres MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add postgresql and read-only-local-postgres-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, PostgreSQL has a quality signal of 64/100 (Good) with 4 views, 0 installs and 24 GitHub stars. Read Only Local Postgres MCP Server has 52/100 (Good) with 2 views, 0 installs and 2 GitHub stars.