Fix MCP install: preserve server name and show paste-ready config

[dilpreetkaur-bluesky]

---

Note

Low Risk
UI and plugin-ingestion metadata only; no auth, migrations, or API contract changes beyond correcting MCP install naming and displayed config shape.

Overview
Fixes repo-ingested MCP plugins installing under the generic name server and showing config that users cannot paste into ~/.cursor/mcp.json.

Ingestion (parse.ts): When unwrapping mcpServers, the server key is now stored in component metadata.name so the install flow can recover it after content is saved as the bare inner config.

Plugin detail (mcp-section.tsx): resolveMcpConfig takes a fallbackName (the component name) so install deeplinks use the real server name when metadata was missing—fixing existing listings without a re-scan. Preview and Copy now show the mcpServers-wrapped JSON (valid for manual mcp.json edits); deeplinks still pass the inner config only. Copy/help text clarifies that the block is paste-ready for ~/.cursor/mcp.json.

^{Reviewed by Cursor Bugbot for commit 777c4f5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

@dilpreetkaur-bluesky is attempting to deploy a commit to the Anysphere Team on Vercel.

A member of the Team first needs to authorize it.

[dilpreetkaur-bluesky]

@ericzakariasson mind taking a look at this one? It's a small fix (+25/-9) to two bugs in repo-ingested MCP plugin listings:

1. The config preview strips the mcpServers wrapper, so copying it into ~/.cursor/mcp.json produces an invalid file that won't load. We had a customer hit this on our own listing and work out the fix themselves.
2. Install registers the server under the generic name server instead of its real key, because the ingestion step drops it when unwrapping.

The fallbackName change means existing listings are fixed without a re-scan.

Bugbot is green; the only red check is the Vercel preview, which can't build because it's a fork PR and needs an Anysphere member to authorize.