Skip to content

feat(connections): register Railway, launch-gated - #30662

Merged
bolichen97 merged 1 commit into
mainfrom
fix/19179-railway-connector
Nov 5, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
fix/19179-railway-connector

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Railway's hosted MCP server joins the vetted connection catalogue behind the launch gate, so it can ship as a one-click Connect once a person walks the launch-gate check.

Railway has no catalogue entry, so an agent reaches Railway deploys and service status only through an MCP server the user wires by hand. Railway does host a remote MCP server with OAuth discovery, which is the case the issue says lands as a registry entry rather than a recipe.

Why it matters

Without an entry Railway gets none of the catalogue's vetting: no nightly check of its OAuth metadata, no stated scope, no revoke link, and no warning that its tools deploy to running services.

Not a goal

  • Passing the launch gate: launch_gate_passed stays false until a person with a Railway account walks Connect, consent, Test and Disconnect.
  • A logo; the card falls back to its lettered tile, as Superhuman's does.
  • Railway's local server (railway mcp local), which has a different tool set.
  • Other bare tool names that two catalogue providers share without a declared rename.

What changed (motivation → approach → change)

Railway's server at https://mcp.railway.com publishes RFC 9728 metadata naming https://backboard.railway.com, whose RFC 8414 document offers dynamic client registration and PKCE (S256). Claude's connector directory and ChatGPT's both list it. That clears the first two rungs of the admission path, so Railway lands as a launch-gated entry, the way TickTick did.

Piece What it does
connections/registry.json The Railway entry: tier 2, developer-tools, asks for workspace:member (the only scope the server publishes), smoke fixture whoami, revoke page Account Settings → Apps, and card copy that names the tools that deploy or delete
security/exfil_oauth.py Railway's consent endpoint backboard.railway.com/oauth/auth joins the banner allowlist; without it every connect fails closed
whoami renames Railway, Sentry and Figma all ship a bare whoami and none declared a rename, so the second to mount hid the other's; each now declares <slug>_whoami
Docs docs/connections.md counts 37 providers and eleven rename declarers, docs/index.md says 37, and the spec roster gains a Railway row whose gate note adds a token-refresh check

Railway's documented hosted tools are redeploy, accept-deploy, create-project, list-services, the feature-flag tools and railway-agent, through which logs and debugging go. There is no rollback tool, so the entry does not claim one.

Backwards compatibility

Compatible: the Railway entry stays hidden until its launch gate passes, and the whoami renames apply only while two of the three servers are mounted together. Figma cannot finish OAuth from Kiro Crew today (vendor approval pending), so no working Sentry and Figma pair loses its bare whoami, and every pair with Railway is new.

Removes nothing: every touched file gains lines or changes a count; no key, path, function or row is removed.

Tests

  • test_railway_requests_the_one_published_scope_and_names_its_writers pins the requested scope and the deploy and delete tools the copy names.
  • test_railway_and_sentry_mounted_together_rename_both_whoami_tools pins both renames when Railway and Sentry are mounted together; connections_tool_aliases_helpers.py learns both URLs.
  • test_connections_registry.py's launch sets hold Railway as registered and gated; oauth_url_corpus.py gains Railway's consent URL for the banner tests; test_connections_doc.py's count words reach eleven; test_security_gate_liveness.py's package budget rises by the one allowlist line.
  • Determinism: the two new tests pass 20/20 at -n0; their three files pass 10/10 at -n 4; 356 tests from the four touched test files pass in a shuffled order (seed 19179).
  • The backend related set (59 files, 2697 tests) passes at 4 workers. No file under website/ changes, so the frontend set is left to CI.

Proof: PROVEN test/test_connections_registry.py::test_registry_contains_only_the_agreed_launch_set, test/test_connections_registry.py::test_probe_accessor_includes_every_entry_even_when_launch_gated, test/test_connections_tool_aliases_decision_table.py::test_railway_and_sentry_mounted_together_rename_both_whoami_tools (head f2799a3)

Manual verification

Done:

  • Discovery fetched live on 2026-11-05. An unauthenticated initialize against https://mcp.railway.com returns 401 with WWW-Authenticate: Bearer realm="mcp", resource_metadata=".../.well-known/oauth-protected-resource", scope="workspace:member".
  • python -m kiro_crew.connections.l0_probe on this head: 37 of 37 providers pass, Railway observed as authorization_server https://backboard.railway.com, dcr true, pkce true. --record produced exactly the committed Railway baseline.
  • https://railway.com/account/apps answers 200 where /account/authorized-apps answers 404, and Railway's docs put the grant under Account Settings → Apps.

