Integration Overview
How Cursorist connects to Cursor IDE through deeplinks and MCP.
Cursorist uses two mechanisms to push content into Cursor IDE: deeplinks for instant one-click installs, and the Model Context Protocol (MCP) for agent-powered plugin workflows. This section covers both.
The Two Channels
| Channel | Best For | How It Works |
|---|---|---|
| Deeplinks | Single rule or MCP config install | A cursor:// URL embeds the content directly — Cursor reads it from the URL, no server fetch needed |
| MCP Server | Agent-driven plugin management | An MCP server runs locally and exposes plugin operations (list, install, upgrade) to Cursor's AI agent |
| CLI | Full plugin bundles | cursorist plugin install downloads all assets (rules, skills, MCP config, hooks) at once |
When to Use What
You want to share a single rule with a colleague?
Use a rule deeplink. It creates a .cursor/rules/NAME.mdc file in their project after they confirm.
You want to set up an MCP server for a team?
Use an MCP install deeplink. It adds the server config to .cursor/mcp.json with one click.
You want full plugin lifecycle management? Set up the MCP server so Cursor's agent can list, install, and upgrade plugins directly in chat.
You want to install a complete plugin bundle?
Use the CLI: cursorist plugin install org/team/plugin. This pulls all components at once.
How Deeplinks Work Under the Hood
Cursor supports a custom cursor:// protocol. When a user clicks a deeplink:
- The OS routes the URL to Cursor
- Cursor parses the protocol path and query parameters
- A confirmation dialog shows the user what will be created
- On confirm, Cursor writes the file(s) to the project
No network requests are made by Cursor — all content is embedded in the URL itself. This means there's an ~8,000 character URL limit for rule content.
Next Steps
- Rule Deeplinks — Format, constraints, and code examples
- MCP Install Deeplinks — One-click MCP server setup
- MCP Server Configuration — Full MCP server setup for agent workflows