How to integrate Doppler secretops MCP with OpenAI Agents SDK

Framework Integration Gradient
Doppler secretops Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Doppler secretops to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Doppler secretops agent that can list all recent config changes for project x, rollback staging config to previous version, clone production config to a new branch, lock main config to prevent accidental edits through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Doppler secretops account through Composio's Doppler secretops 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 necessary dependencies
  • Initialize Composio and create a Tool Router session for Doppler secretops
  • Configure an AI agent that can use Doppler secretops as a tool
  • Run a live chat session where you can ask the agent to perform Doppler secretops operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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

The Doppler secretops 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 secretops account. It provides structured and secure access to your secrets management platform, so your agent can perform actions like auditing activity logs, managing environment configs, rolling back changes, and automating config cloning on your behalf.

  • Fetch activity and config logs: Quickly retrieve detailed activity logs and config change histories to monitor changes and track security events across your Doppler workspace.
  • Rollback and restore configurations: Direct your agent to roll back a config to a previous version, helping you easily undo unwanted or risky changes with confidence.
  • Clone and create branch configs: Automate the cloning of config branches or create new branch configs for different environments and projects, streamlining your secrets management workflows.
  • Config locking and deletion: Secure your critical configs by locking them against unwanted changes or safely deleting obsolete configurations as part of environment cleanup.
  • Retrieve detailed config metadata: Instantly get comprehensive details for any specific config, including project and environment context, to support debugging and compliance tasks.

Supported Tools & Triggers

Tools
Activity Logs ListTool to list workplace activity logs.
Retrieve Activity LogTool to retrieve a single activity log entry by id.
Retrieve Config Log EntryTool to retrieve a specific config log entry.
Config Logs ListTool to list config change logs for a specific config.
Config Logs RollbackTool to rollback a config to a selected log version.
Clone ConfigTool to clone a branch config including all its secrets.
Create Branch ConfigTool to create a branch config.
Configs DeleteTool to delete a config permanently.
Get Config DetailsTool to fetch a config's details.
Lock ConfigTool to lock a config.
Unlock ConfigTool to unlock a config.
Update ConfigTool to modify an existing config.
Revoke Dynamic Secret LeaseTool to revoke a dynamic secret lease.
Create EnvironmentTool to create a new environment.
Environments DeleteTool to delete an environment.
Get Environment DetailsTool to retrieve an environment.
List EnvironmentsTool to list environments in a Doppler project.
Rename EnvironmentTool to rename an environment.
Remove Group MemberTool to remove a member from a group.
Integrations ListTool to list all external integrations.
Invites ListTool to list open workplace invites.
Remove Project MemberTool to remove a member from a project.
Get Project MemberTool to retrieve a project member by type and slug.
Project Permissions ListTool to list project-level permissions.
Get Project RoleTool to retrieve a project role.
Create ProjectTool to create a project.
Projects DeleteTool to delete a project permanently.
List ProjectsTool to list Doppler projects.
Update SecretsTool to update secrets in a config.

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 OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Doppler secretops project
  • Some knowledge of Python or Typescript

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Doppler secretops.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Doppler secretops Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["doppler_secretops"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only doppler_secretops.
  • The router checks the user's Doppler secretops connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Doppler secretops.
  • This approach keeps things lightweight and lets the agent request Doppler secretops tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Doppler secretops. "
        "Help users perform Doppler secretops operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Doppler secretops and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Doppler secretops operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

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

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Doppler secretops.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Doppler secretops and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["doppler_secretops"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Doppler secretops. "
        "Help users perform Doppler secretops operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

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

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Doppler secretops MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Doppler secretops.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Doppler secretops MCP Agent with another framework

FAQ

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

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

Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents 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 Doppler secretops tools.

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

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