DevCycle + clariBI
Connect DevCycle through clariBI's MCP catalog. Read-only OAuth, and your feature flags, rollout state, and audit history turned into a flag-lifecycle inventory.
Native DevCycle connector via the MCP catalog.
Connect with OAuth, keep the access read-only, and ask questions across DevCycle and your other tools in plain English. The setup is the same one-click flow as Google Analytics, Stripe, Meta Ads, or Jira.
What is DevCycle?
DevCycle is a feature management platform built on OpenFeature. Each feature holds variations and variables, targeting rules decide which audiences see which variation, and a feature moves through its lifecycle from off, to a gradual rollout, to fully released across environments.
clariBI reaches your DevCycle project through its hosted MCP server: features and their variations, variables, environments, targeting rules and rollout percentage, and the audit log of who changed what. Reads inherit the connected user's project access, and clariBI never creates, edits, or deletes a flag.
Learn more at devcycle.com
Connect DevCycle in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source → MCP Servers tab. Find DevCycle in the catalog and click Connect.
Authorize with DevCycle (OAuth)
A DevCycle sign-in opens in your browser. Approve the read access. clariBI uses Dynamic Client Registration, so there is no DevCycle app to set up, and credentials are Fernet-encrypted at rest.
Ask questions, get dashboards
clariBI surfaces flag inventory, rollout state, and audit history. Ask "Which flags have not changed in 90 days?" and the AI engine queries DevCycle alongside your release and product data.
What you can analyze
Out of the box with the DevCycle MCP connector:
- Flag count by lifecycle stage: off, partial rollout, fully released
- Rollout percentage per feature across environments
- Stale flags untouched past a chosen age, ready to retire
- Targeting-rule changes from the audit log over time
- Variables and variations defined per feature
- Cross-source: targeting change → deploy date in your issue tracker
DevCycle is one of 90+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
clariBI discovers DevCycle's tool surface at connection time and exposes the read-only tools to the planner. Write or configuration tools are filtered out by the catalog's read-only heuristic, so the connector stays analytical.
When you connect, clariBI lists the tools your DevCycle MCP server advertises and keeps the read-only ones: reading features, variables, variations, environments, targeting rules, and audit history.
Anything that would change DevCycle is excluded at the catalog layer and never reachable through clariBI.
See the live tool list once connected, or read the setup guide →
Cross-source questions DevCycle makes possible
DevCycle data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
DevCycle × issue tracker
"Which flags shipped to production last sprint and do they map to closed tickets?"
Planner: read production targeting changes from the DevCycle audit log, then match each flag to the tickets closed in the same sprint in your issue tracker.
DevCycle × release log
"How many flags are still partial weeks after their launch?"
Planner: read rollout percentage per feature from DevCycle, join to launch dates from your release log, and flag the ones stuck below 100 percent.
DevCycle connector FAQ
Do I need to register an app with DevCycle?
No. clariBI uses Dynamic Client Registration (RFC 7591), so DevCycle issues the connection credentials at connect time. You do not manage any keys in clariBI.
Can clariBI create or change my flags?
No. The DevCycle MCP server can write, but clariBI keeps the read-only tools only and the read-only heuristic filters out anything that creates, edits, or deletes. clariBI reads features, targeting, and audit history; it never changes a flag.
How is this different from connecting an experimentation tool?
DevCycle answers questions about flag lifecycle, targeting, and rollout state: what exists, where it is in its release, and what changed. It is an inventory and audit view of your flags, not an experiment-results readout.
Which clariBI plan includes the DevCycle connector?
MCP integrations are available on the Trial, Starter, Professional, and Enterprise plans. You can connect DevCycle during the free 14-day trial.
Start your free trial and connect DevCycle in a minute
OAuth in, read-only, dashboards in seconds.
Start free trial