针对Cursor上mcp一键安装和 OAuth 支持

[1405942836]

Cursor最新更新日志：https://www.cursor.com/en/changelog/1-0

https://docs.cursor.com/deeplinks
可以生成深度链接，集成到开发文档或者READMD.md文档中。
对于 MCP 开发人员，您可以通过在文档中添加 “Add to Cursor” 按钮来使用户轻松访问您的服务器。

https://docs.cursor.com/tools
还可以提交到Cursor的tool列表中。

[chengzeyi]

Thanks for the suggestion, and sorry for the very late reply. Both points still stand and are worth doing:

1. Add to Cursor deeplink — we'll add a one-click install button to the README.
2. Cursor tools directory — we'll go through that submission process.

The server itself has since been rewritten from Python to TypeScript (npx -y @wavespeed/mcp, published in the official MCP Registry as ai.wavespeed/mcp), so the deeplink will point at that. I'll update here once it ships.

[chengzeyi]

Both parts, with what actually shipped and what didn't.

1. "Add to Cursor" button — shipped

The README now opens with a one-click install button: 71f1c13

Cursor's docs don't spell out the deeplink format, so it was derived from servers that already ship the button (upstash/context7, exa-labs/exa-mcp-server, ref-tools/ref-tools-mcp, joshuayoes/ios-simulator-mcp). The shape is:

https://cursor.com/install-mcp?name=<server-name>&config=<base64 of the JSON config object>

Ours encodes:

{"command":"npx","args":["-y","@wavespeed/mcp"],"env":{"WAVESPEED_API_KEY":"wsk_..."}}

The env placeholder is deliberate — the button lands you in Cursor with the key field present and obviously needing a value, rather than with a config that looks complete and then fails on the first call. If you already ran wavespeed login, you can clear that field; the server falls back to the CLI's stored credentials.

2. Directory listing — partly not automatable

The repo behind cursor.directory moved. pontusab/directories now redirects to cursor/community-plugins — it's owned by the Cursor org now, not stale.

The catch, from its README: "All content is submitted through the website — no pull requests needed for data." Listings live in a Supabase database, not in the repo, so there is no PR path. Submission is cursor.directory/plugins/new, requires a GitHub or Google sign-in, and each submission gets an automated security scan plus a manual admin review. Someone on our side with an account has to do that by hand; I'm not creating one automatically. It's queued.

One thing that will help when we do submit: the directory auto-detects components from the repo, and it reads MCP servers from an mcp.json at the repo root (the Agent Plugins standard Cursor adopted). We don't ship one yet — adding it should make the listing pick up the server without manual entry. Tracking that separately.

On the Cursor Marketplace (the official one, cursor.com/marketplace): no public submission path exists. Cursor's docs say plugins there are "submitted through the Cursor team" and manually reviewed. That's an outreach thing, not something we can file.

So: button is live now, community directory needs a manual submit that's on our list, official marketplace needs a conversation with Cursor.

Thanks for the report — the deeplink was worth doing and we wouldn't have gotten to it this week otherwise.