NestDaddy

Railflag

com.railflag/railflag · v0.1.0

Create, target and roll out feature flags. Production changes wait for a person to approve.

MCP Score How we grade

B
81 / 100

From what our daily checks can see without credentials, last checked 21 Nov 2026.

Reliability
Answered 3 of 3 daily checks.
30 / 30
Speed
Typical response 179 ms.
16 / 20
Tool docs
22 of 29 tools have a full description; 10 of 65 inputs have a description.
11 / 25
Stability
No tool rewrites in 30 days.
15 / 15
Listing
Missing an icon.
9 / 10

How to raise the grade

  • Answer initialize faster: under 150 ms earns full Speed points (yours: 179 ms).
  • Describe every tool input in its inputSchema (55 of 65 have no description).
  • Give every tool a description of at least 80 characters: what it does and when to use it.
  • Add an icon to your server.json in the official MCP registry.
Fixed something? Run the same check now. The grade updates at once.

Connect Remote server

Terminal
claude mcp add --transport http railflag https://mcp.railflag.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "railflag": {
      "url": "https://mcp.railflag.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "railflag": {
      "type": "http",
      "url": "https://mcp.railflag.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.railflag.com/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 29 found in our last check

  • 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, like set_rollout), enabled (on/off) or a full…

  • 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, call get_connection.

  • 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.

Headers

NameDescription
Authorization
Required, secret
Railflag access token as Bearer rf_pat_… (Settings → Access tokens)

Details

Endpointhttps://mcp.railflag.com/mcp (Streamable HTTP)
First published19 Nov 2026
Last updated19 Nov 2026
Registry namecom.railflag/railflag

More developer tools servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.