Developer Tools & Devops · DevCycle + Claude
DevCycle MCP with Claude: Safer Feature Releases and Faster Rollbacks
The short answer
Claude works with DevCycle through the Model Context Protocol, a secure standard that lets Claude read and act inside the tool with permissions you control. Claude can list feature flags, create rollout rules, update targeting and summarise release health, while engineers approve changes that affect live users.
What is DevCycle?
DevCycle is a feature management platform. Development teams use it to switch features on and off with feature flags, decide which users see new functionality, run experiments and roll changes back quickly. Engineering, product and DevOps teams use it to release software more safely, reducing the risk of a single change disrupting every customer at once.
How Claude connects to DevCycle through MCP
The Model Context Protocol, or MCP, is an open standard that acts as a universal adapter between Claude and other software. Through MCP, Claude can securely use a tool like DevCycle to read information and take actions, and the organisation decides exactly what it is allowed to do.
Once connected, Claude can typically list the feature flags in a project, explain how each one is configured, suggest targeting changes, draft rollout rules and report on how a release is performing. A team member could simply ask in plain English which flags are still active for a retired feature.
Permissions and approvals keep people in charge. Access is limited to the least privilege needed, sign-in uses secure server-to-server OAuth2, and consequential changes such as a production rollout or rollback wait for a named engineer to confirm before they take effect.
What you can automate
Flag clean-up and housekeeping
Over time, codebases collect feature flags that nobody remembers. Claude can list flags that have been fully rolled out or unused for a long period, summarise them for the engineering lead and draft removal tickets. Engineers review the list and decide what to retire, which keeps the codebase tidy and reduces confusion for new team members.
Controlled rollouts for new features
Product managers can describe a release in plain language, such as enabling a new checkout option for five per cent of users in one region. Claude drafts the rollout rule and targeting conditions for review. Once approved, the gradual rollout proceeds in stages, so issues are caught while only a small group is affected.
Release monitoring and summaries
During a launch, operations and engineering leads often need quick answers about how a release is doing. Claude can pull the current state of a feature, summarise changes over the day and flag anything unusual for the on-call team. This saves time that would otherwise go on checking dashboards by hand.
Fast, documented rollbacks
When a feature causes problems, speed matters. Claude can help the on-call engineer identify the relevant flag, confirm its current targeting and prepare the rollback change. The engineer approves the action, and an audit trail records who changed what and when.
Experiment set-up and review
Growth and product teams running A/B tests can ask Claude to outline the variations, audience and success measures for an experiment in DevCycle. Claude drafts the configuration and a short summary of the test, which the product owner reviews before the experiment begins.
An end-to-end workflow: Safe release of a new payment option
TriggerA product manager submits a request in the team's ticketing system to release a new payment option to a small group of customers.
Claude reads the ticket from the ticketing system and extracts the target audience, region and release date.
Claude checks the existing feature flag in DevCycle and drafts a rollout rule for five per cent of eligible users.
The engineering lead reviews the draft in the approval step and confirms the rollout.
DevCycle applies the rollout, and Claude posts a status update to the team's Microsoft 365 channel each hour.
If error rates rise, Claude alerts the on-call engineer, who approves a rollback through the same controlled process.
OutcomeThe payment option reaches customers in controlled stages, the team has a clear record of each change, and any problem is contained within minutes rather than affecting the whole customer base.
How we set it up
Free automation audit
We review your release process, feature flag practices and the workflows where Claude could save engineering and operations time. You receive a clear list of opportunities with no obligation.
Secure connection
We connect Claude to DevCycle using server-to-server OAuth2, with least-privilege access scoped to the projects and environments you choose. No shared passwords are stored.
Workflow design
We map the end-to-end process across DevCycle and your other systems, such as Microsoft 365, your ticketing tool or your CRM, and define exactly which actions need human approval.
Testing against real cases
We test the workflow using past releases and rollbacks from your own history, refining prompts, rules and approval steps until results meet your standards.
Launch, monitoring and training
We launch with monitoring and audit logs in place, then train your engineers, product managers and on-call staff so they use the workflow confidently from day one.
Who benefits
- Engineering managers
- Clearer control over releases, with approvals and audit trails for every flag change.
- DevOps and on-call engineers
- Faster identification and rollback of problematic features during incidents.
- Product managers
- Simple, plain-language control over rollouts and experiments without waiting on tickets.
- Engineering leads and CTOs
- Fewer risky all-at-once releases and a tidier codebase with less flag debt.
Security and control
- Least-privilege access scoped to specific projects and environments.
- Secure server-to-server OAuth2 sign-in, with no shared credentials.
- Named human approval for production rollouts, rollbacks and targeting changes.
- Full audit logs of every action Claude takes or proposes.
- Testing against real past releases before launch, with monitoring after go-live.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with local data protection expectations. Companies in India must consider the Digital Personal Data Protection Act, 2023, when handling personal data in feature targeting. Businesses in the UAE and Saudi Arabia must meet their national data protection laws, and we select the hosting region to meet those requirements. Hosting choices in India, the United States, the United Kingdom or the European Union are available for custom applications.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the DevCycle MCP server do?
The DevCycle MCP server lets AI tools such as Claude interact with DevCycle through a standard, secure connection. Typically it allows listing feature flags, reading targeting rules, creating or updating rollout rules and checking release information. The exact capabilities depend on the server version and the permissions you grant, and we confirm these during the audit.
Is connecting Claude to DevCycle secure?
Security depends on how the connection is designed. We use server-to-server OAuth2 sign-in, restrict access to the minimum needed, and require human approval for consequential changes. Audit logs record activity, and access can be revoked at any time. We never guarantee security outcomes, but we design the connection around established least-privilege principles.
What can Claude actually do inside DevCycle?
Once connected, Claude can typically list flags, explain their configuration, draft rollout rules and targeting changes, and summarise release activity. Anything that changes live behaviour is routed for approval before it takes effect, so your team stays in control of production.
How long does setup take?
Timelines vary with the size of your DevCycle set-up and the number of workflows involved. A focused first workflow often moves from audit to launch in a few weeks, including testing and team training. We agree the timeline during the free automation audit.
What DevCycle plan or permissions do I need?
Access depends on your DevCycle account and the permissions your organisation grants to the connection. In general, you need an account with API access and a service identity scoped to the projects and environments involved. We confirm the exact requirements with your administrator during the audit.