Doppler MCP Server
Related Servers
Alternatives to Doppler MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables secure secrets management through the Doppler CLI via natural language interactions. Supports managing secrets, projects, configs, and environments across different Doppler workspaces.11MIT

Doppler MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with the Doppler API for secrets management, including listing, retrieving, and updating secrets across projects and configs. Supports both read-only and full access modes with token-based authentication.3,119 npm8Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Code, Cursor, Codex, and Gemini CLI to use API keys without the model seeing them, by listing project and key names, writing approved .env files, running commands with keys injected, storing keys, creating projects, and importing .env files while returning no secret values.AGPL 3.0
- FlicenseNot gradedqualityFmaintenanceEnables Claude Desktop and other MCP clients to manage Todoist tasks, projects, and labels through natural language.3-
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Proton Pass. It wraps the official pass-cli binary and exposes 14 tools so any MCP-compatible AI assistant (Claude Desktop, Claude Code, etc.) can manage your vaults, credentials, and secrets.14-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.19MIT
TDQS
Scored across 11 tools
Tools are largely distinct by resource type (secrets, projects, configs, environments) and action (get, list, set, delete, create). The only minor overlap is doppler_run which touches secrets, but its purpose of injecting into a command is clearly distinct from directly getting secret values.
All tools follow a consistent doppler_<resource>_<action> pattern (e.g., doppler_secrets_get, doppler_projects_list, doppler_configs_create). This is uniform and predictable across all 11 tools.
11 tools is within the ideal 3-15 range and covers the core Doppler surface reasonably. A few related actions appear grouped (e.g., get/list/set/delete for secrets) which is appropriate. Not excessive or too thin for a secrets management server.
Secrets have full CRUD coverage (get, list, set, delete) which is good. However, there are notable gaps: no ability to update/delete configs or projects, no way to list roles/members, and doppler_run is useful but projects/configs lifecycle is incomplete (create exists but no delete or update).