IntegrationsNeon integration
Your Neon database.Read before it is changed.
Connect Neon to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists projects and branches, reads table schemas, compares a branch's schema with its parent and finds slow queries. CoreSpeed proxies Neon's own hosted MCP server. Running SQL, or explaining a query with analyze, can change a database, and approvals can hold either call.
From a slow queryto a reviewed fix.
Requests you can make once Neon is connected. The data is fictional.
- NeonSlow queries · main
Top three by mean time
- SELECT … FROM orders WHERE customer_id = $1: 1.8 s
- SELECT … FROM invoices JOIN orders …: 640 ms
- UPDATE sessions SET last_seen = …: 210 ms
Find the slow query
Read only · No SQL run
- NeonBranches · add-refunds
Schema diff against the parent
- + ALTER TABLE orders ADD COLUMN refund_reason text
- + CREATE TABLE refunds (…)
- + CREATE INDEX ON refunds (order_id)
Check a branch
Compared, nothing merged
Approval requestWaiting
Cursor for Jessica
neon__run_sql
“Create an index on orders (customer_id) on the main branch.”
Policy: Ask before running any SQL on Neon.
ApproveDeny
Hold the SQL
Ask
Find the slow query.Plan the fix.
Have your agent rank the slow queries, read the table behind the worst one, and explain its plan. You get an index to review, not a change.
Reads fromNeon
All connectors →In my Neon project, list the slowest queries on the main branch, describe the orders table, and explain the worst query without analyze. Do not run anything that writes.
neon__list_slow_queriesok
Orders by customer, 1.8 s mean
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect Neon
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor