Kiwi
Kiwi

Kiwi for Railway

Have the agent on a Kiwi step redeploy a Railway service in a non-production environment, through Railway's MCP server.

  • Your agent works in Railway through its own connection. Kiwi does not call Railway and never holds its credentials.
  • A workflow skill can list Railway among the tools it requires. When you supply your agent's available tools to a skill check and Railway is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Railway, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Railway connection, with report_configuration.
  • The agent submits links to its work in Railway as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Railway

  • List the projects the account can see and the services in a project.
  • Create a new project.
  • Redeploy a service.
  • Check which account the connection is signed in as.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Railway

    Add the Railway MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.railway.com

    Railway documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Railway among its required tools.

    Read the Railway project, service and environment from the step's inputs.
If the environment is production, stop and hand the step to the run's Owner.
Otherwise redeploy that service in the named environment.
Submit the redeploy result and the service name as the step's outputs.
If the redeploy fails, report a blocker.
Get startedRead the setup guide