devcycle.com
DevCycle is a feature flag and experimentation platform built around OpenFeature. It lets teams manage flags, targeting, variables, and evaluations across applications and environments.
DevCycle exposes two HTTP APIs (Management and Bucketing), a hosted MCP server, and a `dvc` CLI; all require DevCycle-issued credentials.
- DevCycle MCP Serverdiscovered
- DevCycle Bucketing APIdiscovered
- DevCycle Management APIdiscovered
- DevCycle CLIdiscovered
In the DevCycle dashboard, open Settings to get your client_id and client_secret. Exchange them at https://auth.devcycle.com/oauth/token with grant_type=client_credentials and audience=https://api.devcycle.com/ to obtain a bearer access token for the Management API, as shown in the Management API docs.
For Enterprise orgs with strict roles and permissions enabled, obtain the DevCycle API client_id from Settings, then use your DevCycle-issued refresh token with grant_type=refresh_token at https://auth.devcycle.com/oauth/token as documented in the Management API docs. The refresh token is organization/user-specific and is used to mint the bearer token accepted by the API.
In the DevCycle dashboard, open your environment's SDK Keys section (the CLI guides link to SDK Keys) and copy the environment sdkKey. The Bucketing API docs state requests can send this key either in the Authorization header or as the sdkKey query parameter.
$ dvc login ssoAcquired by the CLI — running dvc login sso opens the auth flow and stores the credential.
conventions · 1/7 published
- integrations.json——
- llms.txt✓https://devcycle.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing