May 5, 2026

Installing an MCP server in Cursor (the one-click way)

Cursor's MCP support shipped in 2024. Here's the cleanest install path: deeplink, hosted endpoint, no clone, no env vars.

Cursor supports MCP servers natively. The install path most tutorials show — clone a repo, edit ~/.cursor/mcp.json with an absolute path to a stdio binary — works, but it’s the slow path. There’s a one-click flow.

The fast install

A cursor:// deeplink. Click it in your browser, Cursor opens, MCP installs.

The deeplink encodes a config object — { "url": "https://your-mcp.example.com/mcp" } — base64’d into the URL. Cursor reads the URL field, reaches out to the hosted endpoint, lists the tools, you’re done.

For ChiefLab, the deeplink is on the homepage as the “Add to Cursor” button. Anonymous install — no key required to start. Your agent’s first authenticated call returns a chieflab_signup_workspace pointer that mints a workspace and key on your behalf.

Why the hosted path beats stdio

  • No git clone, no npm install, no Node version issues
  • No absolute path in your config (which breaks on every machine)
  • Server-side updates ship to all installs immediately, no re-clone needed
  • Works behind any firewall that allows HTTPS (which is all of them)

After install

In a Cursor chat, mention the tool by intent and Cursor’s agent picks it. For ChiefLab:

I just shipped this product at https://yoursite.com.
Use ChiefMO to plan and queue the launch.

You’ll get a launch pack + signed reviewUrl. Approve in the browser. Posts go live.

Add ChiefLab to Cursor (one click) → · All MCP runtimes →

← all posts