Still owed before the card goes visible, on a test gateway with a real Railway account:

  • Connect, consent, Connected, Test, Disconnect, and record the revoke surface.
  • tools/list on the live server against Railway's documented hosted roster, including the bare whoami.
  • A session held past the access-token expiry: Railway documents refresh tokens only for offline_access, which the entry does not request.

Screenshots / video

N/A — no file under website/ changes, and the entry is launch-gated, so the Connect grid renders the same cards as main.

Related Issues

Closes #19179

Prior art: #29289 (TickTick), the entry this one mirrors.

Sibling sweep

N/A — a feature PR, not a fix.

Pattern harvest

N/A — a feature PR, not a fix.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributed under the project's Apache-2.0 license.

Add Railway's hosted MCP server (https://mcp.railway.com) to the
Connections registry as a tier-2 developer-tools entry with
launch_gate_passed=false, so the Connect grid does not change until the
manual launch-gate check passes. Railway is listed by both connector
directories, and its resource metadata names backboard.railway.com as
the authorization server, with dynamic client registration and PKCE, so
no operator app is needed. The L0 probe passes in record and strict
mode against the committed baseline.

The entry requests workspace:member, the only scope the resource
metadata publishes, and the card copy names the tools that deploy or
delete. Railway's consent URL (backboard.railway.com/oauth/auth) joins
the OAuth banner allowlist and the URL corpus.

Railway ships a bare whoami tool, as Sentry and Figma do, and none of
the three declared a rename, so whichever mounted second shadowed the
others. All three now declare <slug>_whoami. The user doc counts 37
providers and eleven rename declarers; the spec roster gains a row.

Closes #19179
@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/security/exfil_oauth.py

  • @buluoray approved f2799a3 with a complete reasoning template.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision f2799a30881399a8917cc5dd0235b6d4fed4b2f6 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of f2799a30881399a8917cc5dd0235b6d4fed4b2f6 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing to check.

What this change ships

Inventory (8 items) — 8 justified

Intent: let a person connect Railway's hosted MCP server in one click once the launch gate passes (ADDITION, closes #19179).

  1. A Railway catalogue entry that stays hidden until a person walks the launch-gate check — justified
  2. The nightly L0 probe now checks Railway's published OAuth metadata against a recorded baseline — justified
  3. The OAuth banner allowlist accepts Railway's consent URL backboard.railway.com/oauth/auth — justified
  4. Railway's whoami becomes railway_whoami when another provider with a whoami is mounted — justified
  5. Sentry's and Figma's whoami are renamed the same way when they are mounted together; tool_aliases.py only spots a collision between names the catalogue declares — justified
  6. The user docs now say 37 providers and eleven rename declarers, and show a whoami row in the rename table — justified
  7. The connections spec roster gains a Railway row with its gate notes — justified
  8. The package line budget in the security liveness test goes up by one for the allowlist line — justified

[FIRST-PRINCIPLES-REVIEWED] f2799a3

Description read

[DESCRIPTION-READ] 65e51e9be8a3093364efc3271012d9021b49e98a452649a6beb7a6a2436df411

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of f2799a30881399a8917cc5dd0235b6d4fed4b2f6 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: this is a registry entry with no new machinery, and it stays launch-gated. The whoami renames take effect only when two of the claimants are mounted together.

[DESIGN-REVIEWED] f2799a3

Description read

[DESCRIPTION-READ] 350e9fdda166b32bf1e3580e750e5ab1bbd839928cb5c00725a647b260a79fbf

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed f2799a30881399a8917cc5dd0235b6d4fed4b2f6 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] f2799a3

Verdict parsed from the review's SHA-scoped output markers for commit f2799a30881399a8917cc5dd0235b6d4fed4b2f6.

False positive or not applicable? A repository writer can comment:
/ai-review override fable f2799a30881399a8917cc5dd0235b6d4fed4b2f6 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of f2799a30881399a8917cc5dd0235b6d4fed4b2f6 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] f2799a3

False positive or not applicable? A repository writer can comment:
/ai-review override gpt f2799a30881399a8917cc5dd0235b6d4fed4b2f6 false-positive: <reason, 20 to 500 characters>

@bolichen97
bolichen97 enabled auto-merge (squash) November 5, 2026 18:43
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Security Scope Review -- ✅ PASS

Which legitimate operations does f2799a30881399a8917cc5dd0235b6d4fed4b2f6 newly refuse? Updated in place on each push. A script-confirmed regression blocks; the model proposes candidates and never decides a refusal.

