4,000+ servers built on MCP Fusion
Vinkius
VS Code CopilotIDE
Why use Doppler MCP Server with VS Code Copilot?

Bring Secrets Management
to VS Code Copilot

Create your Vinkius account to connect Doppler to VS Code Copilot and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Change SecretsDelete SecretsGet AccountGet ConfigGet ProjectGet SecretList Activity LogsList ConfigsList EnvironmentsList ProjectsList SecretsList Workspaces
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Doppler

What is the Doppler MCP Server?

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

  1. Subscribe to this server
  2. Enter your Doppler Service Token or Personal Token
  3. 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

Built-in capabilities (12)

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

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_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

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_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_environments

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

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

Why VS Code Copilot?

GitHub Copilot Agent mode brings Doppler data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Doppler in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Doppler with Vinkius?

The Doppler connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full Doppler details →
Doppler
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Doppler using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Doppler and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Doppler to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Doppler for VS Code Copilot

Every request between VS Code Copilot and Doppler is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

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 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.

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 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.

05

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

06

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

07

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

08

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

09

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →