Check Your Railway Projects and Logs Through Your Muse

Through an AnythingMCP custom connector, your muse can look after your Railway apps in plain words: list your projects and services, check how the last run went, read the logs that explain a failure, and estimate usage.

What it does

The connector adds 19 tools and connects with a Railway API token. The muse can list projects with environments and services, and read how each service runs, including its start command, health check, and region. It can list runs with their state, such as success, failed, or crashed, and read the right logs: build logs when a run broke while building, running logs when it broke after it started. It can list the names of environment variables without their values, and read measured or estimated usage for a project or workspace. Redeploying and restarting are shown first, with the service and environment named, and wait for your yes. The tools that can read variable values or run any change are off at install.

How to use it

1. Start an AnythingMCP account and add the Railway connector.
2. In Railway, open Account Settings, then Tokens, and create a token. Pick one workspace for a token limited to that workspace, or no workspace for an account token that reaches all.
3. Paste the token only where the connector asks, exactly as Railway shows it, without the word Bearer.
4. Ask the muse to list your projects to check the setup.
5. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in, approve, then ask which service last failed and why.

What you need

• A Muse account that can add custom connectors
• An AnythingMCP account with the Railway connector added
• A Railway account or workspace token. Project tokens do not work here

What to watch for

• A redeploy builds the service and replaces the running one, and it counts as billed usage. A restart stops and starts the containers without a new build. Both can leave the service briefly unavailable.
• Usage comes back as computer time and memory, not dollars. Cost figures use list prices, without plan credits.
• Running logs show whatever your app prints, so treat them as sensitive. Variable values stay in Railway unless you turn that tool on yourself.
• The connector does not create, change, or delete projects, services, variables, or domains, and cannot roll back a run. This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.