Verdict basis: adjudicated, zero confirmed regressions.

Security scope review -- adjudicated candidates

  • macos-latest (platform posix): 12 classified, 0 newly refused, 12 still allowed.
  • ubuntu-latest (platform posix): 12 classified, 0 newly refused, 12 still allowed.
  • windows-latest (platform windows): 4 classified, 0 newly refused, 4 still allowed.

No candidate flipped from allowed to refused.

Scope-Verdict: PASS

Reason: Nothing in this diff makes a rule stricter. The only security edit adds one exact (host, path) pair to the OAuth consent-endpoint allowlist, so the exfil tier refuses less. The other changes are a registry entry, whoami tool aliases for Sentry, Figma and Railway, docs and tests, and none of those touch the shell deny composite. Sixteen candidates probing the exfil tier around the new and neighbouring hosts are submitted for the harness to classify; no confirmed regression was handed to this review.

TIGHTENING: none. The one security hunk widens an exemption: src/kiro_crew/security/exfil_oauth.py _OAUTH_AUTHORIZATION_ENDPOINTS gains + ("backboard.railway.com", "/oauth/auth"),, which extends the banner-only PKCE entropy carve-out to Railway's consent URL. It removes a refusal and adds none. Its threat model is unchanged: the carve-out matches only that exact host and path, with no suffix matching.

ADJUDICATED: 16 candidates, 0 confirmed newly-refused

PLATFORM COVERAGE: The diff makes no assumption about paths, separators, interpreters or environment variables in any guard. The new allowlist entry is a host and URL path pair, which is the same on every platform. The candidates cover:

  • posix: curl discovery and consent-endpoint reads against mcp.railway.com, backboard.railway.com, mcp.sentry.dev and api.figma.com; Railway CLI whoami, status, logs and up; pytest runs of the touched tests; a jq read of the registry.
  • windows: curl.exe and railway.exe spellings, and the pytest run with \ separators, because the exfil tier sees the executable name and the argv shape.

No assumed platform is left without a candidate.

UNADJUDICATED: The allowlist entry is read by exfil_oauth on two paths that the shell classifier does not settle:

  • ACP consent-URL banner gate, called from dashboard/chat_turn/mcp_session.py around line 354. The input that would test it is the Railway consent URL in test/oauth_url_corpus.py (railway-mcp). That URL is a widening target, not a newly refused input.
  • The endpoint-identity helper around exfil_oauth.py:559.

Since the entry only adds an exemption, neither path can newly refuse anything. The whoami → sentry_whoami / figma_whoami renames change the names agents see for MCP tools. No shell row can measure that. It is a name change rather than a refusal, so it is noted here and not claimed as a pass.

[SCOPE-REVIEWED] f2799a3

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 5, 2026

@buluoray buluoray left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Kiro Crew Auto-Pipeline [operator: buluoray]:

Approve. This adds Railway's hosted MCP server to the Connections catalogue behind the launch gate. Once a person walks the manual check, Railway becomes a one-click Connect with a stated scope, a revoke link and a warning that names its deploy and delete tools. Until then, nobody sees a change.

What I verified on f2799a3:

  • Launch gate: the entry has launch_gate_passed false. The visible set filters on launch_gate_passed or a pre-registered client (connections/registry.py:742), and the gate-passed set on this head is still notion, linear, atlassian, stripe, vercel, gitlab. No website file changes.
  • Railway facts, fetched live today: the resource metadata at mcp.railway.com names backboard.railway.com and publishes only workspace:member. The authorization server's metadata gives the endpoint /oauth/auth, dynamic registration and S256 PKCE. The revoke page railway.com/account/apps answers 200. The mcp_url, docs_url, l0 baseline and revoke page in the entry all match.
  • Card copy: every tool it names (redeploy, accept-deploy, create-project, set-feature-flag, delete-feature-flag, railway-agent) is on Railway's documented hosted list. The railway-agent description matches the docs. The workspace-picking sentence is narrower than what the docs allow, never broader. The copy makes no rename or refresh claim.
  • Allowlist: exactly one exact (host, path) pair was added. It is matched as a set key on (host.lower(), path) at security/exfil_oauth.py:559-560, with no prefix or subdomain widening. The package budget goes from 34,523 to 34,524, matching the one added line.
  • Renames: Railway, Sentry and Figma all ship a bare whoami and use it as their smoke tool, so the clash is real. resolve_tool_aliases renames only when two or more URL-verified claimants are exposed, so a lone Sentry keeps whoami. Sentry is gated and Figma is waiting on vendor approval, so no default-path user loses a name. Connection Test counts tools/list and does not call the fixture by name, and linear, atlassian, vercel and ticktick already alias their smoke tools.
  • Tests: 1056 passed across the touched files and every file importing the two touched helpers. A wider run of test_connections*.py plus test_exfil*.py gave 1654 passed. Merge-tree against main is clean.
  • Mutations, each run alone and reverted:
    • Removing the Railway allowlist pair reddens test_corpus_url_not_flagged_as_credential[railway-mcp] and test_corpus_url_renders_banner[railway-mcp].
    • Flipping Railway's launch_gate_passed to true reddens test_only_gated_launch_services_are_visible and test_probe_accessor_includes_every_entry_even_when_launch_gated.
    • Deleting Sentry's tool_aliases reddens test_railway_and_sentry_mounted_together_rename_both_whoami_tools.
  • Review lanes on this head: Opus and GPT found nothing. Design, First Principles and Security Scope passed (0 newly refused). UX skipped. None holds.

