feat(cursor): bundle the local Glean MCP server

[eshwar-sundar-glean]

Summary

Emit the folded vnext/local Glean MCP server in the Cursor glean plugin.

Cursor previously excluded the shared mcp/ component, so it only received the portable skills, agents, and rules and required a separately configured remote Glean MCP server. This change enables the same local MCP adapter already shipped by the Claude Code and Codex glean plugins.

Changes

• Remove mcp from Cursor's exclude list; continue excluding hooks and scripts.
• Cursor now emits:
  • .mcp.json
  • mcp/start.mjs
  • mcp/dist/index.js
  • mcp/package.json
• Update Cursor setup documentation to use the bundled local Glean MCP server and harness-driven setup.
• Update repository documentation to reflect that Claude, Cursor, and Codex bundle the local adapter.

The output remains the existing glean plugin; no separate glean-vnext plugin is introduced.

Verification

• npm test — all target builds and validation passed
• MCP typecheck passed
• MCP tests: 195 passed
• No-shell guard passed
• Cursor manifest contains mcpServers: "./.mcp.json"
• Cursor MCP artifacts verified
• git diff --check passed

[glean-it]

Issue: The Cursor target now includes the shared MCP configuration, but that configuration invokes ${CLAUDE_PLUGIN_ROOT}/mcp/start.mjs, which is Claude-specific and is not a valid Cursor plugin path. The bundled MCP server therefore will not start in Cursor.

Suggested fix: Add overrides/cursor/glean/mcp/config.json using a Cursor-compatible entry such as command: "node", args: ["./mcp/start.mjs"], and cwd: ".", or otherwise provide a resolvable Cursor-specific MCP entrypoint.

_{🔧 Tag @ glean-for-engineering to fix or click here to fix in Glean}

_{💬 Help us improve! Was this comment helpful? React with 👍 or 👎}