Official Meta WhatsApp Business Tools MCP fails OAuth initialization in Cursor Web

I’m connecting Meta’s official WhatsApp Business Tools MCP through cursor.com/agents.

Server: https://mcp.facebook.com/whatsapp_business_tools

The server saves successfully and appears as “Needs authentication”. Clicking Connect immediately produces “Could not obtain authentication URL.”

No Facebook login window opens.

The OAuth Client ID, Client Secret, and HTTP headers are empty, consistent with Meta’s documented OAuth setup.

Meta Social Technologies MCP and Meta Ads MCP both authenticate successfully in the same Cursor account.

Please investigate OAuth authorization URL discovery for this endpoint and whether the connection is affected by rollout restrictions.

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hi @Juliuscl,

This one is on Meta’s side. When you click Connect, Cursor tries to register itself as an OAuth client with Meta’s WhatsApp Business Tools server, and Meta refuses with “Dynamic registration is not available for this client” (it only pre-approves a few clients right now). Without that registration there’s no login page to open. The team knows about this limitation with Meta’s servers.

Meta Ads most likely works for you because that server has its own Client ID set. You can do the same for WhatsApp:

  1. In your Meta app at developers.facebook.com, add https://www.cursor.com/agents/mcp/oauth/callback as a valid OAuth redirect URI.
  2. On cursor.com/agents, edit the WhatsApp Business Tools server and enter the app’s App ID as the OAuth Client ID (and the App Secret as the Client Secret if your app uses one).
  3. Click Connect again. The Facebook login window should open.