Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open Beginner friendly
  • Is something wrong?
#460 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
developer-experience

Research direction

Read apps/cursor/src/lib/github-plugin/parse.ts and apps/cursor/src/components/plugins/detail/mcp-section.tsx, especially resolveMcpConfig and the call that supplies the component name. Use the provided .mcp.json shape to check how the server key reaches the Cursor deeplink. Done means each server's install link uses its own .mcp.json key, including when a plugin has multiple servers.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
4k
Forks
668
Avg merge
5h 2m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/community-plugins

All issues in cursor/community-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.