Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.
Neon’s MCP server connects an authorized assistant to documented project, branch and database workflows.
Specify the project and branch before investigating a schema change. For a migration proposal, read the current schema, show the intended SQL and choose a development branch for the first execution. Keep acceptance checks with the proposal.
Follow Neon’s documented local or hosted connection and its authentication flow. Verify the project and branch returned by the first read. OAuth identity, database credentials and branch selection describe different parts of the connection.
Inspect the schema and query result after a change, then run the application path that uses it. A migration that executes without an SQL error can still break application assumptions. Confirm the branch before promoting any tested change.
Schema changes stage on a temp branch and apply only after you confirm — a review gate built into the workflow.
Spin up a branch with production-shaped data for each experiment, then delete it.
Let the assistant create the project, schema and connection string for a new app in one go.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| list_projects / create_project | Enumerate and provision Neon projects |
| run_sql | Execute SQL against a chosen project and branch |
| create_branch / delete_branch | Copy-on-write database branches in seconds |
| prepare_database_migration | Stage a schema change on a temporary branch |
| complete_database_migration | Apply a staged migration after confirmation |
| get_connection_string | Fetch connection details for any branch |
| describe_table_schema | Inspect table structure on a branch |
claude mcp add --transport http neon https://mcp.neon.tech/mcpOpens a browser to authorise your Neon account.
A Neon account (free tier works). OAuth in the browser for remote mode; an API key only for automation.
| Variable | Description | Required |
|---|---|---|
| NEON_API_KEY | API key for non-OAuth local mode (automation/CI)e.g. napi_... | Optional |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
A MySQL connector for Smithery that allows you to connect to your MySQL database directly from Smithery, built with Python.
Six read-only tools — web_research, web_context, web_search, web_read, web_verify, web_extract — plus MCP resources, prompts, and proper outputSchema / readOnlyHint metadata. Behind each tool: local…
Connect to your Elasticsearch cluster from any MCP-compatible client (such as Claude Desktop) using the Model Context Protocol (MCP). This server
Trivia MCP — wraps Open Trivia Database (free, no auth)