Neon
Neon is a serverless Postgres platform that separates storage and compute, so databases scale automatically and can be branched like code. Developers use branches to give each feature, test run, or preview environment its own copy of the database.
The Neon integration lets developers manage projects and branches and run queries from Omnifact: create a Neon database branch to test a change, run SQL against it, and track down slow queries, then reset or delete the branch when you are done. Users sign in with their own Neon account and only see and change the projects they have access to in Neon.
- Provided by
- Neon
- Category
- Development
- Access
- Users sign in with their own Neon account and only see resources they have access to.
- Connects to
- https://mcp.neon.tech/mcp
- Product website
- neon.com
What you can do
Manage projects
List, create, update, and delete Neon projects, recover deleted ones, and see who has access.
Work with branches
Create a branch to test a change, reset it from its parent, set the default branch, or delete it when you are done.
Run queries
Run SQL statements or transactions against a branch and inspect the results.
Explore your schema
List tables, describe their columns and constraints, and compare schemas between branches.
Test migrations safely
Apply a schema change on a temporary branch, test it, and then apply or discard it.
Tune slow queries
Find the slowest queries, read their execution plans, run database health checks, and test index changes on a temporary branch.
Manage databases and roles
Create and delete databases and Postgres roles on a branch, reset role passwords, and get connection strings.
Control compute
Create, start, suspend, and restart the compute endpoints of your branches.
Back up and restore
Create snapshots, schedule automatic backups, and restore a snapshot onto a branch.
Check logs and configure services
Query branch logs and configure Neon Auth, the Data API, Functions, and object storage.
Related integrations
All integrations
GitLabA DevSecOps platform for source code management, code review, and CI/CD pipelines.
by GitLab
GitHubA platform for hosting code and collaborating on software development.
by GitHub
SentryAn application monitoring platform for tracking errors and performance problems in software.
by Sentry
PostHogA product analytics platform that also includes feature flags, experiments, session replay, and error tracking.
by PostHog
What to know before
using Neon with Omnifact
Use cases, setup, and permissions when your team connects Neon to Omnifact.
What can Omnifact do with Neon?
Omnifact handles everyday Postgres work in a chat. A developer asks which tables hold customer data or what changed between two schemas, a team lead sets up a database branch for a new feature, and a backend engineer runs a SQL query and gets the result explained in plain language. Omnifact reads everything live from Neon when you ask.
Can Omnifact find slow queries in Neon?
Yes. Omnifact lists the slowest queries in your Neon database, shows how each one is executed, and runs health checks. It then suggests an index and can try it on a temporary branch, so you compare the speed before and after. Backend engineers get a clear starting point without digging through the database by hand.
Can Omnifact test a schema change on a Neon branch first?
Yes. Omnifact applies a schema change, such as a new column or index, on a temporary Neon branch and checks the result against the original. You then decide whether to apply the change or discard the branch. Branches are Neon's way of trying changes safely, and Omnifact asks for your confirmation before it changes anything.
Which Neon projects can Omnifact see?
Exactly what you can already see in Neon. Everyone signs in with their own Neon account, so requests run with each person's own permissions, changes appear under their name, and nothing runs through a shared admin account. Anyone can disconnect their account again at any time.
Does Omnifact ask before changing data in Neon?
Yes. By default, running a write statement, resetting a branch, or deleting a project waits for your confirmation in the chat, while reading a schema or running a lookup runs right away. Admins decide which Neon actions are allowed, need confirmation, or are switched off. Neon recommends this kind of access for development and test branches, which are a good place to start.
How does Omnifact handle Neon data?
Your Neon data stays in Neon under your agreement with Neon. Omnifact reads schemas and query results live when a request needs them, instead of copying or indexing your database in advance, and what it reads becomes part of that conversation. The database itself stays hosted in the Neon region you chose. Omnifact is operated in Germany, business data is not used to train the connected AI models, and admins can limit Omnifact to European or Europe-hosted models.
How do I connect Neon to Omnifact?
An Omnifact admin adds Neon once for the whole organization, and everyone then signs in with their own Neon account. There is nothing to prepare in Neon. Anyone can disconnect their account again at any time.
Ready to automate work across your tools with Omnifact?
Connect Neon and the other tools your team already uses, and let Omnifact look up information and take care of everyday tasks.