Claude Neon connectorWhat Claude can do in your Neon account.
The Claude Neon connector exposes 35 tools. 20 read projects, schemas, logs and docs, 13 create, run or delete something, and 2 are described by no official source. Here is what Claude can do in your Postgres, which actions Neon flags for your approval, and how to keep it read-only.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your Neon projects
With the connector, you describe what you want and Claude does the round trip itself: it inspects the schema, runs the query, tries a migration on a throwaway branch and reads the logs. Neon is blunt about the stakes, though: the server grants broad database management rights, so it tells you to review what Claude asks to do.
Understand a database before touching it. You ask what a project contains. Claude calls get_database_tables, then describe_table_schema on the tables that matter, and compare_database_schema to see how a branch differs from its parent.
Ship a schema change safely. prepare_database_migration applies the change on a temporary branch, Claude tests it there with run_sql, and complete_database_migration applies or discards it once you decide. Neon's own tool descriptions tell Claude to ask you before that last step.
Chase a slow query. list_slow_queries ranks statements by execution time, inspect_database runs Neon's diagnostic checks, and prepare_query_tuning analyzes the query on a temporary branch, where suggested changes are tried before anything reaches the real one.
Then the limits. Neon recommends the server for development and testing, not production, and says never to point it at production databases. You can pick read-only access at authorization, which keeps SELECT queries and schema inspection but turns off branching, migrations and auth changes. Two tools on the sheet have no description anywhere. And nothing runs by itself: a failed deploy does not wake Claude up. Scheduled jobs belong to an automation tool, which does a different job; the Integrations hub covers that side.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, here Neon, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs by itself, and the directory sheet lists all 35 by name.
- Authorization
- Neon's sign-in screen, where you grant the access Claude will use and can choose read-only or full access. Granted once per person.
- Approval
- The confirmation Claude waits for before doing something that changes your databases, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Neon.
Connect Neon to Claude in three steps
- 01
Find Neon in Claude
Open Claude's settings, then Customize and Connectors, and look up Neon in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to Neon in the window Neon opens. If the link breaks later, Disconnect and connect again; the access can also be withdrawn from the Neon side.
- 03
Read the authorization screen
Read what Neon asks before you accept. That screen belongs to Neon, not to Claude, and it decides what the access covers. It is also where Neon lets you pick the scope, as the tip below explains.
The 35 tools, split by what they do
Neon gives Claude 35 tools: 20 that read your account, 13 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Names stay exactly as Claude shows them.
- 20 read
- 13 write
- 2 not documented
What Claude reads (20)
20 toolsTwenty tools that inspect projects, schemas, queries, logs and docs without altering them.
compare_database_schema
Puts one database's schema on a branch side by side with another branch, by default its parent, and shows the differences. It can also compare against a point in time.
describe_branch
Gives a tree view of everything inside a branch: databases, schemas, tables, views and functions. It is the broad map, not the column detail.
describe_project
Returns a project's record: its settings, compute and usage figures. Branches are listed by another tool.
describe_table_schema
Shows the columns, data types and constraints of one specific table, the detail you need before querying it.
get_database_tables instead.explain_sql_statement
Produces PostgreSQL's execution plan for a statement so Claude can tell you why it is slow. With the analyze option, PostgreSQL actually executes the statement, side effects included.
fetch
Retrieves the details of a specific organization, project or branch, using the identifier that the search tool returned.
search, not a name.get_connection_string
Hands back a PostgreSQL connection string for a Neon database, resolving branch, compute and database if you leave them out.
get_database_tables
Lists every table in a Neon database, the quick overview when you do not yet need column-level detail.
describe_table_schema.get_doc_resource
Pulls one page of Neon's documentation into the conversation as markdown, picked from the list of available pages.
list_docs_resources; Neon gives its Prisma guide as an example.get_neon_auth_config
Reads the Neon Auth configuration of a branch with OAuth and SMTP secrets redacted, so Claude can review it without exposing credentials. Neon Auth has to be provisioned first.
inspect_database
Runs one of Neon's read-only diagnostic checks: table and index sizes, unused indexes, sequential scans, locks, stalled queries running longer than 30 seconds, cache hit rate, bloat, replication. It works inside a read-only transaction.
list_branch_computes
Lists the compute endpoints attached to a given branch, so Claude can tell you what is running behind it.
list_docs_resources
Lists the documentation page identifiers Neon publishes, which Claude needs before opening a specific page instead of guessing its address. Neon's description is explicit on that point.
list_log_field_values
Lists the distinct values a low-cardinality log field takes on a branch, over a window of up to seven days. Neon marks it as private beta.
list_log_fields
Shows which low-cardinality log fields have been observed on a branch, the step before asking for their values. It belongs to Neon's logging beta.
list_organizations
Lists the organizations your Neon account belongs to, with an optional search by name or identifier, partial values included.
list_projects
Lists the Neon projects you own, returning every page at once unless you set a limit on how many come back.
list_slow_queries
Ranks queries recorded by Postgres statistics by execution time, slowest first, so Claude knows where to look.
query_logs
Returns logs for a branch, filtered by fields or by a LogQL expression, over a window that defaults to the last hour and stops at seven days. Neon lists it as private beta.
search
Looks across all your organizations, projects and branches by keyword and returns matches with their identifier, title and link. The query needs at least three characters.
What Claude changes (13)
13 toolsThirteen tools that create, run, apply or delete something. For seven of them, Neon's own description tells Claude to ask you first.
complete_database_migration
Asks you firstApplies or discards a migration prepared earlier and deletes the temporary branch either way.
complete_query_tuning
Approval: see the ruleCloses a tuning session: it keeps or drops the indexing or query changes tested during a tuning session, then deletes the temporary branch.
create_branch
Approval: see the ruleCreates a branch that copies its parent at its current state, with a read-write compute unless you skip it, and waits until it is ready.
create_project
Approval: see the ruleCreates a new Neon project and waits until its default compute is ready. It does not return a connection string on its own.
delete_branch
Asks you firstDeletes a branch and all the data it holds. For a whole project, another tool exists.
delete_project
Asks you firstDeletes a Neon project with every branch and all of its data.
prepare_database_migration
Asks you firstApplies a schema change on a temporary branch and returns an identifier for the migration, leaving the main branch untouched for now.
prepare_query_tuning
Approval: see the ruleAnalyzes a slow query on a temporary branch and returns a tuning identifier, so suggested indexes can be tried away from the real data.
provision_neon_auth
Approval: see the ruleEnables Neon Auth on a branch by connecting it to an authentication provider.
provision_neon_data_api
Approval: see the ruleCreates a Neon Data API instance on a branch.
reset_from_parent
Asks you firstResets a branch to its parent's current state and discards every change the branch has made since it split off, with an option to save the current state first.
run_sql
Asks you firstExecutes one SQL statement on a Neon database, on a temporary branch if a previous step created one.
run_sql_transaction
Asks you firstExecutes several SQL statements as one transaction.
Undocumented (2)
2 toolsThe directory lists these two names, but Neon's published tool list does not include them. No text says what they do.
configure_neon_auth
The directory sheet lists this name, but it is absent from the tool list Neon publishes and no Neon page describes it. Nothing sourced says what kind of tool it is, so the general approval rule below is the only thing that covers it.
list_shared_projects
Another name the directory shows without any explanation: Neon's own published list skips it, and its documentation is silent too. We cannot say whether it only reads, so this page does not describe it and refers you to the default approval rule.
What Claude checks with you first
By default, Claude stops and asks before an action it takes on an account for someone. Neon goes further in its own words: always review and authorize what the assistant requests before it runs.
Seven tools carry that instruction in Neon's description: finishing a migration, preparing one, deleting a branch or a project, resetting a branch, and running SQL or transactions that could be destructive. That is Neon's guidance to the model, not a separate Claude screen, and the default rule still applies on top. On Team and Enterprise, owners decide whether members may let some actions through without being asked again and can restrict a connector for the whole organization. Claude works with the rights of the person who connected and nothing beyond.
Which plans include it
None of the 819 sheets in the official directory states plan availability. For Neon, as for every other connector, that answer is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, the Neon sheet in the official directory is the place to check.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a deploy fails or a query slows down.
This connector is documented by its publisher only: no Claude help article covers it, and the details here come from Neon's documentation and the tool list Neon publishes. The directory's verification badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees their behaviour. Two tools on the sheet, configure_neon_auth and list_shared_projects, appear in no Neon source. Other connectors reviewed the same way are in the Claude connectors hub.
Need help connecting Neon to Claude?
A person reads every message.
