Deploy and Host Railway and Github MCP for Claude Connector on Railway

A self-hosted MCP server that gives Claude or ChatGPT the ability to build and ship real applications. It exposes Railway tools (projects, services, deploys, variables, domains, logs, Postgres, volumes) and GitHub tools (repos, files, branches, pull requests, code search) behind a single connector, so you can describe what you want in plain English and have it built, committed, and deployed without leaving the conversation.

About Hosting Railway and Github MCP for Claude Connector

You deploy your own private copy — nothing is shared or multi-tenant. The service runs Node and Express behind a single /mcp endpoint, auto-derives its public URL from Railway, and persists OAuth and GitHub state on an attached volume at /app/data. Authentication is Login with Railway (OAuth 2.1 with PKCE and dynamic client registration), so there is no API token to paste — the server calls the Railway API as you, scoped to the workspace you consent to. Access is locked to the email you specify at deploy time. GitHub is connected separately and optionally via a device flow, again with no token to copy. Once deployed, open the service's public URL for setup instructions.

Common Use Cases

• Build and deploy a working app end to end from a chat conversation — create the repo, write the code, provision the service, and get back a live URL
• Manage existing Railway infrastructure conversationally: check deploy status, read logs, inspect variables, query a Postgres database, or attach a domain
• Review and modify code across your GitHub repositories — search code, open pull requests, and merge changes without switching tools

Dependencies for Railway and Github MCP for Claude Connector Hosting

• A Railway account (the connector authenticates as you and deploys into your workspace)
• A paid plan on Claude or ChatGPT — custom connectors are not available on the free tiers. Check your provider's current plans for which ones include them.
• A GitHub account, only if you want the GitHub tools. The Railway tools work without one.

Deployment Dependencies

• Source repository
• Model Context Protocol documentation
• Railway documentation
• GitHub signup (optional — only if connecting GitHub)

Implementation Details

One variable is required at deploy time:

• ALLOWED_RAILWAY_EMAILS — your Railway account email. Only this address can use the connector; anyone else who finds the URL is turned away. Comma-separate to allow more people later.

Optional variables for scoping capabilities:

• RAILWAY_MODE — read, deploy (default), or full. The default allows creating and deploying but not deleting.
• GITHUB_MODE — off, read, or write (default). Set to off to hide the GitHub tools entirely.
• DISCORD_WEBHOOK_URL with MCP_ACTIVITY_ALERTS=true — alerts on destructive actions.

After deploying, copy the service's public URL, append /mcp, and add it as a custom connector in Claude (Settings → Connectors → Add custom connector) or ChatGPT (developer mode). Then click Connect and log in with Railway. To enable GitHub, ask your assistant to run github-connect.

Why Deploy Railway and Github MCP for Claude Connector on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Railway and Github MCP for Claude Connector on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.