How do I create a Neon API Key?

Log in to the [**Neon Console**](https://console.neon.tech), go to **Account Settings** > **API Keys** (or **Organization Settings** > **API Keys**), click **Create New**, choose the scope (Personal, Organization or Project-scoped), and copy the token immediately — it is shown only once.

What is a Neon branch and how does branching work?

A Neon branch is an isolated PostgreSQL environment with its own compute, databases and roles. Branches are created instantly using copy-on-write cloning from a parent branch (default: primary). This means zero data copy and instant provisioning. Each branch gets its own compute endpoints and can have different PostgreSQL schemas and data.

Can I get a ready-to-use connection URI?

Yes! Use the `get_connection_uri` tool with your project_id and optionally a branch_id. It returns a complete PostgreSQL connection string (postgres://user:password@host/dbname) ready to use with psql, ORMs or application clients.

Can the agent delete projects and branches?

Yes, the agent has tools to delete both projects and branches. Deleting a project marks it for recovery (7-day grace period) but destroys all associated data. Deleting a branch is irreversible and removes all its databases, roles and endpoints. Use caution when executing these actions.

Neon MCP Server for AutoGen 17 tools — connect in under 2 minutes

Name: Neon
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 17 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Neon as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="neon_agent",
            tools=tools,
            system_message=(
                "You help users with Neon. "
                "17 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Neon MCP Server

Connect your Neon account to any AI agent and take full control of your serverless PostgreSQL infrastructure through natural conversation.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Neon tools. Connect 17 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

Project Management — List, create, update and delete Neon projects with region and PostgreSQL version selection
Branch Operations — Create instant branches via copy-on-write cloning, set primary branches and manage branch lifecycle
Compute Endpoints — Provision read-write and read-only compute hosts for your branches
Database Administration — Create and list PostgreSQL databases within any branch
Role Management — Create database roles (users) with auto-generated passwords for secure access
Connection URIs — Get ready-to-use psql connection strings for any branch

The Neon MCP Server exposes 17 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Neon to AutoGen via MCP

Follow these steps to integrate the Neon MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 17 tools from Neon automatically

Why Use AutoGen with the Neon MCP Server

AutoGen provides unique advantages when paired with Neon through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Neon tools to solve complex tasks

Role-based architecture lets you assign Neon tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Neon tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Neon tool responses in an isolated environment

Neon + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Neon MCP Server delivers measurable value.

Collaborative analysis: one agent queries Neon while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Neon, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Neon data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Neon responses in a sandboxed execution environment

Neon MCP Tools for AutoGen (17)

These 17 tools become available when you connect Neon to AutoGen via MCP:

create_branch

Optionally set a human-readable name and a parent branch ID to clone from (if omitted, clones from the project's primary branch). Branches are created instantly with zero data copy overhead. Returns the new branch along with its initial endpoints, databases and roles. Create a new branch in a Neon project

create_database

Requires the database name. Optionally set the owner role name (must exist in the branch — see list_roles). Returns the new database metadata. Create a new database in a Neon branch

create_endpoint

Specify the endpoint type: "read_write" for full access or "read_only" for read replicas. A branch can have at most one read_write endpoint. Returns the new endpoint with its connection host and configuration. Create a compute endpoint for a Neon branch

create_project

Optionally set a human-readable name, AWS region (e.g. "aws-us-east-2", "aws-eu-central-1") and PostgreSQL version (15, 16, 17). A default branch, database and read-write endpoint are automatically provisioned. Returns the new project along with its initial connection URIs, roles, databases and endpoints. Create a new Neon project

create_role

The role can be used to authenticate database connections and own databases. Provide the project_id, branch_id and desired role name. Returns the new role metadata including the generated password. Create a new database role in a Neon branch

delete_branch

The primary branch cannot be deleted — set another branch as primary first. Provide the project_id and branch_id. WARNING: this action is irreversible and destroys all branch data. Delete a Neon branch

delete_project

The project is recoverable for 7 days via the Neon console. All associated branches, databases, endpoints and data are deleted. Provide the project_id. WARNING: this action destroys all data in the project. Delete a Neon project

get_branch

Provide both the project_id and branch_id. Get details for a specific Neon branch

get_connection_uri

Optionally specify a branch_id to get the URI for a specific branch (defaults to the primary branch). The URI includes the host, database name, role and password. Use this to connect psql, ORM tools or application clients. Get a PostgreSQL connection URI for a Neon project

get_project

Provide the project_id (e.g. "purple-shape-411361") obtained from list_projects. Get details for a specific Neon project

list_branches

Each branch is an isolated PostgreSQL environment with its own compute, databases and roles. Branches can be created from any point-in-time using copy-on-write cloning. Returns branch ID, name, parent ID, primary status, creation date and current state. Use the project_id from list_projects. List branches in a Neon project

list_databases

Each database has a name, owner role and creation metadata. Use the project_id and branch_id to scope the query. List databases in a Neon branch

list_endpoints

Each endpoint has a type (read_write or read_only), host address, current state (active, idle, suspended) and autoscaling configuration. A branch can have at most one read_write endpoint. Use the project_id and branch_id. List compute endpoints for a Neon branch

list_projects

Each project is a workspace that contains branches, compute endpoints, databases and roles. Returns project ID, name, region, PostgreSQL version, creation date and resource usage metadata. Use this as the starting point for all Neon operations — you need a project_id to manage branches, databases or endpoints. List all Neon projects

list_roles

Each role has a name, creation date and privilege metadata. Use the project_id and branch_id to scope the query. Roles are used to authenticate database connections and control access. List database roles in a Neon branch

set_primary_branch

The primary branch is the default source for new branch cloning and receives the default read-write compute endpoint. Provide the project_id and the branch_id to promote. Set a branch as the primary branch of a Neon project

update_project

Provide the project_id and the new name. This does not affect branches, databases or endpoints. Update a Neon project name

Example Prompts for Neon in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Neon immediately.

"List all my Neon projects and show me which regions they're in."

"Create a new branch called 'feature-auth' from the primary branch of my project."

"Get the connection URI for the main branch of my project."

Troubleshooting Neon MCP Server with AutoGen

Common issues when connecting Neon to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Neon + AutoGen FAQ

Common questions about integrating Neon MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Neon tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.