PulseLight × Cursor

Launch readiness inside Cursor

PulseLight's MCP server tells Cursor what's blocking launch in your repo, then hands it a paste-ready fix prompt — restraint-engineered so Cursor doesn't refactor half the codebase while it's there.

Cursor is the AI-first code editor founders are shipping with.

Install

Once @pulselight/mcp publishes to npm, the flow below is the full install. Until then, use the dashboard's Copy-for-Cursor button on each blocker — same prompt, no install required.

Early access

@pulselight/mcp is in early access — npm publish in flight. The snippet below previews the install once it's live; tracking shipping at /changelog.

# Preview — once @pulselight/mcp publishes to npm:

# 1. Install the MCP server
npm install -g @pulselight/mcp

# 2. Mint a token in the dashboard:
#    app.pulselight.io → Settings → API tokens

# 3. Wire it into Cursor — add to ~/.cursor/mcp.json:
{
  "mcpServers": {
    "pulselight": {
      "command": "pulselight-mcp",
      "env": {
        "PULSELIGHT_TOKEN": "pul_…",
        "PULSELIGHT_WORKSPACE_ID": "ws_…"
      }
    }
  }
}

How it works

  1. 1

    Ask Cursor what to fix next

    In Cursor chat, prompt it to use pulse_status. Cursor calls the MCP server, which returns the launch verdict, the top 3 blockers, and a per-pillar status — grounded in real PulseLight data, not a hallucinated checklist.

    Use pulse_status to tell me what's blocking this repo from shipping.
  2. 2

    Pick a blocker, fetch the fix prompt

    Cursor calls pulse_top_blockers to get full founder copy + evidence, then pulse_fix_prompt to fetch the v2 restraint-engineered prompt for the chosen finding.

  3. 3

    Apply the fix, re-scan

    Cursor applies the diff exactly as the prompt directs. Push to your branch — the PulseLight GitHub App auto-runs a fresh scan on push, and Cursor’s next pulse_status call sees the new verdict. Green re-scan = the only proof. Repeat for the next blocker.

FAQ

Does PulseLight read my code?
It scans the repo you connect via the PulseLight GitHub App. Findings stay scoped to your workspace; the share-token system is opt-in for anything public.
Why an MCP server instead of a Cursor extension?
MCP is the open protocol Anthropic, Cursor, and others have aligned on. One server works in every MCP-aware tool — Cursor today, Claude Code, future editors — without us shipping per-host extensions.
Do I need a paid plan?
No — Pro is enough for solo founders preparing to launch. Growth and Studio unlock more Connected Checks and projects. 14-day Studio trial included.

Ready when you are

14-day Studio trial. No card up front. Cancel any time.