--- title: "Aurora DSQL MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/awslabs-aurora-dsql/ description: "AWS Labs MCP server that turns questions into Postgres-compatible SQL for Aurora DSQL, read-only unless --allow-writes is passed, and only on the same host as the client." --- # Aurora DSQL MCP: review, setup & limitations · Undominated.ai > AWS Labs MCP server that turns questions into Postgres-compatible SQL for Aurora DSQL, read-only unless --allow-writes is passed, and only on the same host as the client. [← Explore all mcp servers](/mcp-servers/) DATABASE DEVELOPMENT / AWS Labs # Aurora DSQL MCP AWS Labs MCP server that turns questions into Postgres-compatible SQL for Aurora DSQL, read-only unless --allow-writes is passed, and only on the same host as the client. [See setup guidance ↓](#setup)[Original source ↗](https://github.com/awslabs/mcp/tree/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server) SOURCE REVIEW Reviewed 2026-10-14 Evidence 2 linked sources Publisher AWS Labs Licence [Apache-2.0 ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/LICENSE) Revision 8840003820a7 [Read what was—and wasn’t—checked ↓](#review) “Exposes readonly_query, transact, get_schema, documentation search and read, recommendations, and a SQL linter for a configured DSQL cluster.” [AWS Labs · upstream description ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/README.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - The catalogue's AWS database servers cover DynamoDB, DocumentDB, and ElastiCache, not Aurora DSQL. - The README lists the SQL and documentation tools and says writes need an explicit flag. ### A good fit for - Running a read-only SQL question against a DSQL cluster - Checking SQL with dsql_lint before it is executed ### Weigh up before choosing - This review did not execute it. - This review did not start the server or run the readonly enforcement tests. - The JSON examples are not a single shell command, so install.command is null. - The plugin lines later in the README install a DSQL agent skill from another repository, not this server. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - src/aurora-dsql-mcp-server/README.md - src/aurora-dsql-mcp-server/LICENSE ### Our findings - Database tools are readonly_query, transact, and get_schema, and they require --cluster_endpoint, --database_user, and --region. - Writes are off until --allow-writes; the README says the server can only run locally on the same host as the LLM client. - The Windows configuration block sets type to stdio. The directory LICENSE at this commit is Apache-2.0. ### Not established by this review - The server was not started. - No SQL tool was called. - uv run pytest was not executed. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. [Upstream setup instructions ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/README.md) - Install uv and Python 3.10, then put uvx awslabs.aurora-dsql-mcp-server@latest in the client JSON with the cluster flags. - The Windows block uses type stdio. - No single shell install line is recorded. ### Before you start - Python 3.10 and uv - An Aurora DSQL cluster endpoint, database user, and region - AWS credentials on the same host ### Compatibility Kiro · Cursor · VS Code · Amazon Q Developer CLI ### Implementation python ### Transports stdio ### Local stdio, read-only unless flagged - Run read-only SQL - Run writes only with --allow-writes - Search and read Aurora DSQL documentation ### Cost model Apache-2.0; AWS credentials and a DSQL cluster are required 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Aurora DSQL README ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/README.md Supports: tools, read-only default, and stdio config - [Directory LICENSE ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/LICENSE) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aurora-dsql-mcp-server/LICENSE Supports: Apache-2.0 KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### AWS Labs Postgres MCP ↗ Pins the AWS Labs Postgres server whose read-only guard parses SQL with pglast and still tells operators to use a least-privilege role.](/mcp-servers/awslabs-postgres/)[### Aurora MySQL MCP ↗ AWS Labs MCP server that turns natural language into SQL for Aurora MySQL on the same host as the client, with a keyword guard the README says is not a security boundary.](/mcp-servers/awslabs-mysql/)[### YugabyteDB MCP Server ↗ Python MCP server from the Yugabyte organisation that lists schema objects, runs a SELECT inside a read-only transaction, and keeps the write tool off unless an operator flag turns it on.](/mcp-servers/yugabytedb/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Inspect resource evidence](/tools/) - [Choose a host](/agents/) - [Inspect reusable workflows](/skills/) - [Use Undominated data](/api/)