How to connect Railway to Grok Bot

Connect Grok Bot to Railway MCP. Deploy latest commit to production service, list all services and environment variables, and more using natural language, with authentication handled for you.

Railway MCP logoRailway MCP
Oauth2

Railway MCP is Railway's hosted MCP server for managing projects, services, environments, variables, and deployments. Use it to automate deployments, inspect environments, and manage runtime configuration from AI agents.

46 Tools

Introduction

Grok is xAI's assistant, and its bot builder lets you create a personal agent that holds context, runs skills, and connects to the apps you already use through plugins.

This guide explains how to connect Railway to a Grok bot using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a plugin, authenticate once, then ask your bot to work with Railway in plain language.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Railway MCP with

Why use Composio?

Composio exposes 1,700+ apps to your Grok bot through a single connection, so you get:

  • Connect to 1,700+ apps with on-demand tool loading, so you do not fill your context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote workbench, letting the model write its own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the model context to keep conversations lean.

Connecting Railway to Grok Bot

Once Grok Bot is set up, you connect Railway entirely from its interface, and the whole flow takes under a minute.

Set up Grok Bot

Get access. Grok Bot is included with Cursor Ultra, Cursor Premium Teams, and SuperGrok Heavy. Get the desktop app for macOS or Windows from x.ai/bot and sign in. An iPhone companion app is also available, and your bots sync across devices.

Create a bot. Pick a suggested role or define your own, then give it a short name, one primary job, and a short description of how it should work. Focused bots work best, because a clear role gives the bot more useful context over time.

Connect Railway

1. Add the Composio plugin

Click the button. The Composio listing on x.ai opens and launches Grok Bot for you. If the app does not open on its own, click Add to Grok Bot.

Add to Grok Bot

Composio for Grok Bot listing on x.ai with the Add to Grok Bot button

Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.

Composio plugin sheet in Grok Bot with the Add button

2. Authenticate

Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.

Installed Composio plugin showing the Authenticate button

Click Authenticate. You'll be taken to the Composio consent screen. Review the access it requests and click Authorize. Composio handles the OAuth handshake for you, so you never touch API keys or tokens.

Composio authorization screen with Authorize and Deny

3. Connect your Railway account

Back in the chat, ask your bot to connect to Railway or give it any Railway task.

For example, ask it to:

  • "Deploy latest commit to production service"
  • "List all services and environment variables"
  • "Create staging environment and deploy service"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in your Grok bot, and your Railway account is ready to use.

What is Grok Bot?

Grok is xAI's assistant, available as a chat interface and a bot builder for creating personal agents that run skills and connect to external apps.

With Composio Connect, your Grok bot can securely access apps like Railway through MCP without you sharing account credentials directly with the agent.

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 to your Railway projects, services, environments, variables, and deployments, so your agent can create infrastructure, inspect configurations, deploy services, monitor performance, and troubleshoot failures on your behalf.

  • Project and service creation: Have your agent create Railway projects, add services from GitHub repositories or Docker images, and connect deployment sources.
  • Deployment management: Let the agent review staged changes, commit them for deployment, list recent deployments, redeploy builds, or restart running services.
  • Environment and configuration inspection: Instruct your agent to describe environments and services, list rendered variables, and inspect domains, volumes, buckets, and TCP proxies.
  • Monitoring and troubleshooting: Have your agent check service health, resource usage, request volume, error rates, response times, logs, and diagnoses for failed deployments.
  • Storage and public access: Direct your agent to create buckets and persistent volumes, generate public service domains, or expose services through TCP proxies.

Way Forward

Now that Railway is connected, extend your setup by connecting the other apps you already use every day, so your Grok bot can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, your bot can coordinate multiple tools safely and reliably in one conversation.

TOOLS

Supported Tools

Every Railway MCP action and event your agent gets out of the box.

Accept-deploy

DESTRUCTIVE: Commits all staged changes in a Railway environment and triggers a deploy.

Connect-service-source

Attach a source to an existing service: a GitHub repository (deploys on push, builds immediately) or a Docker image.

Create-bucket

Create an S3-compatible object storage bucket in a project and provision it in an environment.

Create-deployment

Create a new service from a GitHub repository and trigger its first deployment.

Create-project

Create a new Railway project

Create-service

