# How to connect Railway MCP with ChatGPT Work

```json
{
  "title": "How to connect Railway MCP with ChatGPT Work",
  "toolkit": "Railway MCP",
  "toolkit_slug": "railway_mcp",
  "framework": "ChatGPT Work",
  "framework_slug": "chatgpt",
  "url": "https://composio.dev/toolkits/railway_mcp/framework/chatgpt",
  "markdown_url": "https://composio.dev/toolkits/railway_mcp/framework/chatgpt.md",
  "updated_at": "2026-08-25T05:33:47.803Z"
}
```

## Introduction

### How to connect Railway MCP with ChatGPT Work
[ChatGPT Work](https://openai.com/chatgpt-work/) is an agent inside ChatGPT built for your most ambitious work. It takes action across your apps and files, stays with a project for hours, and turns a goal into finished materials like sheets, slides, and docs - not just answers.
In this guide, I will explain the easiest and most secure way to connect your Railway account to ChatGPT Work via Composio Connect, so it can create projects, inspect environments, trigger deployments, and manage rollbacks through natural language commands without ever putting your account credentials at risk.

## Also integrate Railway MCP with

- [Claude Cowork](https://composio.dev/toolkits/railway_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/railway_mcp/framework/hermes-agent)

## TL;DR

### Why use Composio over default connectors?
- Apps with read and write access. Default connectors mostly can read your data. Composio's Railway integration lets ChatGPT Work take actions like creating drafts, sending updates, labeling records, and more.
- 1,500+ SaaS toolkits out of the box. Composio gives you instant access to a vast catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
- One MCP server for every app. Connect any of your applications on demand through a single endpoint, rather than juggling a separate server for each app.
- Smart, context-aware tool loading. Unlike traditional MCP servers that dump every available tool into the LLM context window, Composio searches for and loads only the tools relevant to the task at hand.
- Cross-app automation. Chain actions across multiple apps in a single run - fetch a thread, summarize it in Notion, and post highlights to Slack without leaving the conversation.

## Connect Railway MCP to ChatGPT Work

### Prerequisites
- A ChatGPT account with access to ChatGPT Work (rolling out across Pro, Enterprise, Edu, Plus, and Business plans). We will use the [ChatGPT desktop app](https://openai.com/chatgpt/download/), which is available on every plan.
- Access to the Railway workspace you want to connect.
- [Composio MCP](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=chatgpt&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fchatgpt).
Note: Composio connects through OAuth. You will be asked to sign in and approve specific permissions. Review the permission screen carefully if you are using a work account.
### Step-by-step: Connect Railway to ChatGPT Work
### 1. Open the MCP settings
In ChatGPT Work, go to Settings and open the Plugins section. Inside the Plugins page, click the MCP tab.
### 2. Add the server
Click Add server. In the Name field enter Composio, for Type select Streamable HTTP, and in the URL field paste the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the Railway MCP server, and what's possible with it?

The Railway MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Railway account. It provides structured and secure access so your agent can perform Railway operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `RAILWAY_MCP_ACCEPT_DEPLOY` | Accept-deploy | DESTRUCTIVE: Commits all staged changes in a Railway environment and triggers a deploy. Only use this when the user has explicitly confirmed they want to deploy. |
| `RAILWAY_MCP_CREATE_DEPLOYMENT` | Create-deployment | Create a new service from a GitHub repository and trigger its first deployment. The repo must be one the authenticated user has connected via GitHub. Returns the new service; use get-status or list-deployments to follow the deploy. Before calling this tool you MUST have a GitHub repo to deploy. If the user has not provided one, do not guess — first ask them which GitHub repo to deploy (in 'owner/name' form). If they don't have a repo yet, offer to help create one: if you have tools available to create a GitHub repository (e.g. a GitHub MCP server or `gh` CLI), offer to scaffold and push one for them; otherwise point them to create a repo on GitHub and share its 'owner/name'. Only call this tool once a concrete repo has been confirmed. |
| `RAILWAY_MCP_CREATE_PROJECT` | Create-project | Create a new Railway project |
| `RAILWAY_MCP_CREATE_SERVICE` | Create-service | Create a new service in a project from a Docker image, or an empty service to configure later (e.g. before setting variables and attaching a source). To create a service from a GitHub repository, use create-deployment instead. |
| `RAILWAY_MCP_DELETE_FEATURE_FLAG` | Delete-feature-flag | Delete a project-scoped feature flag. Workspace-scoped flags cannot be deleted from project context. |
| `RAILWAY_MCP_FETCH_DOCS` | Fetch-docs | Fetch the full markdown content of a Railway documentation page by URL or slug (e.g. 'https://docs.railway.com/quick-start' or 'reference/variables'). Use search-docs first to find the right page. |
| `RAILWAY_MCP_GENERATE_DOMAIN` | Generate-domain | Expose a service publicly. Without `domain`, generates a Railway *.up.railway.app service domain (if the service already has domains, they are returned instead of creating another). With `domain`, attaches a custom domain you own and returns the DNS records the user must create for it to verify. If environmentId is omitted, the production environment is used. |
| `RAILWAY_MCP_GET_FEATURE_FLAG` | Get-feature-flag | Get a Railway feature flag (Signal) by name for a project or its parent workspace scope. |
| `RAILWAY_MCP_GET_LOGS` | Get-logs | Get logs from Railway for a deployment — covers deploy (runtime), build, and http (proxy request) contexts. Pass a specific deploymentId, or pass serviceId + environmentId to resolve the latest deployment. Use `types` to choose which streams to return (default: ['deploy']). |
| `RAILWAY_MCP_GET_SERVICE_CONFIG` | Get-service-config | Get a service's configuration in an environment: source (repo/image), build settings, deploy settings (start command, healthcheck, replicas, cron, restart policy), networking, and volume mounts. Variable names are listed but values are not included — use list-variables for values. If environmentId is omitted, the production environment is used. |
| `RAILWAY_MCP_GET_SERVICE_METRICS` | Get-service-metrics | Get resource usage metrics (CPU, memory, disk, network) for a service, summarized as current/average/min/max over a time window. Defaults to CPU_USAGE and MEMORY_USAGE_GB over the last hour. If environmentId is omitted, the production environment is used. |
| `RAILWAY_MCP_GET_STATUS` | Get-status | Get the deployment status of a Railway project environment. Returns project + environment metadata and, for each service in the environment, its latest deployment status, replica count, and cron schedule. If environmentId is omitted, the project's `production` environment is used when present, otherwise the oldest environment. |
| `RAILWAY_MCP_LIST_DEPLOYMENTS` | List-deployments | List recent deployments for a Railway project, optionally filtered by environment, service, or status. Returns the most recent first. |
| `RAILWAY_MCP_LIST_DOMAINS` | List-domains | List all domains (Railway-generated service domains and custom domains) for a service in an environment. If environmentId is omitted, the production environment is used. |
| `RAILWAY_MCP_LIST_FEATURE_FLAGS` | List-feature-flags | List Railway feature flags (Signals) for a project and optionally the parent workspace. Project flags are editable with admin access; workspace flags are read-only from project context. |
| `RAILWAY_MCP_LIST_PROJECTS` | List-projects | List all Railway projects accessible to the authenticated user |
| `RAILWAY_MCP_LIST_SERVICES` | List-services | List all services and environments in a Railway project |
| `RAILWAY_MCP_LIST_VARIABLES` | List-variables | List all environment variables for a service, fully rendered (reference variables like ${{Postgres.DATABASE_URL}} are resolved). With a Railway session or API token, values are returned in plaintext and may contain secrets. Connected OAuth apps receive variable names only. If environmentId is omitted, the production environment is used. |
| `RAILWAY_MCP_LIST_WORKSPACES` | List-workspaces | List the Railway workspaces the current user belongs to. Use a workspace ID with create-project to choose where a project is created. |
| `RAILWAY_MCP_RAILWAY_AGENT` | Railway-agent | Send a message to Railway's AI agent for complex infrastructure operations. The agent can inspect services, diagnose issues, and take actions on your behalf. |
| `RAILWAY_MCP_REDEPLOY` | Redeploy | Re-run the most recent deployment of a service in a given environment, reusing that deployment's existing build. Only works on a service that has already deployed in that environment — check with list-deployments if you are unsure. This does NOT give a service its first deployment: if it has never deployed, nothing here can deploy it, and create-deployment would build a separate new service from a GitHub repo rather than deploying this one. |
| `RAILWAY_MCP_SEARCH_DOCS` | Search-docs | Search the Railway documentation (docs.railway.com) for features, configuration, guides, and tutorials. Returns matching sections with URLs — use fetch-docs to read a full page. |
| `RAILWAY_MCP_SET_FEATURE_FLAG` | Set-feature-flag | Create a project-scoped feature flag or update its default value. Use list-feature-flags and get-feature-flag to inspect existing flags first. |
| `RAILWAY_MCP_SET_VARIABLES` | Set-variables | Set one or more environment variables on a service (or environment-wide shared variables when serviceId is omitted). Existing variables with the same name are overwritten; others are left unchanged. Reference syntax like ${{Postgres.DATABASE_URL}} is supported. Affected services are redeployed unless skipDeploys is true. |
| `RAILWAY_MCP_UPDATE_SERVICE` | Update-service | Update a service's configuration: build/start/pre-deploy commands, healthcheck, sleep mode, root directory, cron schedule, Dockerfile path, restart policy, config file path, and watch patterns. Only the fields you pass are changed. Changes apply on the service's next deployment (use redeploy to apply immediately). Scaling (replicas/regions) and source changes are not handled by this tool. |
| `RAILWAY_MCP_WHOAMI` | Whoami | Get the current authenticated Railway user's profile information |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, ChatGPT Work can access the Railway MCP server via Composio to run actions that you authorize, directly in your workspace.

## Complete Code

None listed.

## How to build Railway MCP Agent with another framework

- [Claude Cowork](https://composio.dev/toolkits/railway_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/railway_mcp/framework/hermes-agent)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch.
- [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster.
- [Azure Monitor Activity Log](https://composio.dev/toolkits/azure_monitor_activity_log) - Azure Monitor Activity Log is Azure's service that records management and control-plane events for a subscription. Use it to audit changes, troubleshoot issues, and track resource operations across your Azure resources.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Railway MCP?

With a standalone Railway MCP server, the agents and LLMs can only access a fixed set of Railway tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Railway and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with ChatGPT Work?

Yes, you can. ChatGPT Work fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Railway tools.

### Can I manage the permissions and scopes for Railway while using Tool Router?

Yes, absolutely. You can configure which Railway scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Railway data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)