DevCycle

@DevCycle list all features in the mobile-app project and show which environments they're enabled in

Found 7 features in mobile-app. Three are live in production: 'new-checkout-flow' (enabled for 100% of users), 'dark-mode' (enabled for beta audience), and 'push-notifications' (enabled for users in US region). Two features are staging-only: 'experimental-search' and 'redesigned-profile'. Two features are disabled across all environments: 'legacy-payment-ui' and 'social-sharing'. Each feature includes its current targeting rules and rollout percentages per environment.

This read operation requires OAuth scope to view project features. The response reflects the state at query time—feature flags may change between queries if your team is actively deploying. Useful for auditing what's live before a release or debugging unexpected behavior in specific environments.

@DevCycle create a boolean variable called 'enable_ai_suggestions' in the web-platform project and associate it with the smart-editor feature

Created variable 'enable_ai_suggestions' (type: Boolean, default: false) in web-platform project. Variable is now associated with feature 'smart-editor' and available for targeting across all environments. You can configure per-environment values and targeting rules in the DevCycle dashboard or by updating feature configurations through this MCP. Variable key is stable and can be referenced in your application code immediately.

This write operation permanently adds a variable to your project. Requires OAuth scope for variable creation. The variable exists but won't affect application behavior until you configure targeting rules in at least one environment. Consider setting a safe default value (typically false for new features) to avoid unintended rollouts.

@DevCycle check the targeting configuration for the 'premium-analytics' feature across all environments and summarize which user segments will see it

The 'premium-analytics' feature uses different targeting strategies per environment. In development: enabled for all internal team members (audience: 'devcycle-internal'). In staging: enabled for 25% of users with email domain '@company.com' plus the 'beta-testers' audience (estimated 340 users). In production: enabled only for users with account_type='enterprise' AND region in ['US', 'CA', 'UK'] (estimated 2,100 users, 8% of total traffic). No targeting configured in the 'preview' environment—feature is fully disabled there.

This synthesis combines feature configuration data with AI reasoning to translate technical targeting rules into plain-language summaries. Useful for release planning or explaining rollout strategy to non-technical stakeholders. Audience size estimates depend on DevCycle's analytics data availability and may lag real-time user counts by several minutes.

When DevCycle wins for multi-environment feature releases

A 6-person engineering team shipping a new checkout flow needs to coordinate feature flags across staging, canary, and production. DevCycle's List Feature Configurations and List Environments tools let the team audit targeting rules in one pass during their release standup. The OAuth2 flow means each engineer authenticates once, then the shared workspace shows real-time flag state without passing SDK keys around Slack. This works cleanly when you have 3-8 environments and ship weekly or faster. If you only toggle flags once a quarter or run a single production environment, the MCP overhead outweighs opening the DevCycle dashboard. The buying call: teams running continuous deployment with environment parity use this to catch misconfigured rollouts before they hit users.

Using DevCycle MCP for live customer troubleshooting

A 3-person support team fields tickets about inconsistent UI behavior tied to feature flags. The List Variables and List Audiences tools let them search which flags apply to a specific customer segment without asking engineering to check the dashboard. The MCP surfaces variable types and audience membership in the shared Switchy workspace, so the support rep can confirm "yes, enterprise users see the new nav" in under 30 seconds. This scenario breaks down if your flag taxonomy exceeds 100 variables or you need to modify targeting on the fly—DevCycle MCP is read-heavy, and the Create/Delete Variable tools require project-write permissions most support teams shouldn't have. The threshold: if you troubleshoot flags more than twice a week, this saves 15 minutes per incident.

When DevCycle MCP handles feature flag compliance checks

A fintech startup's 4-person ops team needs quarterly proof that payment-related features were gated correctly across regions. The List Features and List Feature Configurations tools pull targeting history into the Switchy workspace, where the team exports a snapshot showing which audiences saw which variables in each environment. The OAuth2 auth means the audit log ties back to named users, not shared API keys. This works when you have 10-40 features under regulatory scope and audit once a quarter or month. If you need real-time compliance monitoring or your feature count exceeds 200, you're better off piping DevCycle webhooks to a dedicated audit database. The call: teams with light compliance needs use this to avoid building custom reporting infrastructure.