Doppler MCP integration for AI agents.
Connect AI agents to Doppler through 44 structured actions, including download secrets, create change request, delete config, and clone config. Review authen…
- ACTION CONTRACTS
- 44
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Doppler integration exposes
The Doppler Agent App exposes 44 provider-backed actions for developer tools and security work. Its current contract lets an authorized agent download doppler secrets, create a doppler change request, and delete a doppler config. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Doppler account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Doppler capabilities.
Showing 12 of 44 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
download_secretsREADDownload Doppler secrets.
create_change_requestWRITECreate a Doppler change request.
delete_configHIGH IMPACTDelete a Doppler config.
clone_configREVIEWClone a Doppler config.
create_configWRITECreate a Doppler config.
create_environmentWRITECreate a Doppler environment.
create_projectWRITECreate a Doppler project.
create_service_tokenWRITECreate a Doppler service token.
create_syncWRITECreate a Doppler sync.
delete_environmentHIGH IMPACTDelete a Doppler environment.
delete_projectHIGH IMPACTDelete a Doppler project.
delete_secretHIGH IMPACTDelete a Doppler secret.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Download Secrets
Download Doppler secrets. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
download_secretsControl Create Change Request
Create a Doppler change request. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_change_requestVerify with Create Change Request
Create a Doppler change request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_change_requestSAFETY BOUNDARY
Operate Doppler with explicit limits
- Authorize Doppler with API key and grant only the provider access required by the selected actions.
- 21 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_config`, `delete_environment`, and `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Doppler rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Doppler task completed successfully.
CONNECTION MODEL
API key
Doppler API token used with the Authorization Bearer header. For automation, create a service token from Doppler's Access tab as documented at https://docs.doppler.com/docs/service-tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 20
- WRITE SIGNALS
- 14
- HIGH IMPACT
- 7
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Doppler.