Skip to content

feat(auth): connect to Socket through browser sign-in - #25

Merged
Jordan Harband (ljharb) merged 1 commit into
SocketDev:mainfrom
ljharb:feat/oauth-connect
Nov 5, 2026
Merged

Jordan Harband (ljharb) merged 1 commit into
SocketDev:mainfrom
ljharb:feat/oauth-connect

Conversation

@ljharb

@ljharb Jordan Harband (ljharb) commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Add a socket-connect plugin that bundles the hosted Socket MCP server (https://mcp.socket.dev/). Agents sign in with OAuth (dynamic client registration + PKCE against api.socket.dev), so users no longer paste an organization API token to use Socket from Claude Code, Cursor, or Gemini.

  • socket-connect: sign-in steps per agent, choosing among the organizations a sign-in covers, and linking the CLI for scans
  • marketplace: socket-connect entry with an inline mcpServers block; auth-dependent plugins depend on it so one sign-in serves them all
  • cursor/gemini: ship the same server; a structural test keeps the URL identical across all three manifests
  • skills: prefer browser sign-in; keep API tokens for CI; the user runs socket login in their own terminal, never pasting tokens into chat

Note

Medium Risk
Changes how users authenticate across agent plugins and skill instructions (OAuth MCP + CLI login guidance), though impact is limited to documentation and manifest config rather than application runtime code.

Overview
Introduces socket-connect, a new skill and Claude marketplace plugin that bundles the hosted Socket MCP server (https://mcp.socket.dev/) so agents authenticate with OAuth in the browser instead of pasting organization API keys.

Plugin wiring: Claude marketplace adds socket-connect with inline mcpServers; scan, inspect, setup, fix, and related plugins declare dependencies: ["socket-connect"]. Cursor’s generated .cursor-plugin/mcp.json and gemini-extension.json now ship the same MCP URL, with a structural test keeping all three manifests aligned via SOCKET_MCP_URL in generate-cursor-plugin.mts.

Skill and doc updates: Shared CLI setup text and socket-setup, socket-scan-setup, socket-inspect, and fix skills steer users to /socket-connect and user-run pnpm dlx socket login (interactive TTY), reserve SOCKET_CLI_API_TOKEN for CI, and forbid pasting tokens in chat. socket-inspect prefers MCP depscore when connected. README and agents/README.md document the new plugin and de-emphasize demo-token / dashboard API-key flows for local agent use.

Reviewed by Cursor Bugbot for commit e1fec9c. Configure here.

Add a socket-connect plugin that bundles the hosted Socket MCP server
(https://mcp.socket.dev/). Agents sign in with OAuth (dynamic client
registration + PKCE against api.socket.dev), so users no longer paste an
organization API token to use Socket from Claude Code, Cursor, or Gemini.

- socket-connect: sign-in steps per agent, choosing among the
  organizations a sign-in covers, and linking the CLI for scans
- marketplace: socket-connect entry with an inline mcpServers block;
  auth-dependent plugins depend on it so one sign-in serves them all
- cursor/gemini: ship the same server; a structural test keeps the URL
  identical across all three manifests
- skills: prefer browser sign-in; keep API tokens for CI; the user runs
  `socket login` in their own terminal, never pasting tokens into chat

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very cool 🤩

@ljharb
Jordan Harband (ljharb) merged commit 24cbd3d into SocketDev:main Nov 5, 2026
10 checks passed
@ljharb
Jordan Harband (ljharb) deleted the feat/oauth-connect branch November 5, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants