Doppler MCP ServerSAFE

MCP (Model Context Protocol) server that provides AI assistants with access to the Doppler API for secrets management.

[!IMPORTANT] The Doppler MCP Server is experimental and intended for development, testing, and evaluation purposes. Because outputs are non-deterministic and vary with the connected model, query, and server configuration, always use a token scoped only to the actions, projects, and environments you intend to allow, and review agentic output for alignment with your security and compliance requirements.

Quick Start

1. Authenticate:

npx @dopplerhq/mcp-server login

2. Add to your MCP client configuration (e.g., Claude Desktop):

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

With Service Token

Alternatively, use a service token instead of logging in:

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

See Service Tokens to create a config-scoped token.

Commands

login              Authenticate with Doppler (interactive)
logout             Clear cached auth credentials

Options

--read-only        Only expose read operations (GET endpoints)
--project    Override auto-detected project
--config     Override auto-detected config
--verbose, -v      Enable verbose logging to stderr
-h, --help         Show help message

Examples

Read-only mode

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

Restrict to a specific project:

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

*