Databases MCP Servers

10 databases MCP servers are cataloged, 1 with verified current-spec support.

MCP servers that query, inspect, or manage databases and data stores: SQL and NoSQL engines, ORMs, migrations, schema exploration, and hosted database platforms.

• Airtable - Earlier Revision

  Distributed as npm:airtable-mcp-server. Resolved from the published package: airtable-mcp-server 1.14.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• AWS Labs postgres MCP Server - Spec Support Unverified

  AWS Labs' own MCP server for Amazon Aurora and RDS Postgres, distributed from the awslabs/mcp monorepo at src/postgres-mcp-server. Authority is first-party on two AWS-controlled surfaces: GitHub reports the awslabs organization as verified ("is_verified": true, name "Amazon Web Services - Labs"), and the monorepo's own README describes the collection as "Open source MCP servers for AWS... A suite of specialized MCP servers that help you get the most out of AWS, wherever you use MCP." The server runs over stdio only, per the monorepo root README's transport statement ("The MCP servers in this repository are designed to support stdio only") and confirmed in source, where server.py calls mcp.run() with no transport argument. The auth enum has no clean match for this server's credential model: it authenticates to AWS through the AWS_PROFILE/AWS_REGION credential chain, requires an RDS Data API resource ARN carrying rds-data:ExecuteStatement permission, and separately authenticates to Postgres via IAM or username/password credentials held in AWS Secrets Manager and referenced by --secretManagerARN; api_key is recorded here for lack of a better enum value rather than as a literal description. The server is read-only by default; --allow_write_query disables that enforcement, and the README's own security section calls the mechanism "a best-effort, defense-in-depth mechanism, not a security boundary." Neither the README nor the docs site enumerates a tool list; tools_count 7 and the key_tools below were recovered by reading the source directly at https://raw.githubusercontent.com/awslabs/mcp/main/src/postgres-mcp-server/awslabs/postgres_mcp_server/server.py.

• DBHub - Current Spec Verified

  Bytebase's universal database MCP server for PostgreSQL, MySQL, SQL Server, MariaDB, and SQLite, run locally via npx with a connection DSN. Supports a read-only mode and a bearer-token-authenticated HTTP transport. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @bytebase/dbhub 1.2.0 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.

• dbx - Spec Support Unverified

  Distributed as npm:@dbx-app/mcp-server. Hand check 2026-08-25: no MCP revision statement in the main or mcp-server package READMEs; the Rust server depends on rmcp 2.2.0 (Cargo.toml), not sufficient evidence on its own. Authority evidence: t8y2 is the sole npm maintainer (tongty.it@gmail.com) and owns the repository; dbx is the account's own product.

• Firebase MCP Server - Earlier Revision

  Firebase's MCP server ships inside the Firebase CLI (firebase-tools) and runs locally via npx firebase-tools mcp, exposing tools across Firestore, Auth, Storage, Crashlytics, Functions, and other Firebase products using the developer's existing CLI credentials. No vendor documentation surface names a supported MCP revision. Resolved from the published package: firebase-tools 15.28.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• MongoDB MCP Server - Earlier Revision

  MongoDB's first-party MCP server for MongoDB databases and Atlas clusters, run locally via npx mongodb-mcp-server or Docker. Version 2.0.0 (2026-08-04) removed session state and requires explicit connection ids. No vendor documentation surface names a supported MCP revision. Resolved from the published package: mongodb-mcp-server 2.1.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• MSSQL MCP Reader - Spec Support Unverified

  Distributed as npm:@connorbritain/mssql-mcp-reader. Community: the publisher is the personal GitHub account ConnorBritain and the server fronts Microsoft SQL Server, which the publisher does not operate. The read-only tier of the publisher's two-package split. Registry record (v0.3.1, updated 2026-02-18) trails npm (0.6.1, 2026-08-04). No MCP revision statement found (checked 2026-08-27).

• MSSQL MCP Server (ConnorBritain) - Spec Support Unverified

  Distributed as npm:@connorbritain/mssql-mcp-server. Community: the publisher is the personal GitHub account ConnorBritain and the server fronts Microsoft SQL Server, which the publisher does not operate. The registry record (v0.4.5, updated 2026-02-18) trails npm (0.7.0, 2026-08-04) by three minor versions. No MCP revision statement found in the README (checked 2026-08-27).

• Supabase MCP Server - Earlier Revision

  Supabase's first-party MCP server, hosted at mcp.supabase.com/mcp with OAuth dynamic client registration; feature-group, project-scoping, and read-only flags are documented. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no vendor documentation surface names a supported MCP revision. Resolved from the published package: @supabase/mcp-server-supabase 0.10.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• YawLabs Postgres MCP - Spec Support Unverified

  Distributed as npm:@yawlabs/postgres-mcp. Community: the YawLabs organization does not operate PostgreSQL, which the server fronts. Read-only by default with writes behind an env var, per the README. No MCP revision statement found (checked 2026-08-27).