Hosting · 4 skills
Vercel MCP and Claude skills
Read deployments, build logs, runtime logs and domains from Vercel, and report failed builds, production deploys and errors after a release.
Connect Vercel to your agent (MCP)
- Vercel MCP, Vercel's official remote server at
https://mcp.vercel.com, signed in with OAuth. It lists projects and deployments, reads build and runtime logs, and searches Vercel's docs. - The
vercelCLI.vercel ls <project>lists recent deployments,vercel inspect <deployment-url> --logsprints the build log, andvercel logs <deployment-url>shows runtime logs. Pass--token $VERCEL_TOKENand--scope <team>in scheduled runs. - REST API with an access token created under Account Settings > Tokens and scoped to the team, stored in
VERCEL_TOKEN, withVERCEL_TEAM_IDsent asteamId.
Vercel tokens can be limited to one team and given an expiry but can't be made read-only, so use a short-lived token for reports and keep deploy and env var tasks out of the same skill.
4 Vercel skills
Vercel usage and spend this billing cycle
Every weekday: what this Vercel billing cycle has cost so far, how much included credit is left, the projected total, and which resource is driving it.
DevelopersWeekdays at 9:30Stat tileUses Vercel.Vercel failed deployments alert
Three times a day: Vercel production and preview deployments that failed in the last 24 hours, the step and error line, and an ask on whether to redeploy.
DevelopersWeekdays at 9:00, 13:00 and 17:00Asks youUses Vercel.GitHub, Vercel and Sentry release health check
An hour after each production deploy: errors after the release against the hour before, new Sentry issues, key page checks, and the PRs that shipped.
DevelopersEvery hourReport cardUses GitHub, Vercel, Sentry.Deploy to error to conversion chain
Each morning and after a deploy: every production release lined up with the Sentry issues it introduced and the key event rate before and after it.
DevelopersDaily at 8:00, and after each deployReport cardUses GitHub, Sentry, PostHog, Google Analytics, Vercel.What agents do with Vercel
Vercel's REST API lists deployments per project and team (GET /v6/deployments with projectId, target=production and state), each with state (READY, ERROR, BUILDING, CANCELED), createdAt, the creator and Git metadata such as meta.githubCommitSha and meta.githubCommitMessage. Build output comes from the deployment's events, request and function output from runtime logs, and domain configuration from GET /v6/domains/{domain}/config, which flags a domain whose DNS no longer points at Vercel.
The reports worth scheduling: failed preview and production builds with the error line from the log, a daily record of what went to production and from which commit, runtime errors after a deploy, and misconfigured domains.
Often used with Vercel
Teams that use these
Your Vercel numbers, on one board with everything else
Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.
Free during the open beta. No card.