MCP server installation doesn't take name into account

[StefELianos]

Hello,

I submitted a plugin containing an MCP https://cursor.directory/plugins/apptweak-mcp-plugins
When I add it to Cursor via the add to cursor button, Cursor opens up properly, but the name of the MCP appears as server instead of the name submitted.

[StefELianos]

Opened a PR #417

[Leestex]

Confirming this, with two additions — the submitted component name is stored correctly and still ignored, and for a plugin with more than one MCP server the fallback does more than mislabel: it makes the install buttons collide.

Listing: https://cursor.directory/plugins/qlane — two MCP servers, one per data region.

The stored component names are correct (read from the edit form):

componentNames: ["qlane-eu", "qlane-us", "test-local-changes"]
componentTypes: ["MCP Server", "MCP Server", "Skill"]

The generated deeplinks are not (read from the live listing's href, config base64-decoded):

Add to Cursor #1   name=server   {"type":"http","url":"https://mcp-eu.qlane.ai/api/mcp"}
Add to Cursor #2   name=server   {"type":"http","url":"https://mcp-us.qlane.ai/api/mcp"}

So the config payload is per-server and correct, while name is server for both. That matches the diagnosis in #417 — the name comes from the config structure rather than the submitted component name — and shows the stored name is present and simply unused, so no author-side edit can work around it.

Why the multi-server case is worse than a cosmetic label. Both buttons resolve to the same server name, so installing the second overwrites the first. A user cannot end up with both. For a region-split plugin this is the whole point of the listing: the two entries differ only by region, the name is the only cue telling them apart, and after install neither is identifiable. The fix in #417 resolves this too — flagging it in case the multi-server impact is useful for prioritising.

Reproduce: open the listing above, inspect either Add to Cursor anchor's href, and base64-decode the config parameter.

[ergoveritas1-alt]

Confirming this on the live CertScore.ai MCP Light listing:

• Listing: https://cursor.directory/plugins/certscoreai-mcp-light
• Displayed MCP component name: CertScore.ai
• Generated deeplink: cursor://anysphere.cursor-deeplink/mcp/install?name=server&config=...
• Expected deeplink name: CertScore.ai (URL-encoded as needed)
• The decoded config is otherwise correct: {"type":"streamable-http","url":"https://mcp.certscore.ai/mcp/light"}

This confirms the stored/displayed component name is available but is not used when generating the install link, matching the diagnosis in #417. There is no author-side metadata workaround because the listing already shows the intended component name.