Integration · Automate and collaborate

Neon and Meteor AI agents

Connect Neon to an internal Met: check projects, branches and tables, find slow queries and review indexes and locks with Neon's official MCP.

Book a demo See every integration

How does Neon connect to Meteor?

With the Neon ready connector, your Met uses Neon's official MCP server on your Postgres databases, with the account the admin authorizes. When authorizing you choose read-only or full access, and you can pin a Postgres role so SQL only sees what that role can see. The Met lists projects and branches, describes tables, shows the slowest queries and checks sizes, indexes and locks. Running SQL, creating, resetting or deleting projects and branches, completing migrations and handing out the connection string start turned off until the admin turns them on. Neon recommends its MCP server for development and testing, not for production databases.

What it automates

What a Meteor Met does with Neon

Answer the team with a fact from the database

When someone on the team asks on WhatsApp for a fact, the Met finds the project, lists the tables, checks the columns of the right one and, if the admin turned on the SQL query, which starts turned off, runs a read query.

Find out why the database is slow

The Met lists the slowest queries, runs Neon's read-only checks on indexes, locks and sizes, and generates the execution plan of the heaviest query.

Test a change without touching the main branch

With full access, the Met applies the schema change on a temporary branch. Testing it with SQL and completing it, which applies or discards it and deletes the temporary branch, start turned off until the admin turns them on.

Compare two branches

The Met compares a database's schema on a development branch with its parent branch and tells you which tables or columns changed before the change is applied.

25 tools

Everything your Met can ask Neon for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_organizations`	Lists the organizations the account belongs to, with optional search by name or ID.
`list_projects`	Lists the Neon projects of the connected account.
`describe_project`	Returns the project record, with its settings, compute and usage.
`create_project`	Creates a Neon project and waits until its default compute is ready. Starts turned off.
`delete_project`	Deletes a Neon project and all its data. Starts turned off.
`describe_branch`	Shows a tree of a branch's objects, such as databases, schemas, tables, views and functions.
`create_branch`	Creates a branch with a read-write compute, a copy of the parent branch at its current state. Starts turned off.
`delete_branch`	Deletes a branch and all its data. Starts turned off.
`reset_from_parent`	Resets a branch to its parent's current state and discards everything the branch wrote since it diverged. Starts turned off.
`list_branch_computes`	Lists a branch's compute endpoints.
`get_connection_string`	Returns a database connection string, which carries a privileged role's password. Not available in read-only mode. Starts turned off.
`get_database_tables`	Lists all the tables in a Neon database.
`describe_table_schema`	Returns a table's columns, data types and constraints.
`compare_database_schema`	Compares a database's schema on one branch with another branch, the parent by default.
`run_sql`	Runs one SQL statement on a Neon database. Starts turned off.
`run_sql_transaction`	Runs several SQL statements as one transaction. Not available in read-only mode. Starts turned off.
`explain_sql_statement`	Generates a statement's execution plan; with analyze, Postgres runs it with its side effects.
`list_slow_queries`	Lists pg_stat_statements queries by execution time, slowest first.
`inspect_database`	Runs one of the 15 read-only checks from neon inspect db, such as sizes, unused indexes or locks.
`prepare_database_migration`	Applies a schema change on a temporary branch to test it before completing it.
`complete_database_migration`	Applies or discards a prepared migration and deletes the temporary branch. Unless told otherwise, it applies it. Starts turned off.
`prepare_query_tuning`	Analyzes a slow query on a temporary branch to test changes that speed it up.
`complete_query_tuning`	Applies or discards the tuning changes and deletes the temporary branch. Unless told otherwise, it discards them. Starts turned off.
`provision_neon_auth`	Turns on Neon Auth for a branch and connects it to an authentication provider. Starts turned off.
`provision_neon_data_api`	Creates a Neon Data API instance on a branch. Starts turned off.

The limits

What the Neon integration does NOT do

We would rather say it here than have you find out during rollout.

It is not meant for production databases. Neon recommends its MCP server for development and testing, not connecting it to production databases and not exposing personal data.
It does not ask you for confirmation in the chat before writing. Deleting, creating or resetting projects and branches, running SQL and completing a migration start turned off; if the admin turns them on in Connections, the Met runs them.
It does not limit SQL on its own. If the admin turns on the SQL query, which starts turned off, with full access it runs the statement the Met writes; to limit it, authorize read-only or pin a Postgres role with narrow permissions.
It does not limit what a role created in the Neon console reads. Those roles are members of neon_superuser and read all data; the narrow role is created with SQL.
It does not pay your Neon plan. The projects and branches it creates, with their compute, stay in your account; Meteor does not resell the service.

Before you start

What you need to connect Neon

1

A Neon account with your projects

The account your team manages its Neon databases with. The Met works with the projects that account can access.
2

Connect it in Met

In Met, open Connections → Neon → Connect. A Neon window opens so you sign in and authorize Met; there you choose read-only or full access and, if you want, a Postgres role.
3

The Neon server IPs, if you use IP Allow

If your project has IP Allow on, add the addresses of Neon's hosted MCP server, 34.192.103.46 and 23.22.233.166, to the list so it can connect.

Frequently asked questions

Questions about Neon and Meteor

Yes. In the Neon authorization window you choose read-only. SELECT queries and schema inspection stay available, and creating branches, running migrations and changing the Auth configuration are turned off. In Met, the SQL query starts turned off anyway: the admin turns it on if the Met needs it.

It is optional. If you set it, the SQL tools log in as that role instead of the database owner, so its permissions decide what the Met can read and change.

Only if the admin turns that action on, because it starts turned off. Deleting a project in Neon deletes all its data.

You do, with your Neon account and plan. Meteor does not resell Neon: the connector uses your company's account.

Step by step