24 days ago
The Railway connector in ChatGPT failed twice on 27 October 2026 when calling railway.list-connector-tunnels for my personal workspace (Hobby). Both metadata-only attempts returned the same error. The same connection successfully listed my workspace and fetched Railway documentation.
Exact error:
Mcp error: -32603: Internal error
Please investigate whether list-connector-tunnels supports personal workspaces and whether this indicates an API, permission or integration issue. No inventory was returned, so I am not claiming that no tunnel exists or reporting a production outage.
I am trying to identify an existing, supported read-only route for attributable in-container process identity/start time and effective application holds, protected-volume integrity, or restricted PostgreSQL observation. Platform configuration and health alone do not establish those facts. Please explain the available interfaces and their limits; do not execute SQL or inspect protected records on my behalf.
Please provide diagnosis or documentation only. Do not deploy, restart, unpause, enable tracing, create tunnels/proxies, or change credentials or permissions. Prior SSH/TCP attempts are outside the authorised retry scope. railway connect and --tunnel-only have not been run as alternatives.
The AI assistant recommended contacting support after the repeated inventory error prevented its capability assessment. I authorised this request. Resource identifiers and protected evidence are omitted because this thread is public.
Prepared with Railway's support template (v1).
1 Reply
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
list-connector-tunnels is not one of the tools we publish for the Railway MCP server, and -32603 is a generic internal-error response, so on its own it does not show whether the workspace type, a permission, or the integration caused the failure. Since the same connection listed your workspace and fetched documentation, it was authenticated at the time.
For read-only observation, the hosted server at mcp.railway.com publishes tools for account identity, projects and services, feature flags, deploys, and the Railway agent, and the local server (railway mcp local) adds reads for workspaces, service config, deployments, variables, domains, TCP proxies, logs, service metrics, and HTTP request metrics. None of these published tools reports in-container process identity or start time, verifies volume integrity, or runs PostgreSQL queries, so platform logs and metrics are the limit of what they observe. The full tool list is on the MCP server docs.
Status changed to Awaiting User Response brody • 24 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago