An AWS Labs Model Context Protocol (MCP) server for postgres
Project description
AWS Labs postgres MCP Server
An AWS Labs Model Context Protocol (MCP) server for Aurora Postgres
Features
Natural language to Postgres SQL query
- Converting human-readable questions and commands into structured Postgres-compatible SQL queries and executing them against the configured Aurora Postgres database.
Prerequisites
- Install
uvfrom Astral or the GitHub README - Install Python using
uv python install 3.10 - This MCP server can only be run locally on the same host as your LLM client.
- Docker runtime
- Set up AWS credentials with access to AWS services
- You need an AWS account with appropriate permissions
- Configure AWS credentials with
aws configureor environment variables
Installation
| Kiro | Cursor | VS Code |
|---|---|---|
Configure the MCP server in your MCP client configuration (e.g., for Kiro, edit ~/.kiro/settings/mcp.json):
{
"mcpServers": {
"awslabs.postgres-mcp-server": {
"command": "uvx",
"args": [
"awslabs.postgres-mcp-server@latest",
"--allow_write_query"
],
"env": {
"AWS_PROFILE": "your-aws-profile",
"AWS_REGION": "us-east-1",
"FASTMCP_LOG_LEVEL": "ERROR"
},
"disabled": false,
"autoApprove": []
}
}
}
Windows Installation
For Windows users, the MCP server configuration format is slightly different:
{
"mcpServers": {
"awslabs.postgres-mcp-server": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "uv",
"args": [
"tool",
"run",
"--from",
"awslabs.postgres-mcp-server@latest",
"awslabs.postgres-mcp-server.exe"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"AWS_PROFILE": "your-aws-profile",
"AWS_REGION": "us-east-1"
}
}
}
}
Build and install docker image locally on the same host of your LLM client
- 'git clone https://github.com/awslabs/mcp.git'
- Go to sub-directory 'src/postgres-mcp-server/'
- Run 'docker build -t awslabs/postgres-mcp-server:latest .'
Add or update your LLM client's config with following:
Option 1: Using RDS Data API Connection (for Aurora Postgres)
{
"mcpServers": {
"awslabs.postgres-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "AWS_ACCESS_KEY_ID=[your data]",
"-e", "AWS_SECRET_ACCESS_KEY=[your data]",
"-e", "AWS_REGION=[your data]",
"awslabs/postgres-mcp-server:latest",
"--allow_write_query"
]
}
}
}
NOTE: the MCP config example include --allow_write_query illustrate how to enable write queries. If you want to disable write queries, remove --allow_write_query option.
Support for Database Cluster Creation
You can use the following LLM prompt to create a new Aurora PostgreSQL cluster:
Create an Aurora PostgreSQL cluster named 'mycluster' in us-west-2 region
Connection Methods
The MCP server supports connecting to multiple database endpoints using different connection methods via LLM prompts.
Database Types
- APG: Amazon Aurora PostgreSQL
- RPG: Amazon RDS for PostgreSQL
Example Prompts
Connect using RDS Data API:
Connect to database named postgres in Aurora PostgreSQL cluster 'my-cluster' with database_type as APG, using rdsapi as connection method in us-west-2 region
Connect using pgwire (Aurora PostgreSQL):
Connect to database named postgres with database endpoint as my-apg17-instance-1.ctgfg6yyo9df.us-west-2.rds.amazonaws.com with database_type as APG, using pgwire as connection method in us-west-2 region
Connect using pgwire (RDS PostgreSQL):
Connect to database named postgres with database endpoint as test-apg17-instance-1.ctgfg6yyo9df.us-west-2.rds.amazonaws.com with database_type as RPG, using pgwire as connection method in us-west-2 region
Supported Connection Methods
| Method | Description | Supported Database Types |
|---|---|---|
pgwire |
Connect to PostgreSQL instance directly using the PostgreSQL wire protocol. Requires proper VPC security group configuration for direct database connectivity. | APG, RPG |
pgwire_iam |
Same as pgwire, but uses IAM authentication. Requires IAM authentication to be enabled on the Aurora PostgreSQL cluster. |
APG only |
rdsapi |
Connect to Aurora PostgreSQL using the RDS Data API. Requires the RDS Data API to be enabled on the cluster. | APG only |
Prerequisites by Connection Method
pgwire / pgwire_iam
- VPC security group must allow inbound connections from your MCP server to the database
- For
pgwire_iam: IAM authentication must be enabled on the Aurora PostgreSQL cluster
rdsapi
- RDS Data API must be enabled on the Aurora PostgreSQL cluster
- Appropriate IAM permissions for Data API access
AWS Authentication
The MCP server uses the AWS profile specified in the AWS_PROFILE environment variable. If not provided, it defaults to the "default" profile in your AWS configuration file.
"env": {
"AWS_PROFILE": "your-aws-profile"
}
Make sure the AWS profile has permissions to access the RDS data API, and the secret from AWS Secrets Manager. The MCP server creates a boto3 session using the specified profile to authenticate with AWS services. Your AWS IAM credentials remain on your local machine and are strictly used for accessing AWS services.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file awslabs_postgres_mcp_server-1.0.17.tar.gz.
File metadata
- Download URL: awslabs_postgres_mcp_server-1.0.17.tar.gz
- Upload date:
- Size: 180.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
791682e9007cf07e5eb705ca20416c14cbbe174a98f521e935e53e0295962add
|
|
| MD5 |
a6acd995fda39b7c49a199615138ac99
|
|
| BLAKE2b-256 |
13873d2a098a20a35293e1ae355cf2aafb5066393cf484fbae9d2ca0c42e14d5
|
Provenance
The following attestation bundles were made for awslabs_postgres_mcp_server-1.0.17.tar.gz:
Publisher:
release.yml on awslabs/mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
awslabs_postgres_mcp_server-1.0.17.tar.gz -
Subject digest:
791682e9007cf07e5eb705ca20416c14cbbe174a98f521e935e53e0295962add - Sigstore transparency entry: 917053144
- Sigstore integration time:
-
Permalink:
awslabs/mcp@cd57218bfca749cb85eab44832fa2f9dff9e654d -
Branch / Tag:
refs/tags/2026.02.20260204163019 - Owner: https://github.com/awslabs
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@cd57218bfca749cb85eab44832fa2f9dff9e654d -
Trigger Event:
push
-
Statement type:
File details
Details for the file awslabs_postgres_mcp_server-1.0.17-py3-none-any.whl.
File metadata
- Download URL: awslabs_postgres_mcp_server-1.0.17-py3-none-any.whl
- Upload date:
- Size: 33.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
4691f093f85e6f09ab9973f59c57aa3ffcf85e6e09c91b04eaaa1aa4dd7838de
|
|
| MD5 |
dcf0cb6084fa712d414b0722d9552df4
|
|
| BLAKE2b-256 |
5e91158083ee5404899268578e65c6ac4e9a8045fa0fb55fd6e5f9a73d5ecbe7
|
Provenance
The following attestation bundles were made for awslabs_postgres_mcp_server-1.0.17-py3-none-any.whl:
Publisher:
release.yml on awslabs/mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
awslabs_postgres_mcp_server-1.0.17-py3-none-any.whl -
Subject digest:
4691f093f85e6f09ab9973f59c57aa3ffcf85e6e09c91b04eaaa1aa4dd7838de - Sigstore transparency entry: 917053180
- Sigstore integration time:
-
Permalink:
awslabs/mcp@cd57218bfca749cb85eab44832fa2f9dff9e654d -
Branch / Tag:
refs/tags/2026.02.20260204163019 - Owner: https://github.com/awslabs
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@cd57218bfca749cb85eab44832fa2f9dff9e654d -
Trigger Event:
push
-
Statement type: