MCP Server Motherduck vs PostgreSQL

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

MCP Server Motherduck logoMCP Server MotherduckDatabases · Local subprocess (stdio)Fast analytics and data processing with DuckDB and MotherDuck56GoodAuth: not declaredPostgreSQL logoPostgreSQLDatabases · Local subprocess (stdio)MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.64GoodAuth: not declared

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

Which MCP server should you choose?

MCP Server Motherduck logoChoose MCP Server Motherduck when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like execute_query, list_databases, list_tables.
Explore MCP Server Motherduck

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Motherduck logoMCP Server MotherduckPostgreSQL logoPostgreSQL
CategoryDatabasesDatabases
Quality signal56/100 · Good64/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 stars53424
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools45

Tools & capabilities

MCP Server Motherduck tools 4

  • execute_queryExecute SQL query (DuckDB dialect)
  • list_databasesList all databases (useful for MotherDuck or multiple attached DBs)
  • list_tablesList tables and views
  • list_columnsList columns of a table/view

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}, ...]}.

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.

MCP Server Motherduck

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ]
    }
  }
}

PostgreSQL

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

Frequently asked questions

MCP Server Motherduck is categorized under Databases and uses a local stdio subprocess. PostgreSQL belongs to Databases and uses a local stdio subprocess. Pick MCP Server Motherduck for databases work and PostgreSQL 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.

MCP Server Motherduck has no declared pricing — check the project's own site. PostgreSQL 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 mcp-server-motherduck and postgresql as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Server Motherduck has a quality signal of 56/100 (Good) with 3 views, 0 installs and 534 GitHub stars. PostgreSQL has 64/100 (Good) with 4 views, 0 installs and 24 GitHub stars.