Skip to content

Ship a fix and check the Vercel deploy

Fixing a bug means jumping between the editor, GitHub and the deploy logs.

3 stepsModerate
Claude CodeCursorGitHubVercel

How it connects

Your AI reaches your apps through small connectors called MCP servers.
Your AI
Claude CodeCursor
Connectors
GitHubVercel
Your apps
GitHubVercel

This setup is for developers who deploy on Vercel and want the agent to take a bug from fix to verified preview. The agent in Claude Code or Cursor edits the code, opens a pull request on GitHub, then reads the Vercel preview deployment and its build logs. You end up with a pull request and a checked preview link, and you still make the merge decision.

Set it up

3 steps. Open one for the details.
  1. 1Connect GitHub

    Connect GitHub's MCP server through OAuth or a fine-grained personal access token limited to the repositories you work on. Give it permission to read code, push to branches and open pull requests. Protect your main branch in GitHub so changes can only land through a reviewed pull request.

    Tip: Branch protection on main is the real guardrail here, whatever the token allows.

  2. 2Connect Vercel

    Add Vercel's MCP server and sign in with your Vercel account through OAuth. Ask the agent to list your projects and the latest deployments for this repository to confirm access. The agent can then read deployment status and build logs for the preview that each pull request creates.

    Tip: Point the agent at the project by name if your team has many Vercel projects.

  3. 3Verify the preview

    After the pull request opens, ask the agent to wait for the preview deployment, read the build logs and report any errors or warnings. Open the preview URL yourself and test the fix in the browser. Merge only when the build is green and the fix works.

    Tip: If the preview is protected, the agent may not load the page itself; check it in your own browser.

Then just ask

Things to say once it's connected. Click one to copy it.
Ask Claude Code…Claude Code

Good to know

What you need, what it won't do, and how to keep it safe.
What you need
  • GitHub repository connected to a Vercel project
  • Vercel account with access to that project
  • Claude Code or Cursor
  • Branch protection on your production branch
Limits
  • The agent reads build logs and deployment status; it does not test your app in a browser by itself.
  • Protected preview deployments may block automated page checks.
  • Runtime errors that only appear under real traffic will not show up in a preview.
Keep it safe
  • Never give merge rights to the agent.
  • Vercel access is read-only for deployments and logs.
GitHub MCP Server (repository-read, issue-write, pull-request-write) Vercel MCP Server (project-read, deployment-read, logs-read)

Questions

Straight answers before you start
Can the agent deploy to production?
Production deploys on Vercel normally happen when you merge to your production branch, and this setup leaves merging to you. Keep branch protection on and do not give the agent permission to merge.
Do I need a paid Vercel plan?
Vercel's MCP server works with your existing account, and preview deployments are available on the Hobby plan. Team features and some log retention depend on your plan, so check Vercel's pricing page for details.
Should I use Claude Code or Cursor?
Both can edit code and call MCP servers. Claude Code fits terminal-based work and can run your tests and git commands; Cursor suits you if you prefer to watch edits in the editor.
What if the build passes but the fix is wrong?
A green build only proves the code compiled and deployed. Test the preview yourself or ask the agent to add a test that reproduces the bug before you merge.

Tools in this setup

The products involved