Secure Access Endpoint for AWS PostgreSQL (Read-Only)

This Model Context Protocol (MCP) server establishes a safe conduit for executing SELECT operations against a specified AWS RDS PostgreSQL database. Access is strictly restricted to data retrieval via the built-in query toolset. Operational parameters are driven entirely by environmental variables.

Initialization Sequence

1. Acquisition: bash git clone https://github.com/T1nker-1220/aws-postgress-mcp-server.git cd aws-postgress-mcp-server

2. Dependency Resolution & Compilation: bash pnpm install pnpm run build

Configuration for Client Integration (e.g., Cline/Windsurf)

Integrate the following configuration block into your MCP client's configuration file (e.g., cline_mcp_settings.json located in your user profile's application data path):

{ "mcpServers": { // ... existing server definitions ...

"secured-aws-rds-read-only-interface": {
  "command": "node",
  "args": [
    // Path to the compiled main executable file
    "C:\Users\NATH\Documents\Cline\MCP\aws-postgress-mcp-server\build\index.js" 
  ],
  // Connection details must be supplied via environment variables
  "env": {
    "DB_HOST": "YOUR_HOST.rds.amazonaws.com",
    "DB_PORT": "5432",
    "DB_NAME": "YOUR_DB_NAME",
    "DB_USER": "YOUR_DB_USER",
    "DB_PASSWORD": "YOUR_PASSWORD"
  },
  "transportType": "stdio",
  "disabled": false,
  "autoApprove": [] 
}
// ... other server definitions ...

} }

Critical Action: Substitute the placeholder values within the env section with your actual database authentication credentials.

Operational Procedure

Once the configuration is active, the client initiates the server. Data queries are dispatched using the query tool command structure:

xml secured-aws-rds-read-only-interface query { "sql": "SELECT id, record_timestamp FROM operational_logs WHERE status = 'processed' LIMIT 10;" }

Operational Constraints

• The server strictly enforces read-only operational modes (permitting only statements like SELECT, SHOW, EXPLAIN, etc.). Write operations (INSERT, UPDATE, DELETE) are explicitly prohibited.
• If deploying this utility via direct execution (e.g., npx @t1nker-1220/aws-postgres-mcp-server ...), the package must first be published to the NPM registry. Credential management remains consistent via the env object.