How to integrate Doppler MCP with LlamaIndex

Connect LlamaIndex 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 LlamaIndex 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 LlamaIndex 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:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Doppler
  • Connect LlamaIndex to the Doppler MCP server
  • Build a Doppler-powered agent using LlamaIndex
  • Interact with Doppler through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built 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 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 step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Doppler account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Doppler

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Doppler access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called doppler_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["doppler"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Doppler actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, doppler)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Doppler tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Doppler
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Doppler tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Doppler
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Doppler, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["doppler"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Doppler actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Doppler to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Doppler tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
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. LlamaIndex 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