What it does

Talks to Doppler's secrets API. The useful distinction is metadata versus values: knowing that a service has STRIPE_KEY set is operational information, while reading its value is the thing a vault exists to prevent. Configure it with a service token scoped to one config, not a workplace-wide token.

Install

Terminal

npx -y @dopplerhq/mcp-server

Client configuration

Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.

mcp.json

{
  "mcpServers": {
    "doppler": {
      "command": "npx",
      "args": [
        "-y",
        "@dopplerhq/mcp-server"
      ]
    }
  }
}

Use it for

Inspecting which secrets exist in an environment, never the values

Skip it if

Letting an agent read secret values; that defeats the point of a vault

When to use it

Reach for this when the task needs secrets inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.

Other TypeScript servers

Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude

Doppler MCP