# Doppler — MCP server on mcp.ai
> Connect your Doppler account and use 62 tools for developer tools straight from your AI agent. Connect with your own API key. Doppler is a secrets management platform that helps developers organize and sync environment variables across teams and infrastructure.

By: mcp.ai · official
Page: https://mcp.ai/doppler

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_doppler?ms=1787293560000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/doppler/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/doppler/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/doppler/skill.md
Postman collection (v2.1): https://mcp.ai/doppler/postman.json

## Tools
- doppler_activity_logs_list(page?: integer, per_page?: integer) — List workplace activity logs with pagination support. Retrieves a paginated list of activity logs showing actions performed by users and bots in your Doppler workplace, such as creating projects, modi
- doppler_activity_logs_retrieve(id: string) — Retrieve detailed information about a specific activity log entry. Activity logs track all actions performed in the Doppler workplace including project creation, secret modifications, user actions, et
- doppler_add_webhook(url: string, secret?: string, payload?: string, project?: string, authentication?: object, enable_configs?: string[]) — Tool to create a new webhook for a Doppler project. Use when you need to configure webhook notifications for secret changes or other events in a project. The webhook URL must use HTTPS. Optionally con
- doppler_auth_me() — Tool to retrieve information about the authenticated user or token. Use when you need to verify authentication status or get details about the current token's workplace and permissions.
- doppler_config_logs_get(log: string, config: string, project: string) — Tool to retrieve a specific config log from Doppler. Use when you need to view details about a particular configuration change or event.
- doppler_config_logs_list(page?: integer, config: string, project: string, per_page?: integer) — Tool to retrieve configuration change logs for a specific config in a project. Use when you need to view the history of configuration changes, track who made changes, or identify rollback actions.
- doppler_config_logs_rollback(log: string, config: string, project: string) — Tool to rollback a config to a selected log version. Use when needing to undo a specific change by its log ID, after confirming project, config, and log ID.
- doppler_configs_clone(name: string, config: string, project: string) — Tool to clone a branch config including all its secrets. Use after confirming the source config details.
- doppler_configs_create(name: string, project: string, environment: string) — Tool to create a branch config. Use when you need to programmatically establish a new branch-based configuration for a specified project and environment. The config name MUST start with the environmen
- doppler_configs_delete(config: string, project: string) — Tool to delete a config permanently. Use when you need to remove a config that is no longer needed.
- doppler_configs_get(config: string, project: string) — Tool to retrieve a specific Doppler config by project and config name. Use when you need to get configuration details for a specific project environment.
- doppler_configs_list(page?: integer, project: string, per_page?: integer, environment?: string) — Tool to list configurations from a Doppler project. Use when you need to retrieve all configs or filter by environment. Supports pagination for large result sets.
- doppler_configs_lock(config: string, project: string) — Lock a Doppler config to prevent it from being renamed or deleted. Locking provides protection against accidental modifications to critical configurations. Use this after confirming the correct projec
- doppler_configs_unlock(config: string, project: string) — Tool to unlock a config. Use when you need to allow renaming or deletion of a previously locked config.
- doppler_configs_update(name: string, config: string, project: string) — Rename an existing Doppler config within a project. This action modifies the config's name while preserving all secrets and settings. Before using this action: 1. Use DOPPLER_PROJECTS_LIST to get the 
- doppler_create_encrypted(expire_days?: integer, expire_views?: integer, encryption_kdf: string, hashed_password: string, encrypted_secret: string, encryption_salt_rounds: integer) — Create a Doppler Share link for an end-to-end encrypted secret. This tool generates a secure, shareable link where the secret is encrypted client-side and decrypted in the recipient's browser, ensurin
- doppler_create_plain(secret: string, expire_days?: integer, expire_views?: integer) — Tool to generate a Doppler Share link by sending a plain text secret. Use when you need to securely share secrets with expiration controls. The secret is not stored in plain text by Doppler; the recei
- doppler_create_service_token(name: string, access?: string, config: string, project: string, expire_at?: string) — Tool to create a new service token for a Doppler config. Use when you need to generate API credentials for services to access secrets programmatically. The token grants either read-only or read/write 
- doppler_delete_service_token(slug?: string, token?: string, config: string, project: string) — Tool to delete an existing service token from a Doppler config. Use when you need to revoke or remove a service token that is no longer needed.
- doppler_delete_webhook(slug: string, project?: string) — Tool to delete an existing webhook. Use when you need to permanently remove a webhook from a project.
- doppler_disable_webhook(slug: string, project?: string) — Tool to disable an existing Doppler webhook. Use when you need to temporarily stop a webhook from receiving notifications without deleting it.
- doppler_dynamic_secrets_revoke_lease(lease: string, config: string, project?: string, dynamic_secret: string) — Revoke a dynamic secret lease immediately before its TTL expires. Use this tool when you need to terminate access to a dynamic secret (e.g., AWS IAM user, database credentials) by invalidating its act
- doppler_enable_webhook(slug: string, project?: string) — Tool to enable a previously disabled webhook. Use when you need to reactivate a webhook that was temporarily disabled.
- doppler_environments_create(name: string, slug: string, project: string) — Create a new environment in a Doppler project. Environments (like dev, staging, prod) organize different configurations within a project. Use this when you need to set up a new deployment environment 
- doppler_environments_delete(project: string, environment: string) — Tool to delete an environment. Use when you need to remove an environment from a project after confirming it's no longer in use.
- doppler_environments_get(project: string, environment: string) — Retrieves detailed metadata for a specific Doppler environment within a project. Use this to get information about an environment including its name, creation date, first fetch timestamp, and personal
- doppler_environments_list(project: string) — Tool to list all environments in a Doppler project. Use when you need to retrieve the environments available in a specific project.
- doppler_environments_rename(name: string, project: string, environment: string) — Rename an environment's display name within a Doppler project. This updates only the human-readable name; the environment slug remains unchanged. Use this when you need to update how an environment ap
- doppler_get_webhook(slug: string, project: string) — Tool to retrieve an existing webhook by its slug. Use when you need to get webhook details including URL, authentication settings, enabled status, and payload configuration.
- doppler_get_workplace_user(slug: string) — Tool to retrieve a specific workplace user by their workplace_user id. Use when you need to get detailed information about a workplace user including their access level, creation date, and nested user
- doppler_groups_delete_member(slug: string, type: string, member_slug: string) — Remove a member from a Doppler group. This permanently removes the specified member (workplace_user, group, invite, or service_account) from the group. Requires valid group and member slugs. Returns 2
- doppler_integrations_list() — Tool to retrieve all existing integrations in Doppler. Use when you need to list all configured integrations.
- doppler_invites_list() — Tool to list open workplace invites. Use when you need to retrieve all pending invitations for the current Doppler workplace after authenticating.
- doppler_list_change_requests(page?: integer, per_page?: integer) — List existing change requests in the Doppler workplace. Use this tool to retrieve all change requests and view their current status. Change requests are a workflow-driven mechanism for proposing addit
- doppler_list_project_members(page?: integer, project: string, per_page?: integer) — Tool to list all members of a Doppler project including users, groups, service accounts, and invites. Use when you need to retrieve all members with their roles and environment access permissions for 
- doppler_list_service_tokens(config: string, project: string) — Tool to list all service tokens for a specific Doppler config. Use when you need to view existing API credentials and their access levels.
- doppler_list_users(page?: integer, email?: string) — Tool to list all users in the Doppler workplace. Use when you need to retrieve user information, check user access levels, or filter users by email address.
- doppler_list_webhooks(project: string) — Tool to list all webhooks configured for a Doppler project. Use when you need to retrieve all webhooks or check webhook configurations for a specific project.
- doppler_project_members_delete(slug: string, type: string, project: string) — Tool to remove a member from a project. Use after confirming project slug, member type, and slug.
- doppler_project_members_get(slug: string, type: string, project: string) — Retrieve a specific project member's details including their role and environment access permissions. Use this when you need to check a specific user's, group's, service account's, or invite's members
- doppler_project_permissions_list() — List all available project-level permissions in Doppler. Returns permission identifiers (slugs) that can be assigned to project roles when creating or updating custom roles. Use this to discover what 
- doppler_project_roles_get(role: string) — Retrieve detailed information about a specific project role in Doppler, including its permissions, display name, identifier, creation timestamp, and whether it's a custom or built-in role. Use this to
- doppler_project_roles_list() — Tool to list all available project roles in Doppler. Use when you need to retrieve all roles for permission management or to see what roles are available.
- doppler_projects_create(name: string, description?: string) — Tool to create a project. Use when you need to programmatically initialize a new Doppler project after authentication.
- doppler_projects_delete(project: string) — Tool to delete a project permanently. Use after confirming irreversible removal.
- doppler_projects_get(project: string) — Tool to retrieve details of a specific Doppler project by its identifier. Use when you need to get project metadata including ID, slug, name, description, and creation timestamp.
- doppler_projects_list(page?: integer, per_page?: integer) — Tool to list all Doppler projects in your workspace. Use when you need to retrieve available projects for configuration management or to get project details.
- doppler_secrets_delete(name: string, config: string, project: string) — Tool to delete a secret from a Doppler config. Use when you need to permanently remove a secret from a specific project and config.
- doppler_secrets_download(config?: string, format?: string, project?: string, secrets?: string, name_transformer?: string, dynamic_secrets_ttl_sec?: integer, include_dynamic_secrets?: boolean) — Tool to download secrets from a Doppler config in various formats. Use when you need to retrieve all secrets or a subset of secrets from a specific project and config. Supports multiple output formats
- doppler_secrets_get(name: string, config: string, project: string) — Tool to retrieve a specific secret from a Doppler project config. Use when you need to get the value of a specific secret including its raw and computed values.
- doppler_secrets_list(config: string, project: string, dynamic_secrets_ttl_sec?: integer, include_dynamic_secrets?: boolean, include_managed_secrets?: boolean) — Tool to list all secrets for a specific Doppler config within a project. Use when you need to retrieve secret values and metadata. Returns both raw and computed values for each secret, along with visi
- doppler_secrets_names(config: string, project: string, include_dynamic_secrets?: boolean, include_managed_secrets?: boolean) — Tool to retrieve the list of secret names from a specific Doppler config. Use when you need to list available secret names without their values.
- doppler_secrets_update(config: string, project: string, secrets?: object) — Tool to update secrets in a Doppler config. Use when you need to create or update secret values in a specific project and config.
- doppler_secrets_update_note(note: string, config: string, secret: string, project: string) — Tool to update a note for a secret in Doppler. Use when you need to add or modify documentation for a specific secret. Notes are stored at the project level and apply across all environments, though a
- doppler_update_project(name: string, project: string, description?: string) — Tool to update an existing Doppler project's name or description. Use when you need to rename a project or modify its description after it has been created.
- doppler_update_secret_note(note: string, config: string, secret: string, project: string) — DEPRECATED: Use DopplerSecretsUpdateNote instead. Tool to set or update a note for a secret in Doppler. Use when you need to add or modify documentation for a specific secret. Notes are stored at the 
- doppler_update_webhook(url?: string, slug: string, secret?: string, payload?: string, project?: string, enableConfigs?: string[], authentication?: object, disableConfigs?: string[]) — Tool to update an existing webhook configuration in Doppler. Use when you need to modify webhook URL, authentication, enabled configs, or other webhook settings.
- doppler_update_workplace(name?: string, billing_email?: string, security_email?: string) — Tool to update workplace settings in Doppler. Use when you need to modify workplace name, billing email, or security email. At least one field must be provided to update.
- doppler_workplace_get() — Tool to retrieve workplace information from Doppler. Use when you need to get workplace details including ID, name, billing email, and security email.
- doppler_workplace_roles_get(role: string) — Tool to retrieve workplace role information from Doppler. Use when you need to get details about a specific role including its permissions and metadata.
- doppler_workplace_roles_list() — Tool to list all workplace roles in your Doppler workspace. Use when you need to retrieve available workplace roles for user management or permission configuration.
- doppler_workplace_roles_list_permissions() — Retrieves all available workplace permissions in Doppler. This action returns a comprehensive list of permission identifiers that can be assigned to workplace roles. Workplace permissions control acce

## Example prompts
- "What can I do in Doppler?"
- "Show me a summary of my Doppler account"

## Links
Docs: https://mcp.ai/docs/mcps/doppler
Website: https://mcp.ai/mcps/doppler