SECRETS MANAGEMENT / Doppler
Doppler MCP Server
Gives an assistant scoped access to the Doppler secrets API, with an explicit read-only flag and project/config narrowing for secret-bearing work.
“MCP (Model Context Protocol) server that provides AI assistants with access to the Doppler API for secrets management.”
01 / THE REASONING
Why this made the selection.
- Publisher-maintained secrets surface with a documented --read-only flag, so exploration can exclude write endpoints by construction.
- Project and config scoping plus service-token auth let a deployment limit the assistant to named environments.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md: login versus service-token auth, --read-only flag and project/config overrides.
- package.json: @dopplerhq/mcp-server identity, doppler-mcp binary and OpenAPI-driven TypeScript build.
- src/index.ts: TypeScript entrypoint at the pinned revision.
- LICENSE: Apache-2.0 terms for the repository source.
Our findings
- Tools are generated from the Doppler OpenAPI spec, so the surface tracks the API rather than a curated subset.
- Authentication state is either an interactive login cache or a DOPPLER_TOKEN environment value.
- Corrected 2026-10-13: the previous configExample combined --read-only with a DOPPLER_TOKEN placeholder the README does not use. It is now the README Read-only mode block, which relies on the login session. The README service-token blocks use the placeholder <your-doppler-token>.
- Available Tools names writing tools including workplace_update, projects_create, projects_delete, environments_create, configs_create, configs_update, configs_lock, configs_unlock, secrets_update and config_logs_rollback. --read-only exposes GET operations only.
- The README says --project and --config are a convenience layer, not a substitute for token scoping, and that the server cannot tell a read-only token from a read-write one, so --read-only is what hides write tools.
- package.json at this commit names @dopplerhq/mcp-server, matching the install command. HEAD on 2026-10-13 equals the pinned commit.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx @dopplerhq/mcp-server login Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Authenticate once with the login command, or mint a config-scoped service token.
- Add the documented stdio configuration with --read-only for exploration, narrowing project and config.
Before you start
- Node.js with npx available.
- A Doppler account with access to the intended projects.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"doppler": {
"command": "npx",
"args": [
"-y",
"@dopplerhq/mcp-server",
"--read-only"
]
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Doppler MCP server readme ↗Checked
https://github.com/DopplerHQ/mcp-server/blob/989b827c0ff9c93cba529549c2bbed50a48a9191/README.md
Supports: summary, install, compatibility, access, transports, configExample, whySelected, bestFor, limitations, upstreamDescription, Named tools and --read-only behaviour, --project and --config are not access control
- Repository licence ↗Checked
https://github.com/DopplerHQ/mcp-server/blob/989b827c0ff9c93cba529549c2bbed50a48a9191/LICENSE
Supports: license
- Package manifest ↗Checked
https://github.com/DopplerHQ/mcp-server/blob/989b827c0ff9c93cba529549c2bbed50a48a9191/package.json
Supports: Package name @dopplerhq/mcp-server, doppler-mcp binary