PostgreSQL Full Access MCP Server

@kamusis

代码仓库

基本信息

分类

数据库

传输方式

stdio

作者

kamusis

关于 PostgreSQL Full Access MCP Server

A fully featured PostgreSQL server adapter for the Model Context Protocol (MCP), providing robust read/write access and enhanced schema metadata for LLM and AI-powered applications. Supports full SQL DML/DDL operations.

PostgreSQL Full Access MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-postgres-full-access-extended": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "mcp-postgres-full-access",
        "."
      ]
    }
  }
}

PostgreSQL Full Access MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is PostgreSQL Full Access MCP Server?

A Model Context Protocol server that provides full read-write access to PostgreSQL databases. It is an independently maintained fork of the original mcp-postgres-full-access, enabling LLMs to both query and modify database content with transaction management and safety controls.

How to use PostgreSQL Full Access MCP Server?

Install via npx and configure Claude Desktop by editing claude_desktop_config.json with the server command and connection string. Use environment variables to customize timeouts and safety limits. The server can also be run in a Docker container. Example configurations are provided in the README.

Key features of PostgreSQL Full Access MCP Server

Execute DML, DDL, DCL, and TCL operations with safety controls
Rich schema information including primary keys, foreign keys, and indexes
Transaction management with explicit commit and rollback
SQL query classification and automatic timeout monitoring
Two-step commit process requiring user approval
Docker support for containerized deployment

Use cases of PostgreSQL Full Access MCP Server

Create new tables and insert data with user approval
Perform read-only data analysis and reporting
Manage database objects and schema changes
Review and safely commit write transactions after verification

常见问题

How does PostgreSQL Full Access MCP Server differ from the official MCP PostgreSQL server?

The official server is read-only; this server provides full read-write access with transaction management and safety controls.

What environment variables are available?

Key variables include `TRANSACTION_TIMEOUT_MS`, `MAX_CONCURRENT_TRANSACTIONS`, `ENABLE_TRANSACTION_MONITOR`, `PG_STATEMENT_TIMEOUT_MS`, `PG_MAX_CONNECTIONS`, and `MONITOR_INTERVAL_MS`. Defaults are specified in the README.

What permissions should I grant the database user?

Create a dedicated user with restricted grants. Avoid superuser access. For example, grant SELECT on all tables and INSERT/UPDATE/DELETE only on specific tables as needed.

How does the two-step commit safety workflow work?

For write operations, the SQL executes in a transaction and the conversation ends. The user reviews results, then starts a new conversation saying "Yes" to commit or "No" to rollback.

Can I run this server in Docker?

Yes. Build the Docker image and run it with a PostgreSQL connection string. On macOS use `host.docker.internal` to reach the host network.

数据库分类下的更多 MCP 服务器

Dbhub

bytebase

Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.

3.1K

Schemity

tbson

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.