fix: mcp not authenticated

Open
#13,992 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale

Research direction

Start by reproducing the issue with ~/.cursor/mcp.json in Cursor using the provided Vercel MCP URL and authentication steps. Determine whether the failure occurs in Cursor's callback handling or Vercel MCP authentication; done means the browser flow returns to Cursor and the server leaves the "Needs authentication" state.

Written by the indexing model from the issue text.

Description

Hi,

Vercel mcp cannot be authenticated on Cursor.

I know this is not vercel cli bug, but don't know where to post.

Environment

  • macOS: 15.6.1(24G90)
  • Cursor: 1.6.45 (2025-09-22T18:22:38.013Z)
  • Config file: ~/.cursor/mcp.json
    {
      "mcpServers": {
        "vercel": {
          "url": "https://mcp.vercel.com"
        }
      }
    }

Steps to Reproduce

  1. Add the above configuration to ~/.cursor/mcp.json.
  2. In Cursor, Vercel MCP shows "Needs authentication".
Image
  1. Click "Connect" → Browser opens with Vercel.
  2. Successfully log in → Cursor reopens.
Image

(Safari is asking "Do you want to allow this website to open 'Cursor.app'?")

  1. A prompt appears from Cursor
Image
  1. Click "Open".
Actual Behavior
  • After clicking "Open", nothing happens.
  • Vercel MCP remains stuck in "Needs authentication" state.
Expected Behavior
  • After authentication, Cursor should connect successfully to Vercel MCP.
Notes

Unclear whether this is a Cursor bug or a Vercel MCP bug.

Dominant language
TypeScript
Stars
16.3k
Forks
3.8k
Avg merge
2m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/vercel

All issues in vercel/vercel

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.