Install in Cursor

Install in Cursor

slipstream's MCP server runs in Cursor as a first-class MCP tool provider. You get the full sp_* toolset and the local dashboard. The Claude Code plugin surface (skills, slash commands, hooks, statusline) is not available here; the dashboard browser tab is the universal UI.

Requirements

• Cursor 0.45 or newer with the MCP feature enabled (Settings → Features → MCP).
• Node 20 or newer on your PATH.
• A local clone of slipstream, built once.

Check Node from the Cursor integrated terminal:

node --version

Build the server once

git clone https://github.com/sarmakska/slipstream
cd slipstream
npm install
npm run build

This produces dist/mcp/index.js. Note the absolute path; you will paste it into the Cursor config.

Locate the MCP config file

Cursor reads MCP servers from either a per-project file or a per-user file.

• Per-project (recommended for slipstream so the server points at the same repo as the workspace): .cursor/mcp.json at the repo root, on every OS.
• Per-user:
  • macOS: ~/.cursor/mcp.json
  • Linux: ~/.cursor/mcp.json
  • Windows: %USERPROFILE%\.cursor\mcp.json

Settings → MCP also shows the resolved file and offers an "Edit configuration" button.

Paste the slipstream block

{
  "mcpServers": {
    "slipstream": {
      "command": "node",
      "args": ["/absolute/path/to/slipstream/dist/mcp/index.js"]
    }
  }
}

If the file already has an mcpServers block, add the slipstream key alongside the existing entries.

Restart Cursor

Fully restart Cursor (Cmd/Ctrl + Q, then reopen). On startup Cursor spawns the slipstream MCP server over stdio and the dashboard server boots automatically.

Verify the tools appear

Open the Cursor chat (Cmd/Ctrl + L) and ask:

list your MCP tools

You should see the 14 sp_ tools: sp_map, sp_symbol, sp_lines, sp_search, sp_search_memory, sp_timeline, sp_observations, sp_lessons, sp_savings, sp_budget, sp_dashboard, sp_remember, sp_recall, sp_mindmap.

Then ask the agent to call sp_dashboard. It returns a 127.0.0.1 URL. Open it in your browser; the live dashboard fills in as the agent works.

Troubleshooting

• No tools listed. Open Settings → MCP and check the slipstream row shows a green dot. Click it to see the server log.
• "command not found: node" in the server log. Cursor inherited a PATH without Node. Set an absolute path, for example "command": "/usr/local/bin/node" on macOS or "C:\\Program Files\\nodejs\\node.exe" on Windows.
• Server starts then exits immediately. Re-run npm run build in the slipstream clone; the path in args must point at a built dist/mcp/index.js, not the TypeScript source.
• Dashboard tab is empty. Ask the agent to call sp_map first; the dashboard reflects MCP activity, so it stays quiet until a tool runs.
• Tools listed but the agent refuses to call them. Cursor's agent mode must be on (auto-run for tool use). Pure ask-mode will not call MCP tools.

---

SarmaLinux . sarmalinux.com . Repository