Remote MCP (mcp.socket.dev) fails OAuth Dynamic Client Registration in Claude Desktop connectors

Offen
  • Stimmt etwas nicht?
#223 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
nodejs, typescript
Bereich
api, authentication

Rechercherichtung

The failure is in the remote OAuth Dynamic Client Registration flow for https://mcp.socket.dev/, not in a named source file, so start by checking whether this repo contains the server code at all. Fetch /.well-known/oauth-authorization-server and confirm whether a registration_endpoint is advertised and accepts the redirect URI https://claude.ai/api/mcp/auth_callback. Done means Claude Desktop registers and completes sign-in, or the maintainers confirm the fix belongs in an external service.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

Adding the Socket MCP server as a remote connector in Claude Desktop (https://mcp.socket.dev/) fails at the OAuth Dynamic Client Registration step. Claude can't register with Socket's authorization server, so the connector never authenticates.

Error

Couldn't register with Socket's sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: "ofid_03e64c60d9cf295d"

Earlier occurrence (2026-09-17): ofid_325a1efc5e21b2cd

Steps to reproduce

  1. In Claude, open Customize → Connectors.
  2. Select Add custom connector, enter https://mcp.socket.dev/ as the server URL (Team/Enterprise plan: added by an org owner via Organization settings → Connectors).
  3. For OAuth Client, leave it on Register automatically (no Client ID supplied).
  4. Select Connect.

Expected: Socket authorization flow opens, the client registers and the connector connects.
Actual: The registration error above appears; the authorization screen never opens.

Other methods tried (also failing)

  • mcp-remote via npx in claude_desktop_config.json: 
    {
  "mcpServers": {
    "socket-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.socket.dev/"]
    }
  }
}
    OAuth completes, but the redirect to localhost:<port> fails because no server is listening to accept it.
  • HTTP transport with URL https://mcp.socket.dev/: clicking Connect doesn't open the OAuth screen at all.

Environment

  • Client: Claude Desktop (macOS), Claude Team/Enterprise organization
  • Server: remote https://mcp.socket.dev/
  • Last reproduced: 2026-10-14

Context

Reported through Socket support (Zendesk #3814) on 2026-08-21. Support mentioned it split into three engineering tickets, two of which were closed; the remaining DCR failure is still reproducible. The local DXT extension with an API token was suggested as a workaround, but we'd like the remote OAuth connector working so it can be rolled out org-wide via Connectors.

Possibly worth checking: whether the authorization server's registration_endpoint (RFC 7591 Dynamic Client Registration) is advertised in /.well-known/oauth-authorization-server and accepts Claude's redirect URIs (https://claude.ai/api/mcp/auth_callback).

Vorherrschende Sprache
TypeScript
Sterne
137
Forks
45
Ø Merge
12 T. 16 Std.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus SocketDev/socket-mcp

Alle Issues in SocketDev/socket-mcp

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.