Postgres MCP Pro Server: Setup for Claude, Cursor and Other Apps

• Lists the schemas in your database

  Returns every schema in the Postgres instance.

  Try: “What schemas does this database have?”

  Read · list_schemas

• Lists tables, views, sequences and extensions

  Shows the objects inside one schema.

  Try: “List the tables in the public schema.”

  Read · list_objects

• Shows a table's columns, constraints and indexes

  Returns the structure of one table, view or other object.

  Try: “Describe the orders table.”

  Read · get_object_details

• Runs SQL on your database

  Runs any SQL statement you or the assistant write. In the default unrestricted mode it can insert, update and delete data and change the schema. In restricted mode it only runs read-only transactions with a time limit.

  Try: “Show the 10 newest rows in orders.”

  Delete · execute_sql

• Shows how Postgres would run a query

  Returns the execution plan and cost estimates for a query. It can also test the effect of indexes that do not exist yet.

  Try: “Explain the plan for this slow query.”

  Read · explain_query

• Finds your slowest queries

  Reports the queries that took the most total time, using the pg_stat_statements data.

  Try: “Which queries are slowest?”

  Read · get_top_queries

• Suggests indexes for your whole workload

  Looks at the most expensive queries and recommends indexes that would speed them up.

  Try: “Which indexes should I add?”

  Read · analyze_workload_indexes

• Suggests indexes for specific queries

  Takes up to 10 queries you give and recommends indexes for them.

  Try: “Recommend indexes for these three queries.”

  Read · analyze_query_indexes

• Runs a database health check

  Checks cache hit rates, connections, constraints, duplicate or unused indexes, sequence limits and vacuum health.

  Try: “Check the health of my database.”

  Read · analyze_db_health

Watch out for

• It can change or delete data by default

  The default mode is unrestricted, and the SQL tool runs any statement. Use --access-mode=restricted, and a database user with limited rights. github.com

• Restricted mode is not a guarantee

  The authors say restricted mode is conservative but may not yet be safe for production databases. Prefer a read-only database user as well. github.com

• Password sits in the connection string

  The database password is part of the connection string in your client config. Keep that file private. github.com

Security advisories