How to integrate Doppler MCP with Google ADK

Connect Google ADK to Doppler MCP. Get secrets for staging environment in doppler, add a new secret to marketing project, and more using natural language, with authentication handled for you.

Doppler logoDoppler
Api Key

Doppler is a secrets management platform for organizing and syncing environment variables. It lets teams securely centralize, share, and update secrets across infrastructure.

62 Tools

Introduction

This guide walks you through connecting Doppler to Google ADK 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 Google ADK 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.

Also integrate Doppler with

TL;DR

Here's what you'll learn:
  • Get a Doppler account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Doppler
  • Build an agent that connects to Doppler through MCP
  • Interact with Doppler using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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 to your projects, environments, configs, secrets, service tokens, users, and webhooks, so your agent can inspect projects, review configurations, retrieve and update secrets, create service tokens, and audit workspace resources on your behalf.

  • Project and environment discovery: Have your agent list Doppler projects, inspect project details, and review the environments available within each project.
  • Configuration review: Let the agent list configurations for a project and retrieve a specific config when you need to check how an environment is organized.
  • Secret retrieval and updates: Direct your agent to list secret names, retrieve a specific secret, download configured secrets, or update secrets within a chosen config.
  • Service token management: Instruct your agent to create a service token for a config or list its existing service tokens for review.
  • Workspace and webhook auditing: Have your agent identify the authenticated user, list workplace users, and review webhooks configured for a project.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Doppler via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["doppler"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Doppler operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Doppler and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["doppler"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Doppler operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Doppler with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Doppler using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Doppler tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

TOOLS

Supported Tools

Every Doppler action and event your agent gets out of the box.

List Activity Logs

List workplace activity logs with pagination support.

Get Activity Log

Retrieve detailed information about a specific activity log entry.

Add Webhook

Tool to create a new webhook for a Doppler project.

Get Authenticated User Info

Tool to retrieve information about the authenticated user or token.

Get Config Log

Tool to retrieve a specific config log from Doppler.

List Config Logs

Tool to retrieve configuration change logs for a specific config in a project.

Rollback Config Log

Tool to rollback a config to a selected log version.

Clone Config

Tool to clone a branch config including all its secrets.

Create Config

Tool to create a branch config.

Delete Config

Tool to delete a config permanently.

Get Config

Tool to retrieve a specific Doppler config by project and config name.

List Doppler Configs

Tool to list configurations from a Doppler project.

Lock Config

Lock a Doppler config to prevent it from being renamed or deleted.

Unlock Config

Tool to unlock a config.

Update Config

Rename an existing Doppler config within a project.

Create Encrypted Share Link

Create a Doppler Share link for an end-to-end encrypted secret.

Create Plain Text Share Link

Tool to generate a Doppler Share link by sending a plain text secret.

Create Service Token

Tool to create a new service token for a Doppler config.

Delete Service Token

Tool to delete an existing service token from a Doppler config.

Delete Webhook

Tool to delete an existing webhook.

Disable Webhook

Tool to disable an existing Doppler webhook.

Revoke Dynamic Secret Lease

Revoke a dynamic secret lease immediately before its TTL expires.

Enable Webhook

Tool to enable a previously disabled webhook.

Create Environment

Create a new environment in a Doppler project.

Delete Environment

Tool to delete an environment.

Get Environment

Retrieves detailed metadata for a specific Doppler environment within a project.

List Environments

Tool to list all environments in a Doppler project.

Rename Environment

Rename an environment's display name within a Doppler project.

Get Webhook

Tool to retrieve an existing webhook by its slug.

Get Workplace User

Tool to retrieve a specific workplace user by their workplace_user id.

Remove Group Member

Remove a member from a Doppler group.

List Integrations

Tool to retrieve all existing integrations in Doppler.

List Invites

Tool to list open workplace invites.

List Change Requests

List existing change requests in the Doppler workplace.

List Project Members

Tool to list all members of a Doppler project including users, groups, service accounts, and invites.

List Service Tokens

Tool to list all service tokens for a specific Doppler config.

List Workplace Users

Tool to list all users in the Doppler workplace.

List Webhooks

Tool to list all webhooks configured for a Doppler project.

Remove Project Member

Tool to remove a member from a project.

Get Project Member

Retrieve a specific project member's details including their role and environment access permissions.

List Project Permissions

List all available project-level permissions in Doppler.

Get Project Role

Retrieve detailed information about a specific project role in Doppler, including its permissions, display name, identifier, creation timestamp, and whether it's a custom or built-in role.

List Project Roles

Tool to list all available project roles in Doppler.

Create Project

Tool to create a project.

Delete Project

Tool to delete a project permanently.

Get Project Details

Tool to retrieve details of a specific Doppler project by its identifier.

List Doppler Projects

Tool to list all Doppler projects in your workspace.

Delete Secret

Tool to delete a secret from a Doppler config.

Download Secrets

Tool to download secrets from a Doppler config in various formats.

Get Secret

Tool to retrieve a specific secret from a Doppler project config.

List Doppler Secrets

Tool to list all secrets for a specific Doppler config within a project.

List Secret Names

Tool to retrieve the list of secret names from a specific Doppler config.

Update Doppler Secrets

Tool to update secrets in a Doppler config.

Update Secret Note

Tool to update a note for a secret in Doppler.

Update Project

Tool to update an existing Doppler project's name or description.

Update Secret Note

DEPRECATED: Use DopplerSecretsUpdateNote instead.

Update Webhook

Tool to update an existing webhook configuration in Doppler.

Update Workplace Settings

Tool to update workplace settings in Doppler.

Get Workplace Information

Tool to retrieve workplace information from Doppler.

Get Workplace Role

Tool to retrieve workplace role information from Doppler.

List Workplace Roles

Tool to list all workplace roles in your Doppler workspace.

List Workplace Permissions

Retrieves all available workplace permissions in Doppler.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Doppler.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Doppler tool your agent needs.Free to start.

Start building