[Jordan Harband (ljharb)]

The Cursor plugin now declares https://mcp.socket.dev/ in .cursor-plugin/mcp.json, so users sign in to Socket in the browser instead of pasting one org's API key. The manifest also gets a display name, a logo, and a rule that tells the agent when to use the Socket MCP tools and how to fall back to the CLI if sign-in does not complete.

The shipped-content gates now scan .cursor-plugin/rules, including .mdc files, because agents read and obey them.

Known limitation

Hosted OAuth does not complete in current Cursor versions. The socket-mcp README compatibility matrix lists Cursor 3.22.12 hosted OAuth as failing. The cause is described in the Cursor forum report: Cursor shows Authenticate only when the server returns 401 during connect. The live mcp.socket.dev answers an unauthenticated initialize with 200 and returns 401 only on tools/call.

The fix is on the server side:

• fix(oauth): send a bare Bearer challenge when a request has no credentials socket-mcp#230 adds a bare WWW-Authenticate challenge on connect, with tests.
• socket-mcp main already returns 401 on an unauthenticated initialize, but production mcp.socket.dev runs different code. The hosted deployment must be updated as well before Cursor can sign in.

Until then, the README and the Cursor rule say this plainly and point users to the CLI sign-in (pnpm dlx socket login).

Testing

• Rebased onto main after feat(auth): connect to Socket through browser sign-in #25 and build: drop the fleet pack and own the repo tooling #28 landed.
• pnpm run check passes, and all repo tests pass locally: 56 files, 1253 tests. pnpm run generate:check reports the generated files are up to date.
• The push ran the repo's git hooks.
• Not tested in Cursor itself.

---

Note

Medium Risk
Expands agent-obeyed shipped instructions and connects users to an external OAuth MCP endpoint; config avoids embedding secrets but auth and dependency-check behavior in Cursor sessions depend on this wiring.

Overview
The Cursor plugin now wires in Socket's hosted MCP at https://mcp.socket.dev/ (OAuth in the browser, no API key in config) instead of an empty MCP stub, and the manifest adds display name, logo, and rules that tell the agent when to run depscore / org tools and how to fall back to the Socket CLI if Cursor OAuth fails.

README documents the Customize → Authenticate flow and the known Cursor OAuth limitation.

Repo tooling follows suit: the Cursor plugin generator emits the OAuth-only MCP JSON, requires the hand-maintained logo and rules paths, and tests assert no credentials ship. Shipped-content gates now treat .cursor-plugin/rules (including .mdc files) like other agent-obeyed surfaces for fleet-leak and injection scans.

^{Reviewed by Cursor Bugbot for commit f88cdb7. Configure here.}

[John-David Dalton (jdalton)]

Might have some conflicts if multiple prs land but just iron them out as you go