Railway
by Railway
Deploy, redeploy and debug apps on Railway's usage-billed cloud from an AI assistant. 16 tools spanning project creation, deployments, feature flags and production logs. Anthropic's record carries no permissions label over the deploy tools, and the OAuth grant does not separate read from deploy.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Railway via MCP
https://mcp.railway.com/Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Railway Tools & Capabilities (16)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No permissions label in the directory record. Anthropic's entry has no permissions field, over a tool set that deploys to production. Railway's own docs are far more detailed; the directory is not.
- Five of 16 tools are undocumented.
create-deployment,deploy-artifact,get-logs,get-statusandlist-deploymentsappear nowhere in Railway's documentation corpus. Two of them write. - We did not authenticate. No
tools/listwas performed, so we have no tool annotations — noreadOnlyHintordestructiveHintvalues for any of the 16. Every safety claim here is Railway's documented prose, not a protocol annotation we observed. Railway says destructive tools are marked at the protocol level; we did not verify which ones carry the marking. - The scope grant does not separate read from deploy. One Railway scope covers everything the server does.
- No documented log scrubbing. Railway's docs describe no redaction of application log content that
get-logsreturns. accept-deployhas no documented human-in-the-loop. Staged changes are a review buffer for the same actor. The only gate is the MCP client's confirmation prompt.- The compute spend guard is a monthly cycle cap, not a per-action one. It stops a runaway month; it does not stop a single deployment.
- Feature flags are beta. Railway states they are available through Priority Boarding and that breaking changes may occur, and that the TypeScript SDK's API may change in breaking ways between releases.
- Cache propagation on flag deletion is unverified. The SDK caches flags in memory and refreshes in the background; Railway does not document how quickly a deletion reaches running instances.
railway-agentis a second model. It hands the request to Railway's own agent, which acts with your access and bills separately on token consumption.
Frequently asked questions
Can the Railway MCP server deploy code to my production app?
Yes. Railway documents accept-deploy as committing staged changes and deploying, and redeploy as redeploying a service, and the directory description says the connector can deploy services from connected GitHub repositories. Railway's docs list both among destructive tools you should review before approving. Anthropic's directory record for this connector carries no permissions field at all over that surface.
Does accept-deploy let an agent approve its own deployment?
Effectively yes, because Railway's staged changes are a review buffer rather than a second-person approval. The docs describe staging as changes collected for you to review, then applied by clicking Deploy, with no separate approver named. An agent holding accept-deploy stages and applies as one actor. The documented brake is the client confirmation prompt, not Railway.
How much does it cost when an AI agent deploys to Railway?
Railway bills resource usage on top of a plan fee: 10 dollars per GB of RAM per month and 20 dollars per vCPU per month, with plans at 0, 5 and 20 dollars monthly. A deployment an agent creates therefore accrues charges until it is removed. Railway documents workspace usage limits with a hard cap that shuts workloads down, minimum 10 dollars.
What does the Railway MCP server see in my application logs?
Whatever your application writes. Railway captures anything a build or deployment emits to standard output or standard error, plus HTTP logs carrying request paths, user agents and source IP addresses. Railway's logging documentation describes no redaction or scrubbing of application log content. The get-logs tool pipes that material straight into a model's context window.
Which Railway plan do I need to use the MCP connector?
Any plan with a Railway account, including the free tier. Railway documents Free at 0 dollars a month with 1 dollar of monthly credit, and a 30-day trial granting 5 dollars. Remote MCP requires only a Railway account and rejects project tokens, requiring a user identity for billing and audit. Feature flag writes additionally require a project admin role.
Sources
- Anthropic connector directory entry for Railway — tier, 16 tool names, endpoint, transport, absence of a permissions field
- Railway MCP Server — Remote MCP tool list, destructive markings, security considerations, project-token rejection
- Claude connector — OAuth connection flow, no CLI required
- Feature Flags — flag types, targeting, SDK fallback semantics, per-tool role table, Priority Boarding status
- Staged Changes — changeset review flow and the Deploy button
- Logs — what is captured, HTTP and DNS log attributes, filter syntax
- Pricing Plans — plan fees, resource rates, included usage, VM rates
- Cost Control — usage limits, hard limits, compute versus agent caps, replica limits
- Free Trial — trial grant and duration
- Project Members — Owner, Editor and Viewer permissions
- Guardrails — approved deployment sources, API-level enforcement
- Environment RBAC — restricted environments
- Functions — single-file Bun services, 96 KB limit, instant deploys
- Railway Agent — token-based billing at Anthropic's published rates
- Railway documentation full-text export — corpus searched for all 16 tool names and for redaction and scrubbing terms
https://mcp.railway.com/— anonymousinitializereturning 401 with awww-authenticateheaderhttps://mcp.railway.com/.well-known/oauth-protected-resource— RFC 9728 descriptor, 200https://mcp.railway.com/.well-known/oauth-authorization-server— RFC 8414 metadata, 200
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- Railway
- Tools
- 16
- Domain
- mcp.railway.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.