Project-specific Vercel MCP OAuth succeeds, but build and runtime logs return 403

I’m seeing a team-scope authorization failure with the official Vercel MCP server from Codex.

The project-specific connection uses https://mcp.vercel.com/reitojike/stage-tracker. OAuth completed successfully. I also reauthenticated in Codex. At 2026-09-25 10:53:16–18 UTC, I confirmed that the calls were made through the project-specific connection, rather than a separate general Vercel connection:

list_deployment_events for Production build logs returned 403: “Not authorized: Trying to access resource under scope ‘reitojike’.”

get_runtime_logs for Production returned 403 indicating insufficient permission to access the resource.

I am the team Owner, and 2FA is active. The Production deployment is Ready. I can read both sets of logs in the Vercel Dashboard and through the authenticated Vercel CLI. The MCP connection appears in my account’s “Sign in with Vercel” connections with project and deployment permissions.

Could the Vercel team check whether the MCP OAuth grant has effective access to the reitojike team, and why the project-specific MCP endpoint rejects these log reads? I can provide the team, project and deployment IDs, request identifiers, or sanitized error details through a secure channel if needed.

This appears related to another Codex MCP team-scope 403 report, though I have confirmed the failure on a project-specific connection.

Hi there! I'm just a bot here to share some info that might help you before a human arrives.

If your account is eligible, you can use our new self-service recovery flow:

Go to vercel.com/login
Choose to sign in using the email + one-time password (OTP) option.
Select Use another sign-in method
Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account
Follow the remaining prompts to complete the recovery process

If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access.

If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future. There's no need to open an additional case if you already have one open.

Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.