How do I create a Doppler Service Token?

Log in to the [**Doppler Dashboard**](https://dashboard.doppler.com), select your project, go to **Settings** > **Tokens** and click **Generate Token**. Choose the scope (project + config/environment), set the access level (Read or Read+Write) and copy the token immediately — it won't be shown again.

Can I update multiple secrets at once?

Yes! Use the `change_secrets` tool with a JSON object mapping names to values, e.g. `{"DATABASE_URL":"postgres://new-host","API_KEY":"sk-new"}`. This creates or updates all specified secrets in a single atomic operation.

What is the difference between a Personal Token and a Service Token?

A **Personal Token** is scoped to your user account and can access all workspaces and projects you have permission for. A **Service Token** is scoped to a specific project and config, with either read-only or read+write access. Service tokens are recommended for CI/CD and automated integrations, while personal tokens are better for development and admin tasks.

Can I view the activity history for a project?

Yes! Use the `list_activity_logs` tool with the project_slug to see all audit events (secret reads, writes, config changes, user additions). Optionally filter by config_name to see activity for a specific environment only. Each log entry shows who performed the action, when, and what was affected.

Doppler MCP Connector for Claude

A+

Manage secrets and environment variables via Doppler — list projects, audit secrets, and track activity logs from any AI agent.

12 tools Official Updated Oct 1, 2026 Official Vinkius Partner

More Details Connect to Claude

Connect your Doppler account to any AI agent and take full control of your secrets management through natural conversation.

What you can do

Workspace & Project Discovery — List all workspaces and projects with their names, slugs and descriptions
Config (Environment) Management — View all configs (development, staging, production) per project and their metadata
Secret Auditing — List all secret names and computed values for any config, with environment fallback resolution
Secret Operations — Add, update and delete secrets in any environment with atomic change requests
Activity Logging — Review the full audit log of secret reads, writes, config changes and user activity per project

How it works

Subscribe to this server
Enter your Doppler Service Token or Personal Token
Start managing your secrets from Claude, Cursor, or any MCP-compatible client

No more clicking through the Doppler dashboard to check a secret value or audit who changed DATABASE_URL. Your AI acts as a dedicated secrets engineer.

Who is this for?

Developers — quickly look up secret values for any environment, verify config setups and audit secret inheritance without opening the Doppler UI
DevOps Engineers — review activity logs, audit secret changes and verify project/environment structure for compliance
Security Teams — track who modified which secrets, when and in which environment, enabling full audit trail review via conversation

secrets-managementenvironment-variablesdopplerapi-keysconfig-management

12 tools expose this connector's capabilities to your AI agent.

change_secrets

Provide project_slug, config_name and a JSON object mapping secret names to values. For example: {"DATABASE_URL":"postgres://...","API_KEY":"sk-..."}. Existing secrets not included are not modified. Add or update secrets in a Doppler config

get_account

Returns account email, name, and token metadata (type, scope, permissions). Use this to verify your token is working correctly and understand its access level. Get the current Doppler account details

get_config

Returns config name, project, root status, associated environment template, creation date and locked status. Get details for a specific Doppler config

list_activity_logs

Each entry shows who performed what action, when and the affected config. Optionally filter by config_name. Useful for security auditing and compliance. List activity logs for a Doppler project

list_configs

Each config represents a deployment environment (development, staging, production) and contains its own set of secrets. Returns config name, project slug, root status and environment template used. List configs (environments) for a Doppler project

list_projects

Optionally filter by workspace slug. Each project contains configs (environments) and secrets. Returns project name, slug, description, and creation date. List Doppler projects

list_secrets

Returns each secret's name, computed value (with environment fallbacks applied), visibility status. Provide the project_slug and config_name. List all secrets for a Doppler config

list_workspaces

A workspace is the top-level organizational unit in Doppler that groups projects. Returns workspace name, slug and creation date. List all Doppler workspaces

delete_secrets

Provide project_slug, config_name and comma-separated secret names. WARNING: deleted secrets cannot be recovered. If a secret inherits a value from a parent, it reverts to that value. Delete secrets from a Doppler config

get_project

Provide the project slug (e.g. "my-api-project") and optionally the workspace slug. Get details for a specific Doppler project

get_secret

Returns the secret name and its resolved value with fallbacks from parent environments applied. Get a specific secret value from a Doppler config

list_environments

g. development, staging, production, preview). Returns environment name, slug and whether it is the default environment. List Doppler environment types