DevCycle for AI agents

DevCycle is a feature flag platform that lets engineering teams create, target, and roll out features across applications without redeploying code. 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.

Developer toolsOAuth 2.0 client credentialsMCP + RESTdevcycle.com
AUDIT LOG · DEVCYCLEPOLICY: acme-support
09:41:07 · claude · u_8f2read
devcycle.list_features
List Features✓ allowed · 212ms
09:41:08 · claude · u_8f2read
devcycle.list_projects
List Projects✓ allowed · 164ms
09:41:09 · claude · u_8f2write
devcycle.create_variable
Create Variable✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
devcycle.delete_variable
Delete Variable✕ blocked · policy: deny
EVERY DEVCYCLE CALL, ON THE RECORD
01 · USE CASES

What agents do in DevCycle.

01

List active feature flags

Pull every feature and its configuration across projects and environments before a release review.

02

Adjust a targeting variable

Update a variable value for a specific audience once a rollout is approved by the release owner.

03

Require approval to remove a flag

Route a request to delete a variable through approval, since removing a live flag can break running code.

02 · ACTIONS

9 DevCycle actions, graded by risk.

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

read

6

Look things up. Allowed by default.

  • devcycle.list_features
    List Features
  • devcycle.list_projects
    List Projects
  • devcycle.list_audiences
    List Audiences
  • devcycle.list_variables
    List Variables
  • devcycle.list_environments
    List Environments
  • devcycle.list_feature_configurations
    List Feature Configurations

write

2

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

  • devcycle.create_variable
    Create Variable
  • devcycle.update_variable
    Update Variable

destructive

1

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

  • devcycle.delete_variable
    Delete Variable
03 · HOW IT WORKS

DevCycle in three steps.

  1. 01Your users connect DevCycleThey add their DevCycle oauth 2.0 client credentials on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Variable” can wait for the user, and “delete Variable” can be denied outright.
  3. 03Any agent can actYour agent calls DevCycle 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('devcycle', {
  read: 'allow',
  write: 'ask',        // create_variable
  destructive: 'deny',  // delete_variable
})

# 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 DevCycle connects.

Connect DevCycle with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

The same DevCycle 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
OAuth 2.0 client credentials
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use DevCycle from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

DevCycle and Arc0, answered.

Q01

Can I use DevCycle with Claude, ChatGPT or Cursor?

Yes. Connect DevCycle 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 DevCycle actions you allow.

Q02

How do users connect DevCycle?

Connect DevCycle with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

Q03

Which DevCycle actions can my agent take?

9 in total: 6 read, 2 write and 1 destructive, such as “create Variable”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in DevCycle?

Yes. Actions like “delete Variable” 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 DevCycle too?

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

Get started

Plug DevCycle into your agent.

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

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