# Doppler

> Inject secrets from Doppler into agent workflows without exposing values in chat.

[Canonical HTML page](https://top-mcps.com/mcp/doppler) · [server.json](https://top-mcps.com/mcp/doppler.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@drbarq/doppler-mcp"
      ],
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export DOPPLER_TOKEN=dp.st.dev.…
claude mcp add doppler -- npx -y @drbarq/doppler-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@drbarq/doppler-mcp"
      ],
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@drbarq/doppler-mcp"
      ],
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@drbarq/doppler-mcp"
      ],
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@drbarq/doppler-mcp"
      ],
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@drbarq/doppler-mcp"
          ],
          "env": {
            "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.doppler]
command = "npx"
args = [
  "-y",
  "@drbarq/doppler-mcp",
]
env = { DOPPLER_TOKEN = "${DOPPLER_TOKEN}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "doppler": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@drbarq/doppler-mcp"
        ]
      },
      "env": {
        "DOPPLER_TOKEN": "${DOPPLER_TOKEN}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Doppler doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Community (drbarq)
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** DOPPLER_TOKEN
- **Supported clients:** Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, Doppler account
- **License:** Apache-2.0
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **Score:** 64/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/drbarq/doppler-mcp

## Security & scope

- **Access scope:** read-only
- **Sandbox:** Doppler service token in env. Scope at the token level: one project + one config per token. Read-only by design.
- **Gotchas:**
  - Service tokens are long-lived. Rotate on the credential-rotation cadence.
  - A wildcard token defeats the per-env model. Prefer one token per environment.
  - Doppler caches secret values in the MCP process briefly; restart the MCP after rotating a secret to clear the cache.

## Quick answer

**What it does.** Resolves Doppler secret references at tool-call time, lists projects and configs, and surfaces per-environment secret metadata without leaking values into the model context.

**Best for:**
- Reference-only secret injection
- Per-environment agent workflows
- Audit-logged secret use
- Multi-config switching during testing
- Rotating secrets without touching client config

**Not for:**
- Teams without Doppler
- Single-user, single-secret workflows

## Description

The official Doppler MCP lets an AI agent reference secrets stored in Doppler projects and environments without the values appearing in the conversation. Doppler's strength is the per-environment workflow (dev / staging / prod with different secrets); the MCP inherits that — the agent works against the environment its token is scoped to.

## Why it matters

Doppler is the most-used cloud secret manager for small and mid-market teams. An MCP wrapper turns "copy the secret out of Doppler into env" into a runtime reference.

## Key features

- Service-token auth
- Per-environment scoping
- doppler:// reference resolution
- Project + config enumeration
- Audit-trail visibility on the Doppler side

## FAQ

### Service token vs personal token?

Service tokens. Scope per project + config (environment) so a leaked agent token only exposes the smallest possible blast radius.

### Does the model see secret values?

No. References resolve at the MCP layer; cleartext goes only to the downstream tool call, never into the conversation history.

### Can the agent switch environments?

Only between configs the service token has access to. Best practice: one service token per environment — do not give an agent a token that can read prod secrets when staging is enough.

### Audit logs?

Yes — every secret access shows up in Doppler's audit log keyed by service token. Review periodically to spot drift.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-05-02** — Initial directory listing.