How to integrate Neon MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Neon Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Neon to Mastra AI using the Composio tool router. By the end, you'll have a working Neon agent that can create a new neon project with autoscaling, add a developer's email permission to a project, spin up a new branch database for testing, generate an api key limited to a project through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Neon account through Composio's Neon MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Neon tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Neon tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Neon agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Neon MCP server, and what's possible with it?

The Neon MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Neon account. It provides structured and secure access to your serverless Postgres databases and project infrastructure, so your agent can perform actions like managing projects, configuring authentication, creating branches, and automating database operations on your behalf.

  • Project management and insights: Retrieve detailed information about specific Neon projects, including configurations, workflows, and current status for monitoring or troubleshooting.
  • Automated role and permission setup: Grant email-based permissions, add new roles to branches, and streamline access control across your projects with granular, automated adjustments.
  • Seamless API key and authentication management: Create new API keys for organizations or projects, manage authentication flows, and securely handle access credentials for integrations.
  • Database and branch orchestration: Spin up new Postgres databases within branches, create and configure compute endpoints, and automate the creation of development, testing, or isolated environments as needed.
  • Custom project provisioning: Launch new Neon projects with advanced quota, resource, and networking settings—tailored to your application's requirements and operational best practices.

Supported Tools & Triggers

Tools
Access project details by idRetrieves detailed information about a specific project within the neon b2b saas integration platform.
Add new jwks to project endpointAdds a new json web key set (jwks) to a specific endpoint of a project in the neon b2b saas integration platform.
Add project email permissionAdds permissions for a specified email address to a particular project within the neon b2b saas integration platform.
Add role to branchCreates a new role within a specific branch of a project in the neon b2b saas integration platform.
Create api key for organizationCreates a new api key for the specified organization, with optional project-specific access limitations.
Create branch databaseCreates a new database within a specified project and branch in the neon platform.
Create compute endpointCreates a new compute endpoint for a specified branch within a neon project.
Create new api keyCreates a new api key for accessing the neon b2b saas integration platform.
Create new project branchCreates a new branch in a neon project with optional compute endpoints.
Create project with quota and settingsCreates a new neon project with specified configuration settings.
Create vpc endpoint labelUpdates the label of a specific vpc endpoint within a project in the neon b2b saas integration platform.
Create vpc endpoint with labelUpdates the label of a specific vpc endpoint within an organization's virtual private cloud (vpc) in a particular aws region.
Delete api key by idDeletes a specific api key from the neon platform.
Delete database from branchDeletes a specific database from a designated branch within a project in the neon platform.
Delete organization api keyDeletes a specific api key associated with an organization in the neon platform.
Delete organization memberRemoves a specific member from an organization within the neon b2b saas integration platform.
Delete project branch by idDeletes a specific branch within a project in the neon b2b saas integration platform.
Delete project branch roleDeletes a specific role from a branch within a project in the neon b2b saas integration platform.
Delete project by idDeletes a specific project from the neon b2b saas integration platform.
Delete project endpointDeletes a specific endpoint within a neon project.
Delete project jwks by idDeletes a specific json web key set (jwks) associated with a given project in the neon b2b saas integration platform.
Delete project permissionDeletes a specific permission associated with a project in the neon b2b saas integration platform.
Delete vpc endpoint by idsDeletes a specific vpc endpoint within a given organization and region in the neon b2b saas integration platform.
Delete vpc endpoint by project idDeletes a specific vpc endpoint within a designated project in the neon platform.
Fetch database for branchRetrieves a list of databases associated with a specific project and branch in the neon platform.
Fetch organization members by idRetrieves a list of all members associated with a specific organization in the neon b2b saas integration platform.
Fetch vpcendpoint details by idRetrieves detailed information about a specific vpc endpoint within an organization's infrastructure in a particular aws region.
Get branches for projectRetrieves a list of branches associated with a specific project in the neon b2b saas integration platform.
Get branch roles for projectRetrieves the roles associated with a specific branch within a project in the neon b2b saas integration platform.
Get consumption history projectsRetrieves the consumption history for specified projects within the neon platform.
Get current user informationRetrieves the profile information for the currently authenticated user.
Get organization api keysRetrieves a list of all api keys associated with a specific organization in the neon b2b saas integration platform.
Get project branchesRetrieves detailed information about a specific branch within a neon project.
Get project branch roleRetrieves detailed information about a specific role within a particular branch of a neon project.
Get project connection uriRetrieves the connection uri for a specified project within the neon b2b saas integration platform.
Get project endpoint informationRetrieves a list of all endpoints associated with a specific project in the neon b2b saas integration platform.
Get project operation by idRetrieves detailed information about a specific operation within a project in the neon b2b saas integration platform.
Get schema for project branchRetrieves the schema definition for a specific branch within a project in the neon b2b saas integration platform.
Get user organizationsRetrieves a list of organizations associated with the currently authenticated user in the neon platform.
Get vpc region endpointsRetrieves a list of vpc endpoints for a specified organization within a particular aws region.
List api keysRetrieves a list of api keys associated with the authenticated user's neon account.
List shared projectsRetrieves a list of shared projects accessible to the authenticated user within the neon b2b saas integration platform.
Modify branch details in projectUpdates the details of a specific branch within a project in the neon platform.
Patch branch database informationUpdates the properties of a specific database within a project branch in the neon platform.
Reset role password for branchResets the password for a specific role within a project branch in the neon b2b saas integration platform.
Restart project endpointRestarts a specific endpoint within a project in the neon b2b saas integration platform.
Restore project branchThis endpoint restores a branch to a specific state or point in time.
Retrieve account consumption historyRetrieves the consumption history for a specified account within the neon platform.
Retrieve all regionsRetrieves a list of available geographic regions supported by the neon b2b saas integration platform.
Retrieve branch database detailsRetrieves detailed information about a specific database within a neon project and branch.
Retrieve branch endpointsRetrieves a list of endpoints associated with a specific branch of a project in the neon platform.
Retrieve jwks for projectRetrieves the json web key set (jwks) for a specified project.
Retrieve organization by idRetrieves detailed information about a specific organization within the neon platform.
Retrieve organization invitationsRetrieves a list of all pending invitations for a specified organization.
Retrieve organization member infoRetrieves detailed information about a specific member within an organization in the neon b2b saas integration platform.
Retrieve project endpoint detailsRetrieves detailed information about a specific endpoint within a project in the neon b2b saas integration platform.
Retrieve project operationsRetrieves a list of operations associated with a specific project in the neon b2b saas integration platform.
Retrieve project permissionsRetrieves the current permissions settings for a specific project within the neon b2b saas integration platform.
Retrieve projects listRetrieves a list of all neon projects associated with the authenticated user's account.
Retrieve vpc endpoints for projectRetrieves a list of vpc (virtual private cloud) endpoints associated with a specific project in the neon b2b saas integration platform.
Reveal role password in branchReveals the password for a specific role within a branch of a neon project.
Send organization invitationsCreates and sends invitations to join an organization in the neon b2b saas integration platform.
Set branch as defaultSets a specified branch as the default branch for a given project in neon.
Start endpoint for projectInitiates a specific process or workflow associated with a particular endpoint within a project in the neon b2b saas integration platform.
Suspend project endpoint by idSuspends a specific endpoint within a project in the neon b2b saas integration platform.
Transfer user projects to organizationTransfers multiple projects from the authenticated user's personal account to a specified organization within the neon b2b saas integration platform.
Update organization member roleUpdates the role of a specific member within an organization in the neon b2b saas integration platform.
Update project compute endpoint settingsUpdates the configuration of a specific compute endpoint within a neon project.
Update project settings by idUpdates the configuration and settings of a specific neon project.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Neon through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Neon

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["neon"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Neon MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "neon" for Neon access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Neon toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "neon-mastra-agent",
    instructions: "You are an AI agent with Neon tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        neon: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Neon toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Neon and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["neon"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      neon: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "neon-mastra-agent",
    instructions: "You are an AI agent with Neon tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { neon: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Neon through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Neon MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Neon MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Neon MCP with Claude Agent SDK

Google ADK

Google ADK

Use Neon MCP with Google ADK

LangChain

LangChain

Use Neon MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Neon MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Neon MCP with LlamaIndex

CrewAI

CrewAI

Use Neon MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Neon MCP?

With a standalone Neon MCP server, the agents and LLMs can only access a fixed set of Neon tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Neon and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Neon tools.

Can I manage the permissions and scopes for Neon while using Tool Router?

Yes, absolutely. You can configure which Neon scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Neon data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free