Guides / API tokens
How to create a Railway API token with the narrowest permissions
Shipyard uses a Railway token for hosting. The token is stored in your computer's keychain and is not sent to shipyardmcp.com. These are the exact steps, and the smallest set of permissions that works.
Create the token
Start here: https://railway.com/account/tokens
- Open the link.
- Give the token a name, such as Shipyard. In the workspace list, pick the workspace your projects live in. Press Create.
- Copy the token. Railway shows it only once.
- Paste it into Shipyard. When Shipyard asks for a workspace ID, press Enter to skip it.
Permissions, and why each one is needed
- Account token, or a token for one workspace: Railway tokens are not scoped more finely than a workspace. A workspace token is the narrowest that can create a project.
Set up once in Railway before your first launch
- Add a payment method and choose the Hobby plan ($5 a month). A trial account cannot attach a custom domain. (https://railway.com/account/billing)
- Install the Railway GitHub app on the account that owns your repos, with access to all repositories, so Railway can deploy from them. (https://github.com/apps/railway-app/installations/new)
What stays manual
These are things only a person can do at this provider. Shipyard cannot and will not do them for you.
- Creating the Railway account and adding a payment method (Hobby plan, $5 a month).
What you paste into Shipyard
- Account or workspace token
- Workspace ID (optional): Only needed with more than one workspace. It is a long code, not a name: Railway, workspace Settings, General, Workspace ID.
Have this set up for you
Shipyard connects your accounts once and then does all of this for every new product, in about an hour.
See how it works