Skip to main content

Neon

Spin up Neon Postgres branches, run SQL, and inspect table schemas before you migrate.

Tools

29 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

29 tools found.

  • List projects

    Tool name: list_projects

    Lists the first 10 Neon projects in your account.

  • List organizations

    Tool name: list_organizations

    Lists all organizations that the current user has access to.

  • List shared projects

    Tool name: list_shared_projects

    Lists projects that have been shared with the current user.

  • Create project

    Tool name: create_project

    Create a new Neon project.

  • Delete project

    Tool name: delete_project

    Delete a Neon project

  • Describe project

    Tool name: describe_project

    Describes a Neon project

  • Run SQL

    Tool name: run_sql

    Execute a single SQL statement against a Neon database.

  • Run SQL transaction

    Tool name: run_sql_transaction

    Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.

  • Describe table schema

    Tool name: describe_table_schema

    Describe the schema of a table in a Neon database

  • Get database tables

    Tool name: get_database_tables

    Get all tables in a Neon database

  • Create branch

    Tool name: create_branch

    Create a branch in a Neon project

  • Prepare database migration

    Tool name: prepare_database_migration

    Performs database schema migrations by automatically generating and executing DDL statements.

  • Complete database migration

    Tool name: complete_database_migration

    Complete a database migration by applying changes to the main branch and cleaning up the temporary branch.

  • Describe branch

    Tool name: describe_branch

    Get a tree view of all objects in a branch, including databases, schemas, tables, views, and functions

  • Delete branch

    Tool name: delete_branch

    Delete a branch from a Neon project

  • Reset from parent

    Tool name: reset_from_parent

    Resets a branch to match its parent's current state, effectively discarding all changes made on the branch.

  • Get connection string

    Tool name: get_connection_string

    Get a PostgreSQL connection string for a Neon database with all parameters being optional

  • Provision Neon auth

    Tool name: provision_neon_auth

    Provisions Neon Auth for a Neon branch.

  • Provision Neon data API

    Tool name: provision_neon_data_api

    Provisions the Neon Data API for a Neon branch.

  • Explain SQL statement

    Tool name: explain_sql_statement

    Describe the PostgreSQL query execution plan for a query of SQL statement by running EXPLAIN (ANAYLZE...) in the database

  • Prepare query tuning

    Tool name: prepare_query_tuning

    Helps developers improve PostgreSQL query performance for slow queries or DML statements by analyzing execution plans and suggesting optimizations.

  • Complete query tuning

    Tool name: complete_query_tuning

    Complete a query tuning session by either applying the changes to the main branch or discarding them.

  • List slow queries

    Tool name: list_slow_queries

    List slow queries from your Neon database.

  • List branch computes

    Tool name: list_branch_computes

    Lists compute endpoints for a project or specific branch

  • Compare database schema

    Tool name: compare_database_schema

    Compare the schema of a database between two branches.

  • Search

    Tool name: search

    Searches across all user organizations, projects, and branches that match the query.

  • Fetch

    Tool name: fetch

    Fetches detailed information about a specific organization, project, or branch using the ID returned by the search tool.

  • List docs resources

    Tool name: list_docs_resources

    Lists all available Neon documentation pages by fetching the index from https://neon.com/docs/llms.txt.

  • Get doc resource

    Tool name: get_doc_resource

    Fetches a specific Neon documentation page as markdown content.

Compatibility

Connect Neon to the clients your teams already use

27 AI clients can connect to Neon through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Neon through Runlayer?

One approved path

Approve Neon once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions