Guides / API tokens
How to create a Supabase API token with the narrowest permissions
Shipyard uses a Supabase token for database and auth. 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://supabase.com/dashboard/account/tokens
- Open the link.
- Generate a new token and give it a name.
- Copy it and paste it into Shipyard, with the slug of the organisation the project should live in.
Permissions, and why each one is needed
- A personal access token: Supabase access tokens act as your user. Shipyard creates one project in the organisation you name and does not touch your others.
Set up once in Supabase before your first launch
- Create an organisation if you have none. The free plan allows two active projects: pause or delete one if you already have two. (https://supabase.com/dashboard/organizations)
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 Supabase account and an organisation. The free plan allows two active projects and pauses a project after a week without use.
What you paste into Shipyard
- Access token
- Organisation slug (in the dashboard address: supabase.com/dashboard/org/<slug>)
- Region (empty for eu-central-1; for example us-east-1) (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