Not exercised: a real Connect, consent and refresh against Railway. The PR lists these as owed at the launch gate.

Follow-ups, none blocking:

  1. Railway's authorization server also lists workspace:viewer and project:viewer, even though the resource metadata publishes only workspace:member. The launch-gate check should try a viewer grant against mcp.railway.com before the spec's "read-only shape: none" is treated as settled.
  2. The authorization server lists offline_access, and the entry does not request it. If the gate's held-past-expiry session drops, the entry should request offline_access.
  3. Figma's whoami alias has no decision-table test of its own. Only the Railway and Sentry pair is pinned.

Sensitive change review

  • Head commit: f2799a3
  • What rule changed: _OAUTH_AUTHORIZATION_ENDPOINTS in src/kiro_crew/security/exfil_oauth.py gains one exact (host, path) pair, ("backboard.railway.com", "/oauth/auth"). That is the set of consent endpoints where the banner-only high-entropy OAuth query (PKCE challenge, state, client_id) is not treated as a credential.
  • Before -> after (what was allowed/blocked, now): Before, a Railway consent URL from the OAuth flow was flagged as carrying a credential, and the banner refused it, so a Railway connect would fail closed. After, that exact host and path render the consent banner. Every other host, any other path on backboard.railway.com, and any subdomain still go through the unchanged check, because the match is an exact set key on (host.lower(), path) (exfil_oauth.py:559-560). The HTTPS-only and no-explicit-port rules enforced by callers are unchanged.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A real secret placed in the query of a URL to https://backboard.railway.com/oauth/auth would be shown in a consent banner instead of being refused. That host is Railway's own published authorization endpoint, so the exposure is limited to Railway's own login page. Nothing broadens for other hosts. If the entry were wrong in the other direction, only Railway connects would fail, and the entry is launch-gated anyway.
  • Evidence checked (which sandbox result proves it): Removing the pair makes test/test_mcp_oauth_banner.py::TestLegitOAuthUrlCorpus::test_corpus_url_not_flagged_as_credential[railway-mcp] and ::test_corpus_url_renders_banner[railway-mcp] fail, so the new corpus URL depends on exactly this pair. Live fetch of Railway's authorization-server metadata confirms authorization_endpoint https://backboard.railway.com/oauth/auth. The Security Scope Review lane reports 0 newly refused on macOS, Ubuntu and Windows.
  • No regression:
    • Tools still work (which tools/commands were run, result): the OAuth banner and URL suites (test_mcp_oauth_banner.py, test_security_oauth_urls.py) and test/test_exfil*.py passed on this head as part of 1654 passed.
    • Backward compatible (old config / old data / old callers still work, how checked): The change only adds an entry to a frozenset. Every existing pair and the operator-file extension path are untouched. The existing corpus entries for the other providers still pass in the same suites.
    • Existing tests (which suites passed on this head): 1056 passed across the touched files and their helper importers. 1654 passed across test/test_connections*.py and test/test_exfil*.py. test/test_security_gate_liveness.py passed with the budget raised by exactly the one added line (34,523 -> 34,524).
  • How to undo: Revert the commit, or delete the single ("backboard.railway.com", "/oauth/auth") line and lower _PACKAGE_LINE_BUDGET back to 34_523. The Railway registry entry would then fail closed at consent until it is re-added.

@bolichen97
bolichen97 merged commit 96e6620 into main Nov 5, 2026
101 of 102 checks passed
@bolichen97
bolichen97 deleted the fix/19179-railway-connector branch November 5, 2026 20:12
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Railway connector: deploys, service status, logs and rollback

2 participants