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 Google ADK 17 tools — connect in under 2 minutes

Name: Neon
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 17 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Neon as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

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

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="neon_agent",
    instruction=(
        "You help users interact with Neon "
        "using 17 available tools."
    ),
    tools=[mcp_tools],
)

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.

Google ADK natively supports Neon as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 17 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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 Google ADK 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 Google ADK via MCP

Follow these steps to integrate the Neon MCP Server with Google ADK.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 17 tools from Neon via MCP

Why Use Google ADK with the Neon MCP Server

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

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Neon

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

Seamless integration with Google Cloud services means you can combine Neon tools with BigQuery, Vertex AI, and Cloud Functions

Neon + Google ADK Use Cases

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

Enterprise data agents: ADK agents query Neon and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Neon tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Neon regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Neon

Neon MCP Tools for Google ADK (17)

These 17 tools become available when you connect Neon to Google ADK 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 Google ADK

Ready-to-use prompts you can give your Google ADK 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 Google ADK

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

McpToolset not found

Update: pip install --upgrade google-adk

Neon + Google ADK FAQ

Common questions about integrating Neon MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.