Connect DevCycle to 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.
clariBI| Connection | MCP app. You sign in to DevCycle and approve read access. |
| Access | Read-only. clariBI keeps only the DevCycle tools that read. |
| Data | clariBI calls DevCycle when you ask a question and syncs list data where the server offers it. |
| Plans | Trial, Starter, Professional and Enterprise. Not on Free or Lite. |
About 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.
Vendor site: devcycle.com
What clariBI can read
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. Tools that create, change or delete anything are filtered out.
DevCycle is one of 86 apps in the clariBI MCP catalog. See the catalog
What you can chart
- 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
How to connect DevCycle
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 stored encrypted.
Ask questions, get dashboards
clariBI surfaces flag inventory, rollout state, and audit history. Ask "Which flags have not changed in 90 days?" and clariBI reads DevCycle alongside your release and product data.
Questions you can ask
Asking in plain English uses AI credits. The AI decides which DevCycle tools to call, totals are computed from the rows they return, and the AI writes the explanation.
- "Which flags shipped to production last sprint and do they map to closed tickets?"
- "How many flags are still partial weeks after their launch?"
About the DevCycle connector
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 plans include DevCycle?
DevCycle needs the trial or a Starter, Professional or Enterprise plan. MCP apps are not part of the Free or Lite plans.
Try DevCycle in clariBI
The trial lasts 14 days, includes 50 AI credits and needs no card. When it ends, your account moves to the Free plan and keeps its data and dashboards.