Developers · Cursor capture

Capture from Cursor.

5 minutes. Save engineering discussions, code snippets, and decisions to Pulse without leaving the editor.

Step 1, create an MCP token

Generate one at Settings → Integrations → MCP tokens, label it (e.g. “Cursor, dev workstation”), copy it once.

Step 2, add Pulse to Cursor MCP config

Two valid locations:

Global (recommended): ~/.cursor/mcp.json
Per-project: .cursor/mcp.json in the project root

{
  "mcpServers": {
    "pulse": {
      "url": "https://pulsehq.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer pulse_mcp_PASTE_YOUR_TOKEN_HERE"
      }
    }
  }
}

Step 3, reload MCP servers

Cmd/Ctrl + Shift + P, then run MCP: Reload Servers. You should see pulse with 25 tools listed (15 read incl. pulse_recall + 7 capture + pulse_remember / pulse_forget + pulse_propose_action).

Step 4, your first capture

Open the AI chat, work through an engineering question, then say:

Save this conversation to Pulse, tag it auth-middleware-refactor.

For code snippets, pass a language hint so Pulse renders syntax highlighting: “Save this TypeScript code to Pulse, language: typescript.”

For decisions: “We’ve decided to use jose instead of jsonwebtoken. Save the decision to Pulse.”

Tips

Mention a topic name to auto-group captures under a Pulse Topic.
Long debugging sessions: capture the conclusion as a decision rather than the full transcript. Denser and more reusable for the team.
Per-project mcp.json scopes the Pulse connection to that project; use it if you keep work + personal projects separate.