# Doppler MCP for AI Agents AI Agent Connect > Doppler MCP lets you manage secrets and environment variables through your AI agent. It handles project listing, config auditing, and secret updates without you having to flip through the Doppler dashboard. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_vo7jrnUQTRhfeTB2n8hMYKtG5HHsAGAZ6dWipPhZ/ai-agent-connect - **Tags:** secrets-management, environment-variables, doppler, api-keys, config-management ## Description The Doppler MCP connects your secrets management account to your AI agent so you can handle sensitive details using plain English. Instead of hunting for a specific production key in a web UI, you can just ask your agent to find it for you. You can manage different environments like staging or production, check who last touched a secret, or update multiple keys at once. If you're looking for a way to handle infrastructure secrets without constant context switching, this is the way to go. It's one of the many tools you can find in the Vinkius catalog to make your development workflow actually feel faster. You get to treat your AI agent like a dedicated secrets engineer that knows your project structure inside out. ## Tools ### get_config Get specific details about a Doppler config, including its name and locked status. This helps you verify your deployment environment settings. ### get_account Check your current account details and token permissions. Use this to ensure your connection is active and properly scoped. ### change_secrets Add or update multiple secrets in a config using a JSON mapping. This makes rotating keys much faster than doing them one by one. ### delete_secrets Remove specific secrets from a config when they are no longer needed. This helps keep your environment clean and secure. ### get_project Pull specific information about a project using its slug. It's a quick way to see project-level metadata. ### get_secret Retrieve a specific secret value along with any parent environment fallbacks. This ensures you get the correct resolved value. ### list_activity_logs View a history of who performed what action and when for security auditing. It's perfect for compliance checks. ### list_configs See all deployment environments like development or production for a specific project. This gives you a full view of your configs. ### list_environments Browse the different environment types available in your Doppler account. Use this to understand your available deployment tiers. ### list_projects Get a list of all projects, including their descriptions and creation dates. This helps you navigate large organizations. ### list_secrets See all secret names and their resolved values for a specific config. This provides a complete overview of your environment keys. ### list_workspaces View all organizational workspaces in your Doppler account. It's the fastest way to see your top-level structure. ## Prompt Examples **Prompt:** ``` What keys do I have in my staging environment? ``` **Response:** ``` I found the following secrets for your **staging** config: | Secret Name | Resolved Value | Visibility | | :--- | :--- | :--- | | `DATABASE_URL` | `postgres://user:pass@host:5432/db` | Private | | `REDIS_URL` | `redis://default:6379` | Public | | `STRIPE_KEY` | `sk_test_4eC3...` | Private | Would you like me to update any of these? ``` **Prompt:** ``` Who changed the production API key last week? ``` **Response:** ``` I found 3 relevant activity events in the last 7 days for the **production** config: * **User:** alice@company.com * **Action:** Updated `API_KEY` * **Time:** 2026-07-03 14:22:01 * **User:** bob@company.com * **Action:** Read `API_KEY` * **Time:** 2026-07-05 09:10:45 * **User:** admin@company.com * **Action:** Updated `STRIPE_KEY` * **Time:** 2026-07-08 11:00:00 ``` **Prompt:** ``` Update the STRIPE_KEY in prod to the new one. ``` **Response:** ``` Done! I've updated the `STRIPE_KEY` in the **production** config of your backend-api project. The new value has been applied and will be available to all services using this environment. ``` ## Capabilities ### List projects and workspaces See your entire organizational structure and all associated projects in one go. ### View environment configs Check your development, staging, and production settings instantly. ### Audit secret values Get resolved secret values and see how they inherit from parent environments. ### Update or delete secrets Modify secret values or remove old keys using natural language commands. ### Review activity logs Track who performed what action and when for security and compliance audits. ## Use Cases ### Checking a production key A developer needs a DB URL for a hotfix. They ask the agent to get the secret from the prod config to avoid a manual dashboard login. ### Auditing a breach A security pro wants to know who accessed a key. They ask the agent to list activity logs for the last 24 hours to identify the user. ### Updating keys A team rotates API keys. They give the agent a list of new keys to update via change_secrets to ensure all services are synced. ### Project Discovery A new hire wants to see what projects exist. They ask the agent to list projects across all workspaces to understand the tech stack. ## Benefits - Stop switching tabs by using list_secrets to see all keys in one view without leaving your editor. - Keep environments clean by using change_secrets to update multiple values at once during a rotation. - Maintain compliance by using list_activity_logs to see exactly who changed what and when. - Verify setups quickly with get_config to check if a config is locked or a root environment. - Simplify onboarding by using list_workspaces to see the full organizational structure of your team. ## How It Works The bottom line is you get a conversational interface for managing your entire secrets infrastructure. 1. Subscribe to the Doppler MCP on Vinkius. 2. Enter your Doppler Service Token or Personal Token. 3. Ask your AI client to list projects or update secrets. ## Frequently Asked Questions **Can I use the Doppler MCP to see my production secrets?** Yes, the Connector can retrieve resolved secret values for any config. This allows your AI agent to show you the actual keys you need for your production environment. **How does the Doppler MCP help with security?** It makes auditing much faster. You can ask your agent to pull activity logs to see exactly who modified which secrets, providing a clear audit trail without manual log searching. **Can I update multiple secrets at once with the Doppler MCP?** Yes, you can provide a list of keys and values to your AI agent. It will use the change_secrets tool to update all of them in a single operation. **Is my Doppler token safe to use with this Connector?** The Connector uses the token you provide to interact with your account on your behalf. It is handled securely within the Connector framework and is not shared with other services. **Does the Doppler MCP work with Cursor or VS Code?** Yes, it works with any MCP-compatible client, including Cursor, Windsurf, and Claude. You just need to connect it through the Vinkius catalog. **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.