X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Doppler MCP with DeepSeek Harness

Connect DeepSeek Harness 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.

Get started for freeGet a demo
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.

26 Tools

Introduction

DeepSeek Harness (dsh) is an open-source agent runtime from DeepSeek AI, and every part of it is a plugin, so you can swap out the model adapter, the tool registry, or the agent loop. It runs on the Cordis framework and comes with a local Web UI, a headless CLI runner, and a Python SDK. You can point it at DeepSeek V4-Pro and V4-Flash, or at Anthropic, OpenAI, and other OpenAI-compatible providers. It is MIT licensed and still in developer preview.

This guide shows how to connect your Doppler account to DeepSeek Harness, and you can do it with either the Composio Connect CLI or the Composio Connect MCP. The dsh-base bundle gives shell execution as a first-class tool, so the CLI is the easiest path for personal use. It is quick to set up and needs no server config, and the MCP path works well too, since the harness comes with a built-in MCP client.

Also integrate Doppler with

ChatGPT WorkAntigravityOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexGrok BuildCursorVS CodeOpenCodeOpenClawHermesPiGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

What is Composio Connect?

Composio Connect lets anyone plug 1,000+ applications directly into their agent harness, including DeepSeek Harness, through a single hosted MCP endpoint. Each task runs as a session, a scoped runtime that ties together the user, the available toolkits, authentication, and execution state. It can:

  • Discover and load tools on-demand. A small set of meta tools lets the agent search for the right tool at runtime, so you never load hundreds of tool definitions into context.
  • Chain tools in a sandboxed remote workbench. Multi-step workflows run server-side, passing outputs between tools and working with files in the session's sandbox, so long chains finish without a lot of back-and-forth with the LLM.
  • Manage authentication end-to-end. Managed OAuth, per-user connected accounts, and account isolation are all handled for you, so you never wire up auth yourself.

Connect Doppler to DeepSeek Harness with Composio

Prerequisites: Install DeepSeek Harness

DeepSeek Harness needs Node.js (20 or 22) and pnpm. Build it from source. This is also what the MCP path in Option 2 requires, since the built-in MCP client resolves its dependencies from the checkout:

bash
git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web

The Web UI listens on http://127.0.0.1:3080 by default. Open that address to confirm it is up.

Then configure your model route. In the Web UI, open Settings → Models: the built-in DeepSeek card accepts a DeepSeek API key, and the same page supports Anthropic, OpenAI, and custom OpenAI-compatible endpoints. Full first-run details are in the DeepSeek Harness docs.

Option 1: Composio CLI (recommended)

DeepSeek Harness runs shell commands as a first-class tool through its dsh-base bundle, so the Composio Universal CLI fits well. There is no MCP server to configure, and multi-step tool chaining is reliable. Install and authenticate:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Log in to Composio
composio login

Connect to Doppler

Ask DeepSeek Harness to connect to Doppler, or just request any Doppler-related task. Under the hood the agent calls Composio commands like any other shell tool:

bash
composio search "what can I do with Doppler?"
composio link doppler

On the first Doppler call, composio link doppler opens an OAuth prompt so you can authorize access. After that, every Doppler command works with your stored credentials automatically, so you just talk to the agent and it will search, execute, and chain Doppler tools as needed.

Option 2: Composio MCP

DeepSeek Harness bridges MCP through its built-in @deepseek-ai/dsh-mcp-client plugin. You register one server as a plugin row, and its tools appear under server-qualified names (mcp__<serverName>__<rawName>), the same shape Claude Code and Codex use.

MCP requires the source build. The built-in client depends on the harness's own internal packages (cordis, dsh-llm, dsh-tools, dsh-invariants, dsh-subprocess), which resolve from the git checkout you built in the prerequisites. Run everything below from that checkout with pnpm dsh. For a route that avoids editing config files, see the community plugin at the end of this section.

Auth note: The built-in client passes static headers only and has no OAuth flow, so authenticate to Composio Connect with the x-consumer-api-key header. For Composio's OAuth flow, use the community plugin below.

1. Register the Composio server

The web profile's user patch layer is $DSH_HOME/profiles/web/cordis.patch.yml ($DSH_HOME defaults to ~/.dsh). This is a patch file, so a new plugin goes under an insert: entry. A bare - id: row instead targets an existing entry and fails to boot with patch: entry "…" not found. Add:

bash
- insert:
    - id: mcp-composio
      name: '@deepseek-ai/dsh-mcp-client'
      config:
        serverName: composio
        transport: streamable-http
        url: https://connect.composio.dev/mcp
        headers:
          x-consumer-api-key: !!js process.env.COMPOSIO_API_KEY

