mcp server
com.devcycle/mcp
DevCycle MCP server for feature flag management
Description as published by the maintainer. Source
- version 6.3.2
- active
active — Most recent push to the repository was 2026-08-05.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 20 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-05 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 3 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 6.3.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-28 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-04-28 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.configcat/mcp-server
— last commit 2026-07-20, shares feature-flags
Enables AI agents to interact with ConfigCat, a feature flag service for teams.
-
antonbabenko-terraform-skill-terraform-skill
— last commit 2026-07-03, shares devops
Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failur…
-
SentinelX
— last commit 2026-08-01, shares devops
Operate your Linux servers from your LLM. Every action runs through an auditable allowlist.
-
adrkit decision memory
— last commit 2026-08-06, shares devops
Deterministic, offline, read-only ADR decision memory for coding agents. No model or network calls.
-
emisar
— last commit 2026-08-06, shares devops
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
-
Servonaut
— last commit 2026-08-05, shares devops
Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.
-
Control Plane
— last commit 2026-08-05, shares devops
Control Plane (controlplane.com): deploy and operate workloads across AWS, GCP, Azure, and more.
-
io.github.47-ronn/remote-agents
— last commit 2026-07-22, shares devops
Control fleets of remote machines via AI agents: exec, files, git, fleet ops, map/reduce.
-
io.github.ai-4-devops/devops-practices
— last commit 2026-02-22, shares devops
Productivity framework for DevOps engineers using AI assistance (Claude Code) while working on PoCs
-
MikroMCP
— last commit 2026-07-21, shares devops
MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
These share tags the maintainers applied themselves, such as feature-flags, devops. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: continuous-delivery, continuous-deployment, devcycle, devops, feature-flags, feature-toggles, openfeature.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab