ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Doppler with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Manage secrets and environment variables via Doppler. list projects, audit secrets, and track activity logs from any AI agent.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 12 capabilities

The complete Doppler capability set.

These are the exact actions your AI can choose when you ask it to work with Doppler.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through Doppler.

  1. 01

    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

  2. 02

    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

  3. 03

    Get config

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

  4. 04

    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

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through Doppler.

  1. 05

    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

  2. 06

    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

  3. 07

    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

  4. 08

    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

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through Doppler.

  1. 09

    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

  2. 10

    Get project

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

  3. 11

    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

  4. 12

    List environments

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

Observed, not estimated

869ms average. Fast in production.

Doppler is checked daily against the live service.

Daily averagePeak 1198ms
Aug 20Today
Fastest day
753ms
Slowest day
1198ms
14-day trend
Improving-5%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Doppler, so you can see the experience inside your AI.

It does not authenticate your account with Doppler. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Doppler Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_vo7jrnUQTRhfeTB2n8hMYKtG5HHsAGAZ6dWipPhZ/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Doppler capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "doppler-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_vo7jrnUQTRhfeTB2n8hMYKtG5HHsAGAZ6dWipPhZ/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Doppler owners ask.

  • 01

    How do I create a Doppler Service Token?

    Log in to the Doppler Dashboard, 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.

  • 02

    Can I update multiple secrets at once?

    Yes! Use the change_secrets capability 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.

  • 03

    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.

  • 04

    Can I view the activity history for a project?

    Yes! Use the list_activity_logs capability 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.