Skip to content

Document Context Sources (MCP context for Railway Agent and dev.new) - #1284

Open
codyde wants to merge 1 commit into
mainfrom
railway/context-sources-docs
Open

Document Context Sources (MCP context for Railway Agent and dev.new)#1284
codyde wants to merge 1 commit into
mainfrom
railway/context-sources-docs

Conversation

@codyde

@codyde codyde commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds documentation for Context Sources — the feature that lets Railway's agents connect out to external MCP servers and use their tools during a chat.

  • New page: content/docs/ai/context-sources.md, covering:
    • Standard (one-click) context sources: Notion, Linear, Sentry, connected via OAuth
    • Custom MCP servers: registering any streamable-HTTP MCP endpoint by URL, with optional auth headers
    • The Context picker: attach-by-default behavior and per-chat scoping
    • That it works identically in both the Railway Agent (dashboard chat) and dev.new (Railway's AI app builder)
    • Permissions (workspace admin to connect/manage) and personal scoping (a source only ever serves its owner's runs)
  • Cross-links from content/docs/ai.md and content/docs/ai/railway-agent.md
  • Sidebar entry in src/data/sidebar.ts, generated src/generated/page-urls.json updated

Placement rationale

This lives under /ai/ alongside railway-agent.md, not under /agents.md ("Railway for Agents"). Those are the opposite direction: /agents.md and /ai/mcp-server.md cover external AI tools (Cursor, Claude Code) calling into Railway via mcp.railway.com. Context Sources is Railway's own agents calling out to Notion/Linear/Sentry/custom MCP servers — the new page calls out this distinction explicitly to avoid confusion between the two "MCP" features.

Status note for reviewers

This documents a feature currently gated behind the admin-only AGENT_CONTEXT_SOURCES flag in railwayapp/mono. It's marked with the same Priority Boarding banner pattern already used for other flagged features ahead of GA (see sandboxes.md, feature-flags.md). dev.new itself has no other public docs page yet, so it's introduced here with a one-line description rather than a full product page — worth a second look from whoever owns that launch.

Test plan

  • Ran pnpm install + pnpm dev, confirmed /ai/context-sources, /ai, and /ai/railway-agent all return 200 and render correctly (Banner, links, headings compile through content-collections/MDX without errors)
  • Verified all internal links resolve to existing pages
  • Verified technical claims (OAuth flow, HTTPS-only, header encryption, name pattern, 20-server limit, admin-gated settings UI, personal-only scoping) against railwayapp/mono source (packages/backboard/src/controllers/workspaces/mcpServers.ts, mcpCatalog.ts, contextIntegrationRegistry.ts, and the frontend settings/chat components)

Adds a new AI docs page covering Context Sources: connecting Notion,
Linear, Sentry, or a custom MCP server, and attaching them to chats in
the Railway Agent and dev.new via the Context picker. Cross-links from
the AI overview and Railway Agent pages, and adds a sidebar entry.
@railway-app

railway-app Bot commented Aug 7, 2026

Copy link
Copy Markdown

🚅 Deployed to the docs-pr-1284 environment in 🪄 *.railway.com

Service Status Web Updated (UTC)
Docs Frontend ✅ Success (View Logs) Web Aug 7, 2026 at 3:25 pm
7 services not affected by this PR
  • devicons
  • OG
  • Frontend Redis
  • Turnout
  • Meilisearch
  • Geofeed
  • Blog

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.

1 participant