Guides / API tokens
How to create a GitHub API token with the narrowest permissions
Shipyard uses a GitHub token for code. 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://github.com/settings/personal-access-tokens/new
- Open the link. The name and the permissions are already filled in.
- Resource owner: your account, or the organisation your projects live in.
- Expiration: pick "No expiration", or the longest option offered.
- Repository access: All repositories (the new repository does not exist yet, so it cannot be selected).
- Check that Permissions shows Administration and Contents, both "Read and write". Add them if the link did not.
- Press Generate token and copy it. GitHub shows it only once.
Permissions, and why each one is needed
- Administration: Read and write: Create the repository (and delete it, only if you ask destroy to).
- Contents: Read and write: Commit the starter template, CLAUDE.md and the launch kit.
- Metadata: Read-only: Required by GitHub for every fine-grained token.
Set up once in GitHub before your first launch
- If your repos live in an organisation: allow fine-grained tokens there (Organisation settings, Personal access tokens, Allow access via fine-grained personal access tokens). Without it the token cannot see the organisation.
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 GitHub account and verifying its email.
What you paste into Shipyard
- Fine-grained personal access token
- Organisation to create repos in (leave empty for your own account) (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