Create a new service in a project from a Docker image, or an empty service to configure later (e.g.

Create-tcp-proxy

Expose a service on the public internet over a raw TCP port (e.g.

Create-volume

Create a persistent volume in a project and optionally attach it to a service at a mount path.

Delete-bucket

Permanently delete an object storage bucket and its contents.

Delete-feature-flag

Delete a project-scoped feature flag.

Delete-service

Permanently delete a service: its deployments stop and are removed, along with its domains, variables and deployment triggers.

Delete-tcp-proxy

Remove a service's TCP proxy, taking its public endpoint offline.

Delete-volume

Permanently delete a volume and its data.

Describe-environment

Inventory of everything in a Railway environment — services, volumes, buckets, shared variable names — with staged changes applied.

Describe-service

Everything about one service in an environment: its config with staged changes applied (source, build, deploy, networking, volume mounts), the per-field staged changes pending on it, mounted volumes, live domains and TCP proxies, and the latest deployment.

Domain-status

Get detailed status for one domain on a service, by hostname, URL, or domain ID: required DNS records and whether they currently match, ownership verification, certificate status, and any certificate error.

Environment-status

Health overview of every service in an environment in one call: current LIVE (settled) deployment state, replica status, recent failures, unresolved warnings/criticals, and cron execution results.

Fetch-docs

Fetch the full markdown content of a Railway documentation page by URL or slug (e.g.

Generate-domain

Expose a service publicly.

Get-deployment-diagnosis

Get the AI-generated diagnosis for a failed deployment: root cause category, analysis, and suggested fixes, along with deployment context (service config, source repo, branch, commit, PR, failure stage and error).

Get-feature-flag

Get a Railway feature flag (Signal) by name for a project or its parent workspace scope.

Get-logs

Get logs from Railway for a deployment — covers deploy (runtime), build, and http (proxy request) contexts.

Get-service-config

Prefer describe-service: it applies the staged diff onto the live config for you and adds mounted volumes, domains, TCP proxies and the latest deployment.

Get-service-metrics

Get resource usage metrics (CPU, memory, disk, network) for a service, summarized as current/average/min/max over a time window.

Get-staged-changes

Show the changes staged in a Railway environment that accept-deploy would commit: per resource (service, volume, bucket, group) the action — create, delete, update — and each changed field with its live and staged value.

Get-status

Prefer describe-environment: it also lists services that exist only in the staged patch, unattached volumes, and each resource's staged state.

Http-error-rate

Get the HTTP error rate for a service over time — the share of requests answered with a 5xx.

Http-requests

Get HTTP request counts for a service, bucketed over time and split by response status class (2xx/3xx/4xx/5xx).

Http-response-time

Get HTTP latency percentiles (p50, p90, p95, p99) for a service, bucketed over time, in milliseconds.

List-deployments

List recent deployments for a Railway project, optionally filtered by environment, service, or status.

List-domains

List all domains (Railway-generated service domains and custom domains) for a service in an environment.

List-feature-flags

List Railway feature flags (Signals) for a project and optionally the parent workspace.

List-projects

List all Railway projects accessible to the authenticated user

List-services

List the ids and names of all services and environments in a Railway project.

List-tcp-proxies

List the TCP proxies exposing a service over the public internet on a raw TCP port (e.g.

List-variables

List all environment variables for a service, fully rendered (reference variables like ${{Postgres.DATABASE_URL}} are resolved).

List-workspaces

List the Railway workspaces the current user belongs to.

Railway-agent

Send a message to Railway's AI agent for complex infrastructure operations.

Redeploy

Re-run the most recent deployment of a service in a given environment, reusing that deployment's existing build.

Restart-service

Restart a service's running deployment in place — the containers restart without rebuilding the image, and no new deployment is created (use redeploy for a fresh build copy).

Search-docs

Search the Railway documentation (docs.railway.com) for features, configuration, guides, and tutorials.

Set-feature-flag

Create a project-scoped feature flag or update its default value.

Set-variables

Set one or more environment variables on a service (or environment-wide shared variables when serviceId is omitted).

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.

Update-volume

Update a volume's name and/or mount path.

Whoami

Get the current authenticated Railway user's profile information

FAQ

Frequently asked questions

Start with Railway MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Railway MCP tool your agent needs.Free to start.

Start building