2. Set the API key and launch

The header value must resolve to a string at load time. Export your Composio consumer API key (ck_...), which is on the Connect → Settings → Sessions page of the Composio dashboard, in the shell you launch from. If it is unset, process.env.COMPOSIO_API_KEY is undefined and the config fails validation:

bash
export COMPOSIO_API_KEY=ck_your_key
pnpm dsh web

3. Done!

Open http://127.0.0.1:3080 and start a session on Standard or Code mode. (Minimal mode exposes only bash and str_replace_editor, so it hides MCP tools.) Composio's tools register as mcp__composio__*. Ask DeepSeek Harness to connect to Doppler or request any Doppler-related task, and Composio authorizes Doppler on demand on the first call.

The dsh-mcp-client config schema (transport, serverName, url, headers, plus reconnect.* and toolCallTimeoutMs) is the current developer-preview interface and may change between releases.

Alternative: OAuth via the community plugin

To use Composio Connect's OAuth flow instead of a static key, or to skip editing cordis.patch.yml by hand, use the community dsh-mcp-manager plugin. It installs as a self-contained external plugin, ships a bundle patch so it auto-mounts, and adds a Settings → MCP page plus OAuth (authorization code + PKCE, RFC 7591 dynamic client registration, and refresh-token rotation). It needs the web profile and Node.js ^22.19 or >=24, with pnpm on your PATH.

Install it from your source checkout, then restart pnpm dsh web and refresh:

bash
pnpm dsh plugin --profile web add github:hyqhyq3/dsh-mcp-manager

Open Settings → MCP → ＋ Add MCP server, choose HTTP, set the name to composio, the URL to https://connect.composio.dev/mcp, and the auth mode to OAuth. Click Authenticate, and Composio's login and consent screen opens in the browser, then redirects back and registers the tools as mcp__composio__*. The row should read connected (N tools).

The plugin catches the OAuth code on a loopback redirect (http://127.0.0.1:<port>/mcp-manager/callback/<id>), so Composio's OAuth provider must allow that loopback URL. Server configs and tokens persist at ~/.dsh/mcp-manager.json, so treat that file as a secret. Being a community plugin on a preview harness, its commands may change, so check the plugin repo if a step drifts.

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.

Way Forward

With Doppler connected, DeepSeek Harness can now act on your behalf whenever you ask it to.

From here, you can extend the harness further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup, and each new integration adds to what your agent can do for you.
  • Build workflows across tools: Once multiple apps are connected, DeepSeek Harness can chain actions together, so it can turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Use the plugin system: Wrap common Doppler flows as dsh plugins or prompt templates so recurring tasks become one-line commands, and bundle your most-used Doppler tools into a named profile you can boot on demand.

If you run into trouble or want to share what you've built, join the community or check out the Docs for more configuration options.

TOOLS

Supported Tools

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

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.

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.

Create Encrypted Share Link

Tool to generate a Doppler Share link by sending an encrypted secret.

Create Plain Text Share Link

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

List Environments

Tool to list all environments in a Doppler project.

List Integrations

Tool to retrieve all existing integrations in Doppler.

List Change Requests

Tool to list existing change requests in the Doppler workplace.

Get Project Role

Tool to retrieve details of a specific project role in Doppler.

List Project Roles

Tool to list all available project roles in Doppler.

List Project Role Permissions

Tool to list all available permissions for project roles in Doppler.

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.

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

Tool to retrieve all available workplace permissions in Doppler.

FRAMEWORKS

How to build Doppler MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use Doppler MCP with ChatGPT Work

Antigravity logo

Antigravity

Use Doppler MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Doppler MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Doppler MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Doppler MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Doppler MCP with Claude Cowork

Codex logo

Codex

Use Doppler MCP with Codex

Grok Build logo

Grok Build

Use Doppler MCP with Grok Build

Cursor logo

Cursor

Use Doppler MCP with Cursor

VS Code logo

VS Code

Use Doppler MCP with VS Code

OpenCode logo

OpenCode

Use Doppler MCP with OpenCode

OpenClaw logo

OpenClaw

Use Doppler MCP with OpenClaw

Hermes logo

Hermes

Use Doppler MCP with Hermes

Pi logo

Pi

Use Doppler MCP with Pi

Google ADK logo

Google ADK

Use Doppler MCP with Google ADK

LangChain logo

LangChain

Use Doppler MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Doppler MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Doppler MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Doppler MCP with LlamaIndex

CrewAI logo

CrewAI

Use Doppler MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Doppler MCP with Pydantic AI

AutoGen logo

AutoGen

Use Doppler MCP with AutoGen

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. DeepSeek Harness 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