Neon MCP connector
The Neon connector brings your Postgres projects, branches, tables and queries to Claude, ChatGPT, Cursor and any MCP client, so your team can query live data, plan migrations and tune slow queries with their own Neon access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
114 tools
How to connect
How to connect Neon to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Neon once
-
Open Connections, choose Add connection, and pick Neon.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Neon. Neon's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Neon MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Neon MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Neon MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Neon to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Neon through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Plan a migration before touching production
Ask for the schema of the orders table, have the agent prepare the migration on a branch, review the change, then complete it once you are satisfied.
-
Data
Answer a question straight from the tables
Type the question in plain words, let the agent run the query against the right branch, and get the numbers back without opening a SQL editor.
-
Platform
Find the queries slowing a project down
Pull the list of slow queries for a project, ask the agent to explain the worst one, and walk through query tuning before it reaches customers.
-
Support
Look up a customer's record during a ticket
Run a read against the production branch to confirm what the account actually holds, instead of waiting for an engineer to check.
-
Product
Set up a project for a new experiment
Create a Neon project, describe its branches, and hand the connection string to the team building the feature, all from one conversation.
-
Analytics
Check what a table really contains
Inspect the database, read the table schema and sample the rows before building a report on top of it, so the report starts from facts.
Try asking
- “List the slow queries in the production project this week.”
- “Describe the schema of the orders table on the main branch.”
- “Prepare a migration that adds an index to the users table.”
Compare
Elaichi vs Zapier MCP vs Composio for Neon
All three can connect Neon to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Neon tools | Allow or restrict single Neon tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Neon call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Neon tools for your AI agents
114 tools are ready to call through Elaichi's MCP endpoint the moment you connect Neon, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Neon builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Neon gets you
6 screens from the product, each doing one job for your Neon account.
The agent
Ask your Neon database questions in plain words.
Answers come from live tables, branches and queries, not from a stale export.
- projects
- branches
- tables
- migrations
Ask Elaichi to work across your apps.
List the slow queries in the production project this week.
Describe the schema of the orders table on the main branch.
Prepare a migration that adds an index to the users table.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Neon in every client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
114 Neon tools, no custom code required.
Projects, branches, tables, migrations and query tuning are covered without an engineer writing anything.
- List organizations
- Run SQL
- Run SQL transaction
- Describe table schema
ElaichiToolsToolboxes
Every team gets its own Neon toolbox.
Data keeps analysis, platform keeps migrations, and support sees only what it needs.
- Engineering
- Data
- Platform
- Support
ElaichiToolboxesShared connections
Teammates query Neon without seeing a credential.
One person connects, shares with teams, and the connection string never changes hands.
- Production
- Staging
- Data Platform
- Engineering
ElaichiConnectionsAudit log
Every Neon query is logged with a name.
When, who, what happened and which project, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs Neon work end to end.
Slow queries are fetched, grouped and drafted into a digest a person approves before posting.
Neon digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Neon
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Neon
Queued
Collections and dashboards
Neon health numbers arrive before anyone asks.
Four metrics and a 14 day chart, computed from Neon records with no model involved.
Neon health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Branches
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Data Platform 21%
Engineering 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Neon to Claude?
Connect Neon in Elaichi first: pick Neon from the catalog, click connect, and approve the request on Neon's own sign-in page, since Neon connects over OAuth with no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on your Neon projects, branches and tables are available in every conversation.
Does Neon work with ChatGPT and Cursor as well as Claude?
Yes. Once Neon is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Neon once and every client picks it up.
What can an AI agent actually do with my Neon data?
With Neon connected, an agent can list your projects and branches, describe a table's schema, run a query or a transaction, explain why a statement is slow, prepare and complete a migration, fetch a connection string, and create or update a project. Short, concrete asks work best: "show me the slow queries in the billing project" gets a better answer from Neon than a long paragraph of instructions.
Does connecting Neon give the AI every project and branch?
No. Every call to Neon runs as the person who signed in, so the agent sees only the organizations, projects and branches that person can already reach in Neon. Elaichi can narrow that further, for example to read-only queries on one project, but it can never widen it beyond what Neon itself allows that person.
Can I stop an agent from deleting or changing things in Neon?
Yes. Restrictions in Elaichi apply per action, so you can allow reading tables and explaining queries in Neon while blocking migrations, transactions and project updates. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.
What happens to a Neon connection when someone leaves?
Offboarding a person in Elaichi ends their access to Neon through every client at once. If they connected a Neon account that is shared with a team, the connection keeps working for everyone else. Disconnecting Neon once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Neon MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Neon is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Neon?
Yes. Both let Claude, ChatGPT or Cursor use Neon. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Neon call.
How is Elaichi different from Composio for Neon?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Neon: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Neon in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.