easy-pg-admin-mcp
This server provides high-privilege PostgreSQL administration capabilities focused on database, role, and grant management — without supporting raw SQL execution or schema/table operations.
Database Management: List, create, inspect, and change owners of PostgreSQL databases. Dropping a database requires a short-lived confirmation token.
Role Management: List, create, alter passwords/attributes, and drop PostgreSQL roles. SUPERUSER privileges are explicitly unsupported, and dropping roles requires a confirmation token.
Role Membership: Grant/revoke roles to/from other roles, and view memberships for a specific role.
Privilege Management: Grant/revoke database-level privileges to/from roles, and view grants for a role on a database.
Secure Destructive Actions:
pg_drop_databaseandpg_drop_roleare protected by short-lived, single-use confirmation tokens executed viapg_confirm_task.Safety Guarantees: No raw SQL passthrough, and no management of schemas, tables, views, indexes, triggers, or functions.
Provides tools for managing PostgreSQL databases and roles, including creating, altering, and dropping databases and roles, as well as granting and revoking privileges.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@easy-pg-admin-mcp create a role named 'analyst' without login"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
easy-pg-admin-mcp
High-privilege PostgreSQL admin MCP server for database and role/grant management.
This project is a DBA-style tool. It does not provide raw SQL execution and does not manage tables, schemas, views, indexes, triggers, or functions. Use easy-pg-mcp for data access and schema/table operations.
Features
List, create, inspect, and change owners for databases
List, create, update, and drop PostgreSQL roles
Grant and revoke role memberships
Grant and revoke database-level privileges
Protect destructive actions with short-lived confirmation tokens
Related MCP server: PostgreSQL MCP Server
Available Tools
Tool | Description |
| List databases in the current PostgreSQL instance |
| Create a PostgreSQL database |
| Inspect a PostgreSQL database |
| Change a database owner |
| Request database deletion and return a confirmation token |
| List PostgreSQL roles |
| Create a PostgreSQL role without SUPERUSER support |
| Change a role password |
| Change supported role attributes |
| Request role deletion and return a confirmation token |
| Grant a role to another role |
| Revoke a role from another role |
| Show memberships for a role |
| Grant database-level privileges to a role |
| Revoke database-level privileges from a role |
| Show database-level grants for a role |
| Confirm and execute a destructive action token |
Safety
No raw SQL passthrough
No schema, table, view, index, trigger, or function management
SUPERUSER role creation and modification are not supported
pg_drop_databaseandpg_drop_rolerequirepg_confirm_taskpg_drop_roledoes not supportREASSIGN OWNEDorDROP OWNEDConfirmation tokens are random, single-use, and expire quickly
Configuration
Use environment variables, matching the rest of the easy-*-mcp family.
Variable | Required | Default | Description |
| Conditional | - | PostgreSQL connection string. Takes precedence when provided |
| Conditional | - | PostgreSQL host when no connection string is provided |
| No |
| PostgreSQL port |
| Conditional | - | PostgreSQL admin role name when no connection string is provided |
| No | - | PostgreSQL password |
| Conditional | - | Default database used for the admin connection |
| No |
| Maximum number of active pool connections |
| No |
| Connection establishment timeout in milliseconds |
| No |
| Idle connection timeout in milliseconds |
| No |
| Whether TCP keep-alive is enabled |
| No |
| Initial TCP keep-alive delay in milliseconds |
| No |
| Use |
| No |
| Confirmation token lifetime in seconds |
Example
PG_HOST=localhost
PG_PORT=5432
PG_USER=postgres
PG_PASSWORD=your_password
PG_DATABASE=postgres
PG_SSL=false
PG_ADMIN_TOKEN_TTL_SECONDS=120Claude Desktop Example
{
"mcpServers": {
"easy-pg-admin-mcp": {
"command": "npx",
"args": ["-y", "easy-pg-admin-mcp"],
"env": {
"PG_HOST": "localhost",
"PG_PORT": "5432",
"PG_USER": "postgres",
"PG_PASSWORD": "your_password",
"PG_DATABASE": "postgres",
"PG_SSL": "false",
"PG_ADMIN_TOKEN_TTL_SECONDS": "120"
}
}
}
}Codex config.toml Example
[mcp_servers.easy-pg-admin-mcp]
args = ["-y", "easy-pg-admin-mcp"]
command = "npx"
enabled = true
[mcp_servers.easy-pg-admin-mcp.env]
PG_HOST = "localhost"
PG_PORT = "5432"
PG_USER = "postgres"
PG_PASSWORD = "your_password"
PG_DATABASE = "postgres"
PG_SSL = "false"
PG_ADMIN_TOKEN_TTL_SECONDS = "120"OpenCode opencode.jsonc Example
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"easy-pg-admin-mcp": {
"type": "local",
"command": ["npx", "-y", "easy-pg-admin-mcp"],
"enabled": true,
"environment": {
"PG_HOST": "localhost",
"PG_PORT": "5432",
"PG_USER": "postgres",
"PG_PASSWORD": "your_password",
"PG_DATABASE": "postgres",
"PG_SSL": "false",
"PG_ADMIN_TOKEN_TTL_SECONDS": "120",
},
},
},
}Available Tools
17 toolspg_alter_database_ownerC
Change the owner of a PostgreSQL database.
Inputs: owner (required), database (required).
pg_alter_role_attributesC
Change PostgreSQL role attributes. SUPERUSER is intentionally not supported.
Inputs: role (required), login, inherit, createdb, +5 more.
pg_alter_role_passwordC
Change a PostgreSQL role password.
Inputs: role (required), password (required).
pg_confirm_taskC
Confirm and execute a previously issued destructive action token.
Inputs: token (required).
pg_create_databaseD
Create a PostgreSQL database.
Inputs: database (required), owner, locale, encoding, +1 more.
pg_create_roleC
Create a PostgreSQL role. SUPERUSER is intentionally not supported.
Inputs: role (required), login, inherit, createdb, +6 more.
pg_describe_databaseC
Inspect a PostgreSQL database definition.
Inputs: database (required).
pg_drop_databaseC
Request database deletion and return a short-lived confirmation token.
Inputs: database (required), force.
pg_drop_roleC
Request role deletion and return a short-lived confirmation token.
Inputs: role (required).
pg_grant_privilegesC
Grant database-level PostgreSQL privileges to a role.
Inputs: role (required), database (required), privileges (required), withGrantOption.
pg_grant_roleC
Grant a PostgreSQL role to another role.
Inputs: role (required), member (required), adminOption.
pg_list_databasesA
List databases in the current PostgreSQL instance.
Inputs: no named parameters.
pg_list_rolesC
List PostgreSQL roles.
Inputs: includeSystem.
pg_revoke_privilegesC
Revoke database-level PostgreSQL privileges from a role.
Inputs: role (required), database (required), privileges (required), grantOptionFor.
pg_revoke_roleC
Revoke a PostgreSQL role from another role.
Inputs: role (required), member (required), adminOption.
pg_show_grantsB
Show database-level PostgreSQL grants for a role.
Inputs: role (required), database.
pg_show_role_membershipsC
Show memberships for a PostgreSQL role.
Inputs: role (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Each tool targets a distinct action on either databases or roles, with clear descriptions that prevent overlap. For example, pg_grant_privileges and pg_grant_role are explicitly different operations.
All tools follow the consistent pattern 'pg_verb_noun' (e.g., pg_create_database, pg_drop_role). The naming is uniform and predictable.
With 17 tools covering database and role CRUD, grants, and listings, the count matches the domain well. Each tool serves a specific purpose without unnecessary overlap.
The set covers essential PostgreSQL admin tasks: create, drop (with confirmation), list, alter, and grant/revoke for both databases and roles. Minor gaps like renaming or altering database properties other than owner are absent but acceptable for an 'easy' admin tool.
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Hosted MCP server for PostgreSQL diagnostics: slow queries, missing indexes, connection pressure.
Managed Postgres MCP: projects, SQL, docs search, and storage buckets via OAuth.
MCP server for interacting with the Supabase platform
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes PostgreSQL database operations via psycopg2, including connection management, query execution, and transaction control.MIT
- AlicenseAqualityCmaintenanceFull-featured MCP server that exposes 36 tools for interacting with PostgreSQL databases, covering schema introspection, query execution, data exploration, performance monitoring, security auditing, and maintenance.365 npmMIT
- AlicenseAqualityCmaintenanceLocal MCP server for safe querying and inspecting PostgreSQL databases, with write and maintenance operations disabled by default.81MIT
- AlicenseNot gradedqualityDmaintenanceA Python MCP 2.0 server for self-hosted PostgreSQL instances, providing schema/relation discovery, SQL query and controlled transactional execution tools with security features like read-only transactions, role hardening guidance, and optional human approval for write commands.MIT