Vercel
Connect a Vercel account so the orchestrator can verify whether a pushed change has reached production, read deployment details, and pull build logs when a deploy fails — all without leaving the Agenties workflow.
How to connect
1.Open Settings for the project.
2.Go to Integrations → Vercel.
3.Paste a Vercel API token (create one at vercel.com/account/tokens).
4.Optionally enter your team slug if deployments belong to a team.
5.Save — credentials are stored in your OS keychain.
Note:The Vercel integration is read-only. Agents can inspect deployments and build logs but cannot trigger new deployments or modify project settings. Deployments are triggered by pushing to the linked Git repository.
MCP tools
| Tool | Parameters | Description |
|---|---|---|
vercel_list_deployments | limit? | List recent deployments from the configured Vercel account or team. |
vercel_get_deployment | deploymentId | Get detailed information for a specific deployment, including status, aliases, commit SHA, and inspector URL. |
vercel_get_build_logs | deploymentId | Read build events for a specific deployment. Use this when a deployment fails or appears stuck. |
Recommended workflow
| Step | What the agent should do |
|---|---|
| 1 - List deployments | Call vercel_list_deployments after pushing to get the latest deployment ID. |
| 2 - Poll status | Call vercel_get_deployment with the deployment ID and check the state field. |
| 3 - Verify aliases | Confirm the production alias points to the expected deployment once it reaches READY. |
| 4 - Debug failures | If state is ERROR or BUILD_ERROR, call vercel_get_build_logs to read the failure output. |
Tip:A typical release loop: commit, push to GitHub, call
vercel_list_deployments, then poll vercel_get_deployment until the deployment reaches READY and carries the expected production aliases.Common use cases
| Use case | Example |
|---|---|
| Release verification | Confirm a pushed feature reached the production alias before closing an issue. |
| Build failure diagnosis | Pull build logs after a failed deploy to find the root cause without opening the Vercel dashboard. |
| Deployment audit | Review which commit is live and when it was deployed as part of an incident investigation. |