Arlet
Neon

Use Neon from your AI

Manage Neon Postgres projects, branches, databases and computes, run SQL and migrations, tune queries and inspect logs through Neon's official MCP server. Connect by signing in; read-only access can be chosen at authorization.

Enable Neon in ArletNeon official docs

Arlet makes Neon's official MCP server available from the AI client you already use. Signing in completes the connection, and you can choose read-only access at authorization.

The AI can manage projects and branches, run SQL and migrations, tune queries and read logs. Neon recommends MCP for development and testing, so for production projects choose read-only access or keep tool-call confirmation enabled in your AI client. The available tools are those provided by Neon's official server.

Choose your AI client

Pick the AI client you use to see how to connect it with Neon.

What you can do

Tools the AI can call through the Neon integration.

  • list_projects

    List projects.

  • describe_project

    Get a project's branches, databases and computes.

  • create_project

    Create a project.

  • list_branches

    List branches.

  • create_branch

    Create a branch.

  • get_database_tables

    List tables.

  • describe_table_schema

    Get a table's schema.

  • run_sql

    Run SQL.

  • run_sql_transaction

    Run several statements in one transaction.

  • explain_sql_statement

    Get a query plan.

  • prepare_database_migration

    Try a migration on a branch.

  • complete_database_migration

    Apply a tried migration to the main branch.

  • list_slow_queries

    List slow queries.

  • prepare_query_tuning

    Validate a query-tuning candidate.

  • get_connection_string

    Get a connection string.

  • query_logs

    Search logs.

The tool list follows what Neon's official MCP server provides and may change.

Example uses

  • Change the schema safely

    Try a migration on a branch, check the result and then apply it to main.

  • Fix slow queries

    Find slow queries, read their plans and validate improvements such as new indexes.

  • Aggregate data

    Inspect the schema, write the aggregation SQL and explain the result.

  • See the environment

    List projects, branches and running computes.

Prompts you can use as-is

  • Try a migration adding a status column to orders on a branch, and apply it if it looks fine
  • Show the five slowest recent queries and validate an improvement for each
  • Count weekly sign-ups in the users table
  • List the branches and running computes for each project