Vercel Connect support in GitHub Tools
By Steven Van ·
GitHub Tools can now mint short-lived, scoped GitHub tokens via Vercel Connect instead of storing a personal access token.
GitHub Tools has added support for Vercel Connect, letting agents get GitHub access without a stored personal access token. Through a new @github-tools/sdk/connect subpath, an agent mints short-lived, scoped GitHub tokens at runtime from a connector instead, so there's no long-lived secret to store, rotate, or leak.
- Attaching a GitHub connector to a project and picking a preset, such as code-review, issue-triage, or maintainer, maps automatically to Connect scopes, so tokens only carry the permissions that preset needs.
- Importing from @github-tools/sdk/connect/eve registers the full toolset with Connect-backed auth from one file in agent/tools/.
- Calls can override installationId, repositories, or scopes to target a specific installation or narrow access to individual repos.
- Deployments on Vercel authenticate automatically with the OIDC token; local development uses vercel link and vercel env pull. Custom tool factories can use connectGithubToken, which returns a lazy token provider for createGithubTools.
Getting started means creating a GitHub connector and following the documentation.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →