Guides / API tokens
How to create a Vercel API token with the narrowest permissions
Shipyard uses a Vercel 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://vercel.com/account/tokens
- Open the link.
- Create a token. Under scope pick your personal account or one team, and set an expiry.
- Copy it and paste it into Shipyard.
Permissions, and why each one is needed
- A token scoped to one team, or to your personal account: Vercel tokens are scoped to an account or a team, not more finely. Pick the one team the project should live in.
Set up once in Vercel before your first launch
- Install the Vercel GitHub app on the account that owns your repos, with access to all repositories, so Vercel can deploy from them. (https://github.com/apps/vercel/installations/new)
- A product that takes money needs the Pro plan. The free Hobby plan is for non-commercial projects only. (https://vercel.com/account/billing)
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 Vercel account. A commercial product needs the Pro plan; the free Hobby plan is for non-commercial projects.
What you paste into Shipyard
- Access token
- Team ID (only if the project should live in a team; starts with team_) (optional)
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