How to integrate Neon MCP with Autogen

Framework Integration Gradient
Neon Logo
AutoGen Logo
divider

Introduction

This guide walks you through connecting Neon to AutoGen 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 AutoGen 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 OpenAI and Composio API keys
  • Install the required dependencies for Autogen and Composio
  • Initialize Composio and create a Tool Router session for Neon
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Neon tools
  • Run a live chat loop where you ask the agent to perform Neon operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

  • Multi-Agent Systems: Build collaborative agent workflows
  • MCP Workbench: Native support for Model Context Protocol tools
  • Streaming HTTP: Connect to external services through streamable HTTP
  • AssistantAgent: Pre-built agent class for tool-using assistants

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

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Neon account you can connect to Composio
  • Some basic familiarity with Autogen and Python async

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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

bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Neon via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

  • COMPOSIO_API_KEY is required to talk to Composio
  • OPENAI_API_KEY is used by Autogen's OpenAI client
  • USER_ID is how Composio identifies which user's Neon connections to use

Import dependencies and create Tool Router session

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Neon session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["neon"]
    )
    url = session.mcp.url
What's happening:
  • load_dotenv() reads your .env file
  • Composio(api_key=...) initializes the SDK
  • create(...) creates a Tool Router session that exposes Neon tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

  • url points to the Tool Router MCP endpoint from Composio
  • timeout is the HTTP timeout for requests
  • sse_read_timeout controls how long to wait when streaming responses
  • terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Neon assistant agent with MCP tools
    agent = AssistantAgent(
        name="neon_assistant",
        description="An AI assistant that helps with Neon operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Neon tools from the workbench

Run the interactive chat loop

python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Neon related question or task to the agent.\n")

# Conversation loop
while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
What's happening:
  • The script prompts you in a loop with You:
  • Autogen passes your input to the model, which decides which Neon tools to call via MCP
  • agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
  • Typing exit, quit, or bye ends the loop

Complete Code

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

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Neon session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["neon"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Neon assistant agent with MCP tools
        agent = AssistantAgent(
            name="neon_assistant",
            description="An AI assistant that helps with Neon operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Neon related question or task to the agent.\n")

        # Conversation loop
        while True:
            user_input = input("You: ").strip()

            if user_input.lower() in ['exit', 'quit', 'bye']:
                print("\nGoodbye!")
                break

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

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

Conclusion

You now have an Autogen assistant wired into Neon through Composio's Tool Router and MCP. From here you can:
  • Add more toolkits to the toolkits list, for example notion or hubspot
  • Refine the agent description to point it at specific workflows
  • Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Neon, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

How to build Neon MCP Agent with another framework

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 Autogen?

Yes, you can. Autogen 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.