Neon MCP server

What does Neon need from you?

Bearer token — Optional Bearer token with a Neon API key.

• AuthorizationoptionalsecretHTTP header

  Optional Bearer token with a Neon API key.

• x-read-onlyoptionalHTTP header

  Optional header to enable read-only mode for tool filtering.

What tools does Neon expose? (65)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

• projects
• branches
• endpoints
• snapshots
• schema
• querying
• neon_auth
• data_api
• observability
• docs
• functions
• storage
• realtime
• list_projectsLists Neon projects. `limit` caps how many items come back.
• describe_projectFetches a Neon project by id (`{ "project_id": "…" }`).
• create_projectCreates a Neon project and waits for the default compute. Does not return a connection string. Arguments are `{ "name": "…", "org_id": "…", "region_id": "…" }`. Call `get_connection_string` after it succeeds.
• delete_projectDeletes an existing Neon project. Arguments are `{ "project_id": "…" }`.
• list_organizationsLists all organizations that the current user has access to. Optionally filter by organization name or ID using the search parameter.
• list_branchesLists branches in a project. Use it to resolve a branch name to a `br-…` id.
• list_credentials, `create_credential`, `revoke_credential`, `rotate_credential`: Branch-scoped credentials for Object Storage and the AI Gateway. `reveal` is not a tool; rotation replaces secrets in place and is not idempotent.
• create_branchCreates a branch with a read-write compute and waits until it is ready. Does not return a connection string. Arguments are `{ "project_id": "…", "name": "feature-x" }`. Pass `no_compute: true` to skip the endpoint. Call `get_connection_stri
• reset_from_parentResets a branch to its parent's current HEAD (`{ "project_id": "…", "branch_id": "br-…" }`). Discards writes since the branch diverged. `preserve_under_name` is required when the branch has children; those children move to the new branch. P
• delete_branchDeletes a branch (`{ "project_id": "…", "branch_id": "br-…" }`).
• describe_branchRetrieves a tree of databases, schemas, tables, views, and functions on a branch.
• restore_snapshotRestores a snapshot. Pass `target_branch_id` to restore onto an existing branch; omit it to create a new one.
• list_postgres_endpoints, `list_branch_computes`, `get_postgres_endpoint`, `create_postgres_endpoint`, `update_postgres_endpoint`, `delete_postgres_endpoint`, `start_postgres_endpoint`, `suspend_postgres_endpoint`, `restart_postgres_endpoint`
• list_snapshots, `get_snapshot_schedule`, `set_snapshot_schedule`, `create_snapshot`, `update_snapshot`, `delete_snapshot`, `restore_snapshot`
• get_database_tables, `describe_table_schema`
• compare_database_schemaSQL schema diff of one database against another branch. `database_name` is required. Omitting `base_branch_id` compares against the parent. Optional `lsn`, `timestamp`, `base_lsn`, `base_timestamp` are point-in-time only.
• get_connection_stringReturns your database connection string.
• run_sqlExecutes a single SQL query against a specified Neon database. Supports both read and write operations. Optional `role_name` logs in as that Postgres role instead of the database owner, and `compute_id` picks the compute; credentials stay o
• run_sql_transactionExecutes a series of SQL queries within a single transaction against a Neon database. Takes the same optional `role_name` and `compute_id` as `run_sql`.
• describe_table_schemaRetrieves the schema definition of a specific table, detailing columns, data types, and constraints.
• prepare_database_migrationInitiates a database migration process. Critically, it creates a temporary branch to apply and test the migration safely before affecting the main branch.
• complete_database_migrationFinalizes and applies a prepared database migration to the main branch. This action merges changes from the temporary migration branch and cleans up temporary resources.
• inspect_databaseRuns one of 15 predefined read-only Postgres diagnostics against a branch — relation and index sizes, index and sequential-scan usage, active queries and locks, the heaviest and most frequent queries, cache hit rate and working-set size, au
• list_slow_queriesIdentifies performance bottlenecks by finding the slowest queries in a database. Requires the pg_stat_statements extension.
• explain_sql_statementProvides detailed execution plans for SQL queries to help identify performance bottlenecks.
• prepare_query_tuningAnalyzes query performance and suggests optimizations, like index creation. Creates a temporary branch for safely testing these optimizations.
• complete_query_tuningFinalizes query tuning by either applying optimizations to the main branch or discarding them. Cleans up the temporary tuning branch.
• provision_neon_auth, `get_auth`, `disable_auth`, `update_auth_config`
• get_neon_auth_confighost tool; secrets redacted. Use generated Auth write tools to change settings.
• list_auth_oauth_providers, `add_auth_oauth_provider`, `update_auth_oauth_provider`, `delete_auth_oauth_provider`
• get_auth_oauth_server, `update_auth_oauth_server`: Configure Neon Auth as an OAuth 2.1 authorization server (including for MCP servers). Separate from the social login providers above.
• list_auth_oauth_clients, `get_auth_oauth_client`, `create_auth_oauth_client`, `update_auth_oauth_client`, `delete_auth_oauth_client`, `rotate_auth_oauth_client_secret`: Manage the OAuth clients of that server. `create_auth_oauth_client` and `rotate_auth_oauth_cli
• list_auth_trusted_domains, `add_auth_trusted_domain`, `delete_auth_trusted_domain`
• create_auth_user, `delete_auth_user`, `update_auth_user_role`
• provision_neon_data_api, `get_data_api`, `update_data_api`, `delete_data_api`: Manage the Data API for a branch database.
• searchSearches across organizations, projects, and branches matching a query. Returns IDs, titles, and direct links to the Neon Console.
• fetchFetches detailed information about a specific organization, project, or branch using an ID (typically from the search tool).
• send_feedbackSends anonymous feedback to the Neon team. Only the feedback text is sent, with no account, project, or connection details. Messages are limited to 10,000 characters.
• query_logsQueries OpenTelemetry logs for a branch. POST in the Management API; treated as read-only by this server.
• list_log_fieldsLists the log fields you can enumerate values for on a branch.
• list_log_field_valuesLists the distinct values of a log field within a branch and time window.
• search_docsSearches neon.com (docs, API reference, PostgreSQL tutorial, guides, FAQs, changelog, and blog) with the same search as the neon.com search box. Takes `query`, optional `categories` (`docs`, `api`, `postgresql`, `guides`, `faqs`, `blog`, `c
• get_docFetches one neon.com page as markdown. Takes `slug` from a `search_docs` hit (for example `docs/guides/prisma` or `postgresql/tutorial/inner-join`).
• list_functions, `get_function`, `update_function`, `delete_function`, `deploy_function`
• list_functions_custom_domains, `register_functions_custom_domain`, `delete_functions_custom_domain`
• list_triggers, `get_trigger`, `create_trigger`, `update_trigger`, `delete_trigger`: Scheduled function triggers (`type: "schedule"`, five-field UTC cron).
• list_storage_buckets, `create_storage_bucket`, `delete_storage_bucket`
• list_storage_objects, `delete_storage_object`, `delete_storage_objects_by_prefix`
• presign_storage_object, `get_storage`
• get_realtime, `enable_realtime`, `disable_realtime`: Branch Realtime state, enable (optional `allowed_origins`), and disable. Enable and disable wait until the change is applied.
• get_realtime_secretThe shared secret the application backend issues Realtime tokens with. Not available in read-only mode.
• rotate_realtime_secretReplaces the shared secret and waits until the change is applied. Not idempotent. Call `get_realtime_secret` afterwards for the new value.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• Last commit today — Actively maintained.
• 658 GitHub stars — Community adoption signal.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%100%

  Last commit 0 days ago.

• Adoption20%85%

  658 stars.

• Transparency20%100%

  4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

• Provenance15%75%

  Links to its own repository; package linkage unverified.

• Packaging15%100%

  Remote endpoint with documented authentication.

Excerpt — the full document is on GitHub.

Maintain Neon? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![Neon on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-neon-mcp)](https://mcp-skills-hub.vercel.app/mcps/com-neon-mcp)