Access tokens
Snapvisor has two kinds of credentials - project tokens for uploading screenshots from CI, and personal access tokens for the API and MCP server.
Snapvisor has two kinds of credentials. Using the right one keeps CI uploads and agent access cleanly separated.
Project tokens
A project token (the ARGOS_TOKEN you set in CI) authenticates screenshot uploads for a single project. It is upload-scoped: it can send builds, but it cannot read the API or drive the MCP server.
- Find it in the app under your project's settings.
- Store it as a CI secret; never commit it to the repo.
- Rotate it from the same screen if it leaks.
Personal access tokens
A personal access token acts on your behalf across the REST API and the MCP server. Create one under Settings → Tokens in the app. Use it for scripts, agents, or any headless MCP connection. With the MCP server it works the same as OAuth: the build loop (create a project, create, upload to and finalize builds, check status, read diffs) is on the Free plan, while review, approve and team tools need a paid plan (see Plan requirements). Calling the REST API directly with it works on every plan.
Personal access tokens carry your account's access — treat them like a password. Revoke unused tokens from the same settings screen.
Which one do I use?
- Uploading from CI → project token (
ARGOS_TOKEN). See the Quickstart. - Connecting an AI agent → OAuth or a personal access token. See the MCP server guide.