Bring Postgresql
to AutoGen
Create your Vinkius account to connect Neon to AutoGen and start using all 17 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Neon MCP Server?
Connect your Neon account to any AI agent and take full control of your serverless PostgreSQL infrastructure through natural conversation.
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
How it works
- Subscribe to this server
- Enter your Neon API Key
- Start managing your serverless Postgres from Claude, Cursor, or any MCP-compatible client
No more clicking through the Neon console to provision a branch or grab a connection URI. Your AI acts as a dedicated DBA.
Who is this for?
- Developers — instantly provision development branches, grab connection URIs and create test databases without leaving your IDE
- DevOps Engineers — audit project configurations, manage branches for CI/CD pipelines and review compute endpoint status
- DBAs — create roles, manage databases across branches and track PostgreSQL version upgrades via conversation
Built-in capabilities (17)
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
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
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
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
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
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
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
Provide both the project_id and branch_id. Get details for a specific Neon branch
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
Provide the project_id (e.g. "purple-shape-411361") obtained from list_projects. Get details for a specific Neon project
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
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
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
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
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
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
Provide the project_id and the new name. This does not affect branches, databases or endpoints. Update a Neon project name
Why AutoGen?
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.
- —
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 in AutoGen
Why run Neon with Vinkius?
The Neon connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 17 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Neon using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Neon and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Neon to AutoGen through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Neon for AutoGen
Every request between AutoGen and Neon is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
How do I create a Neon API Key?
Log in to the Neon Console, 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.
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.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"
Explore More MCP Servers
View all →
Google Roads
4 toolsAccess Google Roads API — snap GPS tracks to roads, find nearest road segments, and get speed limit data for any road segment worldwide from any AI agent.

BLS Labor Force — National Unemployment & CPS
2 toolsAccess Current Population Survey (CPS) data. Easily query national unemployment rates, labor force participation, and detailed demographic breakdowns at the push of a button.

Ahrefs
10 toolsProfessional SEO intelligence — audit backlinks, keywords, and domain health via AI.

Monday.com (Work Management & CRM)
9 toolsManage work via Monday.com — list project boards, track task items, and audit team workspaces.
