DevCycle's MCP server acts as a bridge between AI assistants and your feature flag management, allowing you to create and manage feature flags using natural language, configure targeting rules without writing complex queries, test features safely using self-targeting and overrides, get real-time insights about your feature flag usage.

Bi-directional integration with the observability platforms, Dynatrace.

This work will include adding multi-select filtering, more filtering options, and an overall improved UX so it is easier visualize work and maximize efficiency for team’s overall software delivery process.

The ability to define your own custom Feature Type & Template, vs using the existing four Feature options (Release, Experiment, Ops, Permission).

This functionality allows teams to define their Feature statuses, such as In Development, QA, Production, etc., which gives features a more relevant meaning for every team based on their internal processes.

A DevCycle Linear integration streamlines your workflow by enabling the linking of Linear issues directly to features within DevCycle, making the feature status easily viewable within Linear.

This work would be redesigning the feature form into a tabbed view, and ensuring relevant Feature information is easy to find for users and the experience of making Feature updates seamless.

A historical lookup of what a given user received at a specific time. This project will create a new section of the DevCycle dashboard where you can inspect users and see what Features, Variations, and Variables they received at a given time.

Sub-feature of customizable feature statuses. If X occurs, trigger a status change (e.g., enabled targeting in Staging & added targeting rule using QA audience, change status to QA).

Contribute back to OpenFeature, a Next.js SDK spec. Once we’ve created the OpenFeature spec, this project will focus on creating an OpenFeature provider built into our Next.js SDK.

Bi-directional integration with two observability platforms as prototypes, Dynatrace and Sentry. This work will focus on building a way for data to be sent from DevCycle regardless of what your observability platform is.

Define custom Roles & Permissions for your Organization.

An aggregate view of all Feature Audit Logs for a particular Project.

A realtime feed of user data, feature/variable evaluations and event triggers

Ability to associate your Features' flag values with spikes in your error logs in DataDog.

Bi-directional integration between DevCycle for Audiences and events. Please let us know if Audience syncing or event integration is a higher priority for your team!

Adding the concept of deleting a Variable to the DevCycle interface. Sometimes, users make mistakes with variables and need to clean things up, so they need an easy way to remove unwanted variables completely.

Giving teams the ability to customize what makes a flag stale. Given every team has a different process and timelines for rollouts, each will have different rules that determine when a flag should be cleaned up.

Generate and submit a PR directly from the DevCycle interface for stale Variables and Features.

Expand DevCycle's code pipeline integrations to include Azure DevOps.

Creating a client-side C# SDK to augment that server-side C# SDKs.

Ability to instruct the SDK to serve certain values while disabling all network activity to the DevCycle servers that could influence the tests.

A view to see all Features that have targeting enabled in a particular environment or set of environments + an environment filter added to the Feature list page.

Adding a Regex Match comparator to DevCycle's targeting rules to enable more complex methods of targeting.

Automatically detect Variables that are run in code and recommend creation of the Variable within the DevCycle dashboard. This can make code-first workflows a lot more intuitive.

Download or export a Feature's Audit Log.

Audiences that are not Project-specific but available to be used in all projects within a DevCycle Organization.

Bi-directional integration with Amplitude for the purposes of pulling cohort data into DevCycle and sending Feature inclusion data to Amplitude.

The ability to exclude users exposed to other Features as part of a Targeting Rule or exclusion group/Audience.

Send Feature, environment, and project updates to Grafana as annotations to add context to your graphs.

Providing the ability to define Variables in code and then push those Variables to the DevCycle dashboard, ensuring that your codebase is the source of truth for Variable definitions.

Adding a "cover page" to Features in DevCycle that uses a markdown editor with embeddable media, so that all users can better understand the purpose of a Feature.

Adding to DevCycle the ability to create rules and automations for Feature status changes. Specifically this builds on top of Custom Feature Statuses, to ensure that when a Feature is In Development, In Production, etc it has specific targeting rules set.

Allowing DevCycle users to save multiple user IDs (potentially per environment) to a DevCycle Identity for Self-Targeting.

Providing AI coding tools such as Cursor an MCP server with which they can interact with the DevCycle platform to manipulate feature flags.

Oscar -- HITRUST compliance, we will need this asap

Connect ServiceNow to DevCycle's Approval Workflows so they can be actioned in ServiceNow.

Create the system and structures by which DevCycle can listen for inbound webhooks and react as necessary. Setting the stage for integrations like one with Datadog, where crossing an SLO turns off a Feature.

Updating the self-targeting feature to be able to target by audience, this is likely best described as creating teams or groups of QA user IDs for simpler or group level management.

