Railflag
com.railflag/railflag · v0.1.0 · MCP 2025-06-18
Create, target and roll out feature flags. Production changes wait for a person to approve.
Reachability
reachable
checked 2026-11-21 05:32 UTC
Registry status active
Tools pinned 29
516f42e9435f
Tools last changed
unchanged since first capture 2026-11-20
Provenance
Registry namespace com.railflag
(domain verified by the official registry)
Website
https://railflag.com/mcp
Remote endpoints
https://mcp.railflag.com/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-20 05:31 | first capture | 29 tools pinned |
Pinned tool definitions (29)
| Tool | Description |
|---|---|
| list_flags | All flags with their state in each environment. |
| get_flag | One flag: variations and full targeting in every environment, with versions for safe updates. |
| list_environments | Environments, whether they require approval, and their published config versions. Keys are not returned. |
| create_flag | Creates a flag, off in every environment. Boolean flags have variations [false, true]. |
| toggle_flag | Turns a flag on or off in one environment. In environments that need approval this returns an approvalUrl for a person. |
| update_targeting | Replaces a flag's targeting in one environment. Read it with get_flag first and pass its version as baseVersion so you never overwrite someone else's change. Rules are checked top to bottom; the first match wins. |
| set_rollout | Sets the percentage split for the default rule, or for one rule by id. percentages has one number per variation and must add up to 100 (e.g. [80, 20] gives 20% true for a boolean flag). Raising a percentage only adds users. |
| get_history | Audit log for the project or one flag: who changed what, when and why. |
| get_change_request | Status of a change waiting for approval: pending, applied, rejected or failed. |
| suggest_watch_plan | Drafts a Release Watch plan for a flag change: which signals to monitor (error rate, latency, conversions, new Sentry issues, the rollout split), the limits, and for how long. Describe the change with percentages (default rule split,... |
| get_watch | A watch: its status (draft, active, passed, paused, stopped), each signal's state, the timeline and the verdict. |
| list_watches | Watches in the project, newest first, optionally for one flag and by status (comma separated: draft, active, passed, paused, stopped, expired). |
| stop_watch | Stops watching. Doesn't change the flag. |
| monitoring_coverage | The project's monitoring coverage: live Production flags nobody watches (ranked by risk), kill switches never tested, flags no SDK evaluates, and services missing error or latency metrics. Business plan. |
| connect_monitoring | Starts connecting Prometheus/Grafana, Datadog, Sentry, New Relic or a Slack channel for alerts. Returns a one-time link: give it to the user, who enters the credentials there. Never ask the user for credentials in chat. Admins only. |
| list_sources | Vendors Railflag can import flags from, what it reads from each, and which are coming later. |
| connect_source | Starts a read-only connection to the user's account at another flag vendor (see list_sources). Returns a link the user opens to enter their credentials there. Never ask the user to paste credentials into the chat. After they finish,... |
| get_connection | Whether the user finished connecting, which source environments are visible, and whether decisions can be compared. |
| scan_source | Reads all flags and their targeting from the connected vendor (read only). Runs in the background: poll get_run with the returned runId. |
| get_run | Status and result of a scan, compare or apply run. |
| plan_migration | Builds a dry-run plan from the latest scan. envMap maps source environment ids (from get_connection or the scan) to Railflag environment keys, e.g. {"production": "staging"} to try production data in staging first. Nothing is written. |
| get_plan | A plan's summary, issues and items. full=true includes each item's targeting. |
| explain_item | The source vendor's definition of one flag next to what it becomes in Railflag, and its issues. |
| update_plan | Records decisions on issues. Each issue lists its allowed actions: skip_flag, drop_rule, keep, rename (value = new key), overwrite. Info issues need no decision. Ask the user when the choice is not obviously safe. |
| compare_decisions | Asks the source vendor what sample users get (AB Tasty: Decision API, needs a Decision API key on the connection; Unleash: its server-side playground) without recording anything, and compares with the plan. Runs in the background: poll get_run. |
| apply_plan | Writes the plan into one Railflag environment. Running it again changes nothing. Environments that need approval return an approvalUrl for a person. Never writes to the source vendor. |
| rollback_run | Undoes one apply run: restores previous targeting and archives flags it created. |
| disconnect_source | Deletes the stored credentials for a source connection. |
| get_code_guide | How to rewrite the source vendor's SDK calls to OpenFeature with Railflag: setup, regex patterns, before/after examples, notes. Apply it in the user's repo yourself and show them the diff. |
Get alerted when this changes.
Email the moment com.railflag/railflag drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/com.railflag/railflag)
Maintain this server? Add the badge to your README. It links your users to this live status page.