2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 17 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Neon through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "neon": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Neon Agent",
    instructions:
      "You help users interact with Neon " +
      "using 17 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Neon?"
  );
  console.log(result.text);
}

main();
Neon
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.

Mastra's agent abstraction provides a clean separation between LLM logic and Neon tool infrastructure. Connect 17 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Neon MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 17 tools from Neon via MCP

Why Use Mastra AI with the Neon MCP Server

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

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Neon without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Neon tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Neon + Mastra AI Use Cases

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

01

Automated workflows: build multi-step agents that query Neon, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Neon as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Neon on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Neon tools alongside other MCP servers

Neon MCP Tools for Mastra AI (17)

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

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

get_branch

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

09

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

10

get_project

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

11

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

12

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

13

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

14

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

15

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

16

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

17

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 Mastra AI

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

01

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

02

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

03

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

Troubleshooting Neon MCP Server with Mastra AI

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Neon + Mastra AI FAQ

Common questions about integrating Neon MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Neon to Mastra AI

Get your token, paste the configuration, and start using 17 tools in under 2 minutes. No API key management needed.