How to integrate Neon MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Neon Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Neon to the Claude Agent SDK 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 Claude Agent SDK 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:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Neon
  • Configure an AI agent that can use Neon as a tool
  • Run a live chat session where you can ask the agent to perform Neon operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Neon account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Neon functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Neon
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["neon"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Neon
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Neon tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Neon
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Neon and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Neon
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["neon"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Neon tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Neon through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Neon MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Neon MCP with OpenAI Agents 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

Mastra AI

Mastra AI

Use Neon MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Neon MCP with LlamaIndex

CrewAI

CrewAI

Use Neon MCP with CrewAI

Claude Code

Claude Code

Use Neon MCP with Claude Code

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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