MCP "Add to Cursor" deeplink always uses name=server instead of the .mcp.json key #460

What happens: on a plugin detail page, the "Add to Cursor" button for an MCP server installs it under the name server instead of the key from the repo's .mcp.json. If a plugin has two servers, both buttons use name=server, so installing both collides.

Example: https://cursor.directory/plugins/financialfilings-mcp. Our .mcp.json is the standard shape:

{ "mcpServers": { "financialfilings": { "type": "http", "url": "https://mcp.financialfilings.com/mcp" } } }

The button links to cursor://anysphere.cursor-deeplink/mcp/install?name=server&config=....

Cause:

• apps/cursor/src/lib/github-plugin/parse.ts: the scanner unwraps mcpServers, stores each server's inner config as content, and keeps the key only in the component's name. metadata has no name.
• apps/cursor/src/components/plugins/detail/mcp-section.tsx, in resolveMcpConfig: content therefore has no mcpServers wrapper, so it falls through to return { name: (meta?.name as string) ?? "server", config: parsed }, and the name is always "server".

Suggested fix: pass the component's name into resolveMcpConfig and use it before the "server" fallback, e.g. name: (meta?.name as string) ?? mcp.name ?? "server". Or store name in metadata at parse time.