Doppler MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doppler_secrets_getC | Get a secret value from Doppler |
| doppler_secrets_listC | List all secrets in a Doppler config |
| doppler_secrets_setC | Set a secret value in Doppler |
| doppler_secrets_deleteC | Delete a secret from Doppler |
| doppler_projects_listA | List all Doppler projects |
| doppler_projects_createC | Create a new Doppler project |
| doppler_configs_listC | List all configs in a Doppler project |
| doppler_configs_createC | Create a new config in a Doppler project |
| doppler_environments_listC | List all environments in a Doppler project |
| doppler_runB | Run a command with Doppler secrets injected as environment variables |
| doppler_meB | Get information about the current authenticated Doppler user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity between them. For example, doppler_secrets_get retrieves a single secret value, while doppler_secrets_list enumerates all secrets, and doppler_run is uniquely for executing commands with injected secrets.
All tools follow a consistent doppler_<resource>_<action> naming pattern using snake_case throughout. This predictable structure makes it easy to understand each tool's function at a glance, such as doppler_configs_create and doppler_secrets_delete.
With 11 tools, the server is well-scoped for managing Doppler projects, configs, environments, and secrets. Each tool earns its place by covering essential CRUD operations and specific workflows like doppler_run, avoiding both bloat and gaps.
The toolset provides strong coverage for core Doppler operations, including project, config, environment, and secret management with create/list/get/set/delete actions. A minor gap exists in missing update operations for configs or projects, but agents can work around this by recreating resources as needed.