Get started

Doppler SecretOps for AI agents

Doppler SecretOps is Doppler's project and access layer for managing environments, secrets, and team permissions across an organization, used by platform and security teams controlling who can read what. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Doppler SecretOpsSee the 29 actions ↓
Developer toolsAPI keyMCP + RESTdoppler.com
AUDIT LOG · DOPPLER SECRETOPSPOLICY: acme-support
09:41:09 · claude · u_8f2write
doppler_secretops.configs_get
Get Config Details✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
doppler_secretops.configs_delete
Configs Delete✕ blocked · policy: deny
EVERY DOPPLER SECRETOPS CALL, ON THE RECORD
01 · USE CASES

What agents do in Doppler SecretOps.

01

Check a project's role permissions

List permissions on a project role to confirm who can read or write its secrets.

02

Update a secret value

Update a secret in an environment once a rotation is approved by the config owner.

03

Block a project deletion

Hold a project deletion for approval, since it removes every environment and secret underneath it.

02 · ACTIONS

29 Doppler SecretOps actions, graded by risk.

Every Doppler SecretOps action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

0

Look things up. Allowed by default.

  • No read actions.

write

23

Create and change things. Allow, or ask the user first.

  • doppler_secretops.configs_get
    Get Config Details
  • doppler_secretops.configs_lock
    Lock Config
  • doppler_secretops.invites_list
    Invites List
  • doppler_secretops.configs_clone
    Clone Config
  • doppler_secretops.projects_list
    List Projects
  • doppler_secretops.configs_create
    Create Branch Config
  • doppler_secretops.configs_unlock
    Unlock Config
  • doppler_secretops.configs_update
    Update Config
  • doppler_secretops.secrets_update
    Update Secrets
  • doppler_secretops.config_logs_get
    Retrieve Config Log Entry
  • doppler_secretops.projects_create
    Create Project
  • doppler_secretops.config_logs_list
    Config Logs List
  • doppler_secretops.environments_get
    Get Environment Details
  • doppler_secretops.environments_list
    List Environments
  • doppler_secretops.integrations_list
    Integrations List
  • doppler_secretops.project_roles_get
    Get Project Role
+ 7 MORE

destructive

6

Delete, cancel or archive. Ask first, or deny outright.

  • doppler_secretops.configs_delete
    Configs Delete
  • doppler_secretops.projects_delete
    Projects Delete
  • doppler_secretops.environments_delete
    Environments Delete
  • doppler_secretops.groups_delete_member
    Remove Group Member
  • doppler_secretops.project_members_delete
    Remove Project Member
  • doppler_secretops.dynamic_secrets_revoke_lease
    Revoke Dynamic Secret Lease
03 · HOW IT WORKS

Doppler SecretOps in three steps.

  1. 01Your users connect Doppler SecretOpsThey add their Doppler SecretOps api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “get Config Details” can wait for the user, and “configs Delete” can be denied outright.
  3. 03Any agent can actYour agent calls Doppler SecretOps through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('doppler_secretops', {
  read: 'allow',
  write: 'ask',        // configs_get
  destructive: 'deny',  // configs_delete
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Doppler SecretOps connects.

Users add their Doppler SecretOps api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Doppler SecretOps connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Doppler SecretOps from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Doppler SecretOps and Arc0, answered.

Q01

Can I use Doppler SecretOps with Claude, ChatGPT or Cursor?

Yes. Connect Doppler SecretOps to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Doppler SecretOps actions you allow.

Q02

How do users connect Doppler SecretOps?

Users add their Doppler SecretOps api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Doppler SecretOps actions can my agent take?

29 in total: 0 read, 23 write and 6 destructive, such as “get Config Details”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Doppler SecretOps?

Yes. Actions like “configs Delete” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Doppler SecretOps too?

Yes. The same Doppler SecretOps connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Doppler SecretOps into your agent.

Your users connect Doppler SecretOps once, under your brand. Your agent gets 29 actions behind your policies, with every call on the record.

Connect Doppler SecretOpsBrowse all apps →

Free to build · MCP + REST · Audit log on every plan