Neon MCP server
Neon is a serverless Postgres platform for building scalable applications with branchable databases and instant compute that scales to zero when idle. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Neon.
List organizations
Use when discovering organization IDs available to your personal API key before listing projects. Returns organization metadata only.
List projects
Use when finding projects accessible to your personal API key. Pass an organization ID from list_organizations for its projects, and the cursor for more.
List branches
Use when finding branches or reconciling an uncertain create_branch by its name. Follow nextCursor; a successful create response does not mean its operations have finished.
10 Neon actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
8Look things up, subject to your permissions.
- neon.list_organizationsList organizations
Use when discovering organization IDs available to your personal API key before listing projects. Returns organization metadata only.
- neon.list_projectsList projects
Use when finding projects accessible to your personal API key. Pass an organization ID from list_organizations for its projects, and the cursor for more.
- neon.list_branchesList branches
Use when finding branches or reconciling an uncertain create_branch by its name. Follow nextCursor; a successful create response does not mean its operations have finished.
- neon.list_databasesList databases
Use when inspecting the database names and owning Postgres roles in a branch. Returns metadata only and does not run SQL.
- neon.list_rolesList roles
Use when checking Postgres roles in a branch. Passwords are deliberately excluded; this action does not retrieve credentials or change permissions.
- neon.list_operationsList operations
Use when checking whether branch operations have finished or failed. Follow the cursor for older operations; do not retry an uncertain write before reading back its branch.
- neon.get_projectGet project
Use when inspecting a known project or reading it back after a change. Returns resource metadata without owner personal data or credentials.
- neon.get_branchGet branch
Use when inspecting a known branch or reading it back after a change. Returns resource metadata without owner personal data or credentials.
write
1Create and change things. Allow, or ask the user first.
- neon.create_branchCreate branch
Use when forking an explicit parent into a named branch without a compute endpoint. Branch/storage charges may accrue. After a timeout, list branches by name before retrying; poll operations before use.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- neon.delete_branchDelete branch
Use when removing a disposable branch after confirming its exact ID. Disconnects its clients; cannot remove a root/default branch or one with children. Acceptance is not completion: check operations and read back before assuming deletion.
Control access to Neon.
Connect the intended Neon account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- neon.create_branch: require approval
- neon.delete_branch: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Neon connects.
Connect Neon using Personal API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- Personal API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Neon with your AI client.
Sign in to Arc0 and connect Neon in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Neon with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingNeon with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingNeon with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingNeon with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingNeon with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingNeon with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More databases and spreadsheets apps.
Neon and Arc0, answered.
Does Neon work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Neon with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Neon MCP server?
This is Arc0’s integration page, not a claim of an official Neon server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Neon for its own current MCP offerings.
Which Neon actions are supported?
10 registry-defined actions: 8 read, 1 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Neon need?
Connect Neon using Personal API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Neon?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Neon through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Neon into your agent.
Neon MCP server: 10 actions including list organizations, list projects, list branches. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Neon and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Neon.