Connect your editor (MCP)
Each running project exposes an MCP server, so Claude Code, Cursor or VS Code can read the notes you left in the browser and mark them done. One button writes the config.
Why connect an editor
PulseDev already runs your coding agent when you send a note from the widget. Connecting your editor is a second, optional route: it lets the agent inside your editor pick up the same annotations. That is useful when you want to batch several notes into one session, or when you are already working in the editor and want it to look at what you flagged on the page.
Use Connect editor (MCP)
Open the project in the PulseDev app, start its server, and click Connect editor (MCP) under Automatic setup. The app writes a pulsedev entry into three project-level config files, creating them if needed and keeping any other servers already listed:
| File | Editor | Key |
|---|---|---|
.mcp.json | Claude Code | mcpServers.pulsedev |
.cursor/mcp.json | Cursor | mcpServers.pulsedev |
.vscode/mcp.json | VS Code | servers.pulsedev |
The entry points at the project's /mcp endpoint and sends the project token as a bearer header. For Claude Code it looks like this:
{ "mcpServers": { "pulsedev": { "type": "http", "url": "http://localhost:3899/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } }}If one of the files exists but isn't valid JSON, the app stops and tells you which one. Fix or delete it and click the button again.
Reload the editor
Editors read MCP config when a session starts. Restart Claude Code in the project folder, or reload the Cursor or VS Code window. Claude Code asks you to approve servers from a project .mcp.json the first time it sees them.
The PulseDev server for that project has to be running for the tools to answer. If the editor reports the server as unreachable, start the project in the app.
The tools it exposes
| Tool | What it does |
|---|---|
list_annotations | Lists annotations for the project, newest first. Optional status filter and limit (default 50, max 200). Read only. |
get_annotation | One annotation with its feedback, conversation, changes and activity. Read only. |
get_element_context | What the widget captured for the clicked element: URL, selectors, site context (styles, matched CSS rules, console and network logs) and the element screenshot as an image when one was saved. Read only. |
update_annotation_status | Sets the status, with an optional reply (up to 5000 characters) and summary (up to 1000) that show up in the widget. |
Statuses are queued, running, applying, review, completed, failed and closed. Status changes are pushed to the widget over its live connection, so the open tab shows them without a reload.
The MCP tools don't write code themselves. Your editor's agent makes the edits with its own tools, under its own permission rules. PulseDev's Approve step only applies to runs started from the widget.
A typical prompt
Use the pulsedev MCP tools. List the queued annotations, read the elementcontext for each one, fix them one at a time, and mark each one completedwith a one-line summary.Other MCP clients
The server speaks MCP over streamable HTTP with JSON responses at http://localhost:<port>/mcp, using the project port the app shows. Any client that supports HTTP servers with custom headers can connect: give it that URL and an Authorization: Bearer <project token> header. Only POST is supported; there is no SSE stream on this endpoint.
If you remove and re-add a project, it may get a new port and token. Click Connect editor (MCP) again to rewrite the files.