Create a DevCycle integration with New Relic to send deployment events. A V2 of this feature would include the ability to have DVC targeting "triggers" to turn targeting on or off if a metrics passes a certain threshold.

Adding the ability to assign a team member who is primarily responsible for the Feature. By default, the owner is set to the member who created the flag, but can be changed. You can view and edit the owner in the Feature settings.

The ability to use multiple events either AND'ed or OR'ed together as the combined conversion events for a given metric.

Create a Gitops style of managing Variable and Targeting changes, so that those changes are approvable and auditable through the traditional Git process.

Providing the ability to define Custom Properties in code and then push those Properties to the DevCycle dashboard, ensuring that your codebase is the source of truth for Custom Property definitions.

A DevCycle provider for the Vercel toolbar, which now supports built-in feature flag overrides.

Expand the capability of DevCycle's Code Cleanup functionality by leveraging generative AI.

Add functionality, similar to our Javascript SDK, that triggers a hook when a Variable is evaluated in the mobile SDKs.

Create a generalized integration that supports the OpenTelemetry standard to pass feature flagging data as context for telemetry data.

Create an integration between Asana and DevCycle that creates a bi-directional link between asana and DevCycle, shows off the Feature status within Asana and controls the Feature status remotely.

The concept of a project setting that defines allowed time windows for a targeting rule schedule. The example would be, a schedule can only be set for Monday-Friday 9-5.

Ability to create alerts in the dashboard for when MAUs reach a selected % of the pre-paid threshold/contracted amount of MAUs.

A new Feature list view in a kanban style to better visualize feature statuses or environments.

Improving overall UX when building & managing Audiences throughout the platform.

Stale Feature detection enhanced with generative AI to automatically raise PRs for review on detection of staleness that can simply be approved, edited or denied, to manage flag removal easily and efficiently.

The natural follow-on of a bi-directional Observability integration are smart triggers off of Observability data. The most relevant smart trigger would be to generate a change request to turn off a flag on anomaly detection in Observability data.

After the initial guided onboarding, once a user is dropped into the main dashboard, leveraging a tutorial or tooltips to introduce new users to key DevCycle concepts in a lightweight way.

Create the initial integrations with key CI/CD platforms like CircleCI, Jenkins, etc, enabling the control of flags through CI/CD to validate builds.

This project would result in a publicly available server-side SDK that is built natively for Rust.

This work aims to add a method to DevCycle that will notify users of the platform when Features are in a state of their lifecycle where they can be marked as 'permanent' or have their variables cleaned up from the code.

When a DevCycle user makes a Feature change, they can request/might require approval for the change from a member of their DevCycle project. Approvals introduces an added level of protection and governance to your use of feature flags.

Ability to roll out or do random distribution grouping by a custom property. The primary use case is for B2B companies that want to roll out Features by an account or org ID.

When using SCIM/SAML account provisioning with permissions turned on you will now be able to manage access and roles on a per-project basis.

This work encompasses reducing the number of polling requests made to the DevCycle Config CDN, and instead using a long-lived HTTP connection to receive updates when there is a new config available. Node.js and Go SDKs complete. Working on Ruby.

Adding an API endpoint and functionality to the DevCycle SDKs that provide a JSON output for why a specific user received a given Variable value. This project should also ensure that our OpenFeature providers are updated to leverage the new evaluation reason functionality.

Completing the full SOC2 Type II audit and certification process.

Adding a native Roku SDK to our library of client-side SDKs.

Adding a "cover page" to Features in DevCycle that uses a markdown editor with embeddable media so that all users can better understand the purpose of a Feature. (e.g. custom links, JIRA ticket/epic status, description, etc.)

Contribute a library to the OpenFeature project that manages multiple providers at once to aid with a gradual transition between Feature Flagging solutions.

Use the Slack Integration App to connect your project to feed updates to your project's Features and more to a Slack channel.

An interactive widget that can be installed on a client's website to allow internal users to manage self-targeting within their active session.

Ensure all DevCycle SDKs have an OpenFeature provider built-in. This project will focus solely on upgrading our current support to match what’s available in OpenFeature.

A multi-part project that is focused on improving the self-serve ability to view usage and manage plans within DevCycle.

Option to pass through targeting rules given their schedule has not yet hit. Helps to enable use cases like time-gated features or scheduling a variation change to the same audience.

The SDK Install Wizard project is aimed at simplifying the process of implementing the DevCycle SDKs. The project has two key components; the install wizard itself and updating the dashboard to give the wizard a home.