Neon MCP server
Neon in any MCP client, through Memtro: Neon does not publish this server. Memtro's Neon connector reads Neon through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Neon serverless Postgres: projects, branches, compute endpoints and their state, recent operations and failures, databases on a branch, snapshots, and usage history. When asked it can create, rename, protect, restore, snapshot, set as default or delete a branch, create a database, start, suspend, restart, resize or delete a compute, and rename, set history retention on or delete a project. Never returns connection strings, passwords or table data.
Reads
neon_list_projectsNeon projects (each a Postgres instance with its branches): name, region, Postgres version, organization, when created and updated…neon_get_projectOne Neon project with this billing period's compute hours, active hours, data written and transferred, history retention and branch size limit.neon_list_branchesBranches of a Neon project: name, parent, state (init, resetting, ready, archived), default or protected, logical size, created, updated…neon_list_endpointsCompute endpoints of a Neon project: which branch, read-write or read-only, state (active, idle, init), autoscaling range in compute units…neon_list_operationsRecent operations on a Neon project (compute starts and suspends, branch creation, config changes) with status, error and duration.neon_list_databasesDatabases on a Neon branch: name, owning role and when created.neon_usage_historyUsage history per Neon project (compute unit seconds, storage, data transfer) per hour, day or month, oldest first, with totals per metric.neon_list_snapshotsSnapshots of a Neon project: id, name, the branch and point in time captured, when made, expiry, and whether manual or scheduled.
Acts, when you ask
These change something in Neon. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
neon_create_branchCreate a branch of a Neon project, from the default branch or a named parent, optionally at a past point in time, only when asked.neon_update_branchRename a Neon branch, protect or unprotect it (a protected branch cannot be deleted or reset), or set when Neon deletes it automatically…neon_set_default_branchMake a Neon branch the project's default, taking the default from the branch that had it.neon_restore_branchRestore a Neon branch to an earlier state of itself or another branch, at a timestamp or (with neither) the source's head.neon_create_snapshotTake a snapshot of a Neon branch now or at a past time within its restore window, only when asked.neon_delete_branchPermanently delete a Neon branch with its data.neon_create_databaseCreate a Postgres database on a Neon branch, owned by an existing role, only when asked.neon_start_endpointStart a suspended Neon compute endpoint, which Neon bills for while it runs.neon_suspend_endpointSuspend a Neon compute endpoint now.neon_restart_endpointRestart a Neon compute endpoint (suspend then start at once).neon_update_endpointResize a Neon compute (autoscaling minimum and maximum in compute units), change its scale-to-zero timeout (0 the plan default…neon_delete_endpointDelete a Neon compute endpoint.neon_update_projectRename a Neon project or change its history retention (the point-in-time restore window, in hours; 0 turns it off…neon_delete_projectDelete a Neon project with all its branches, computes, databases and roles.
Connect it
First connect Neon on Dashboard → Connections, then add Memtro to your client once. The Neon tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Neon connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Is the compute on the main branch active or idle?
- › Why did the database fail to start this morning?
- › Which branches were created this week, and by whom?
- › How many compute hours has the Acme project used this billing period?
- › Create a branch of main called invoice-fix with no compute
Questions
- Is this an official Neon MCP server?
- No. It is Memtro's MCP server with Memtro's Neon connector behind it: the connector reads Neon through its API with the credentials you connect on Dashboard → Connections, and Neon publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Neon?
- Only when you ask, and only what it has been granted: create a branch, optionally with a compute (billed); rename a branch, protect or unprotect it, or set its expiry; make a branch the project's default; restore a branch to an earlier point in time (replaces its data); take a snapshot of a branch; delete a branch (permanent); create a database on a branch; start a compute (billed); suspend a compute (drops connections); restart a compute (drops connections); resize a compute or change its scale-to-zero timeout; delete a compute (drops connections); rename a project or change its history retention; delete a project (recoverable in Neon for 7 days). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.