Deploy and Host Executor MCP Gateway on Railway

Executor is an open-source MCP gateway that lets any MCP-compatible agent — Claude Code, Cursor, Codex, and others — connect to every tool you use through a single endpoint. Instead of exposing hundreds of individual tools to an agent's context, Executor collapses them into one execute tool that searches and calls your configured integrations on demand.

About Hosting Executor MCP Gateway

Executor's self-hosted image runs the entire server — the typed API, MCP server, authentication, sandboxed code execution, and web console — as a single container over a libSQL (SQLite) file, with no external database or separate services required. This Railway template deploys the official image with a persistent volume for the SQLite database and generated encryption keys. The first person to visit the deployed URL and create an account becomes the instance owner; everyone else joins through single-use invite links minted from the Admin page, since open signup is closed by default.

Common Use Cases

Unified agent tool access — connect MCP servers, OpenAPI specs, and GraphQL endpoints once, then give every agent (Claude Code, Cursor, Codex) the same catalog through a single MCP endpoint instead of configuring each client separately
Context-efficient tool exposure — instead of loading hundreds of tool definitions into an agent's context window, Executor exposes one execute tool that searches and loads schemas only when actually called, keeping prompts small even with thousands of connected tools
Team-wide credential management — configure per-user or shared credentials once at the gateway level, so team members don't repeat integration setup for every agent or session, with sandboxed execution ensuring raw tokens are never exposed to the model

Dependencies for Executor MCP Gateway Hosting

Executor self-hosted Docker image — used directly by this template
Persistent volume mounted at /data — included in this template; stores the SQLite database and generated encryption keys across redeploys

Deployment Dependencies

Implementation Details

The template pre-configures the following environment variables:

PORT=4788                                            # HTTP port the server listens on
BETTER_AUTH_SECRET=${{secret(32)}}                   # Session secret; rotating it signs everyone out
EXECUTOR_SECRET_KEY=${{secret(32)}}                  # Master key encrypting stored secrets
EXECUTOR_WEB_BASE_URL=https://${{RAILWAY_PUBLIC_DOMAIN}}  # Public URL browsers use — must match exactly, or logins fail with an invalid-origin error

⚠️ A persistent volume is mounted at /data in this template. This is where the SQLite database (data.db) and generated encryption keys live, so accounts, connections, and configured integrations survive redeploys.

First-run setup — visit your deployed URL after the first deploy completes. The first account created becomes the instance owner. To skip the browser-based first-run screen (useful for headless or infra-as-code deployments), set:

EXECUTOR_BOOTSTRAP_ADMIN_EMAIL=
EXECUTOR_BOOTSTRAP_ADMIN_PASSWORD=

Connecting an agent — Executor exposes a streamable-HTTP MCP endpoint at /mcp. Point any MCP-compatible client at https://your-deployment.up.railway.app/mcp to access your configured tool catalog.

Inviting team members — once the instance is running, open signup is disabled by default. Generate single-use invite links from the Admin page in the web console to add teammates.

Why Deploy Executor MCP Gateway 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 Executor MCP Gateway 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.