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.
Install
Early access
# 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
Ask Cursor what to fix next
Use pulse_status to tell me what's blocking this repo from shipping.Pick a blocker, fetch the fix prompt
Apply the fix, re-scan
FAQ
- Does PulseLight read my code?
- Why an MCP server instead of a Cursor extension?
- Do I need a paid plan?