Railway Connector for Muse
List projects and deployments, set variables, redeploy.
- What
- List projects and deployments, set variables, redeploy.
- Cost
- Free
- Needs
- A Railway API token (account or workspace; dashboard under Tokens), kept in your Muse's secure vault (never paste secrets here). Note: set-var and redeploy are writes β confirm the project, environment, and values first; reading needs no confirmation. Paid API: Railway has no free tier β trial credit, then pay-as-you-go; usage is billed.
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid API required: this connector needs a paid third-party API β the listing is free, but usage is billed. See Prerequisites for costs.
Version:
Install
Prerequisites: A Railway API token (account or workspace; dashboard under Tokens), kept in your Muse's secure vault (never paste secrets here). Note: set-var and redeploy are writes β confirm the project, environment, and values first; reading needs no confirmation. Paid API: Railway has no free tier β trial credit, then pay-as-you-go; usage is billed. No GitHub account needed unless listed here. Install "Railway Connector for Muse" for me. A Muse agent skill for your Railway infrastructure: list projects and deployments, set environment variables, redeploy. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/railway 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "railway". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Railway API token in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a skill before installing it.