How to integrate Doppler MCP with Pydantic AI

GET STARTED FOR FREE
Framework Integration Gradient
Doppler Logo
Pydantic AI Logo
divider

Introduction

This guide walks you through connecting Doppler to Pydantic AI using the Composio tool router. By the end, you'll have a working Doppler agent that can get secrets for staging environment in doppler, add a new secret to marketing project, list all projects and their environments through natural language commands.

This guide will help you understand how to give your Pydantic AI agent real control over a Doppler account through Composio's Doppler 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:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Doppler
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Doppler workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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

The Doppler MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Doppler account. It provides structured and secure access so your agent can perform Doppler operations on your behalf.

Supported Tools & Triggers

Tools
Get Authenticated User InfoTool to retrieve information about the authenticated user or token.
Get Config LogTool to retrieve a specific config log from Doppler.
List Config LogsTool to retrieve configuration change logs for a specific config in a project.
Get ConfigTool to retrieve a specific Doppler config by project and config name.
List Doppler ConfigsTool to list configurations from a Doppler project.
Create Encrypted Share LinkTool to generate a Doppler Share link by sending an encrypted secret.
Create Plain Text Share LinkTool to generate a Doppler Share link by sending a plain text secret.
List EnvironmentsTool to list all environments in a Doppler project.
List IntegrationsTool to retrieve all existing integrations in Doppler.
List Change RequestsTool to list existing change requests in the Doppler workplace.
Get Project RoleTool to retrieve details of a specific project role in Doppler.
List Project RolesTool to list all available project roles in Doppler.
List Project Role PermissionsTool to list all available permissions for project roles in Doppler.
Get Project DetailsTool to retrieve details of a specific Doppler project by its identifier.
List Doppler ProjectsTool to list all Doppler projects in your workspace.
Delete SecretTool to delete a secret from a Doppler config.
Download SecretsTool to download secrets from a Doppler config in various formats.
Get SecretTool to retrieve a specific secret from a Doppler project config.
List Doppler SecretsTool to list all secrets for a specific Doppler config within a project.
List Secret NamesTool to retrieve the list of secret names from a specific Doppler config.
Update Doppler SecretsTool to update secrets in a Doppler config.
Update Secret NoteTool to update a note for a secret in Doppler.
Get Workplace InformationTool to retrieve workplace information from Doppler.
Get Workplace RoleTool to retrieve workplace role information from Doppler.
List Workplace RolesTool to list all workplace roles in your Doppler workspace.
List Workplace PermissionsTool to retrieve all available workplace permissions in Doppler.

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:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming

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 pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Doppler
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Doppler
  • MCPServerStreamableHTTP connects to the Doppler MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Doppler
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["doppler"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Doppler tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
doppler_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[doppler_mcp],
    instructions=(
        "You are a Doppler assistant. Use Doppler tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Doppler endpoint
  • The agent uses GPT-5 to interpret user commands and perform Doppler operations
  • The instructions field defines the agent's role and behavior

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Doppler.\n")

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", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Doppler API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Doppler and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Doppler
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["doppler"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    doppler_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[doppler_mcp],
        instructions=(
            "You are a Doppler assistant. Use Doppler tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Doppler.\n")

    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", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

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

Conclusion

You've built a Pydantic AI agent that can interact with Doppler through Composio's Tool Router. With this setup, your agent can perform real Doppler actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Doppler for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

How to build Doppler MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Doppler MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Doppler MCP with Claude Agent SDK

Google ADK

Google ADK

Use Doppler MCP with Google ADK

LangChain

LangChain

Use Doppler MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Doppler MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Doppler MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Doppler MCP with LlamaIndex

CrewAI

CrewAI

Use Doppler MCP with CrewAI

Claude Code

Claude Code

Use Doppler MCP with Claude Code

Codex

Codex

Use Doppler MCP with Codex

FAQ

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

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

Can I use Tool Router MCP with Pydantic AI?

Yes, you can. Pydantic 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 Doppler tools.

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

Yes, absolutely. You can configure which Doppler 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 Doppler 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