tcp_proxy_create
Create a TCP proxy to enable external access to services, configure database connections, or expose TCP endpoints on the railway-mcp server. Requires environment ID, service ID, and application port.
Instructions
[API] Create a new TCP proxy for a service
⚡️ Best for: ✓ Setting up database access ✓ Configuring external connections ✓ Exposing TCP services
⚠️ Not for: × HTTP/HTTPS endpoints (use domain_create) × Internal service communication
→ Prerequisites: service_list
→ Alternatives: domain_create
→ Next steps: tcp_proxy_list
→ Related: service_info, service_update
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| applicationPort | Yes | Port of application/service to proxy, usually based off of the service's Dockerfile or designated running port. | |
| environmentId | Yes | ID of the environment (usually obtained from service_info) | |
| serviceId | Yes | ID of the service |
Input Schema (JSON Schema)
{
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"applicationPort": {
"description": "Port of application/service to proxy, usually based off of the service's Dockerfile or designated running port.",
"type": "number"
},
"environmentId": {
"description": "ID of the environment (usually obtained from service_info)",
"type": "string"
},
"serviceId": {
"description": "ID of the service",
"type": "string"
}
},
"required": [
"environmentId",
"serviceId",
"applicationPort"
],
"type": "object"
}