“Save this to Pulse” works inside every AI client.
Wire Pulse into Claude Desktop, Cursor, Codex CLI, or Claude Code and the AI conversations + decisions your team has with their tooling flow back into your workspace.
The MCP surface
Pulse exposes twenty-seven MCP tools: fifteen read tools (search_company, find_expert, pulse_workspace_snapshot, plus the filesystem-style pulse_ls / pulse_tree / pulse_grep / pulse_glob, and more), seven capture tools (pulse_capture_conversation, pulse_capture_snippet, pulse_capture_decision, pulse_capture_commitment, pulse_capture_failure_case, pulse_capture_note, pulse_suggest_skill), three personal-memory tools (pulse_remember, pulse_recall, pulse_forget) that carry your own private memory + style across tools, and pulse_propose_action, which drafts a real action into the human approval inbox and never executes anything itself. Wire them into Claude Desktop, Cursor, Codex CLI, or Claude Code and the AI conversations + decisions your team has with their tooling flow back into your workspace. Opt-in auto-capture is available for Claude Code (a SessionEnd hook); Cursor history syncs via a manual export (npx cursor-history piped to the sync script). Auto-pushed sessions land AUTHOR_ONLY in your workspace.
- Claude DesktopAdd Pulse as an MCP server in Claude Desktop. Say "save this to Pulse" inside a chat and the conversation becomes a Document with the AI_CLAUDE_DESKTOP source, runs through extraction, and surfaces decisions + commitments back into the workspace.
- CursorCursor's MCP integration sends conversations captured at coding-time into Pulse with the AI_CURSOR source. The same seven capture tools (conversation, snippet, decision, commitment, note, …) work; per-user pulse_mcp_* tokens scope to the engineer's own workspace.
- Codex CLICapture from the terminal. Codex pushes conversations with the AI_CODEX source. Identical token + scope model to Claude Desktop and Cursor.
- Capture overviewArchitecture: the seven capture tools converge on ingestPushedDocument(), which fans out the same 6 extraction events as connector data. Decisions, commitments, custom entities, sensitivity, embeddings, and summaries all run automatically.
- Personal memoryCarry your own private facts and writing/coding style across AI tools. pulse_remember saves a durable preference, pulse_recall loads your facts + style block so any client continues in your voice, pulse_forget drops one. Private to you, never team-visible; managed at Settings → Data → Personal memory.
Mint a per-user MCP capture token at /app/settings/integrations/mcp-tokens. Tokens start with pulse_mcp_ and carry the mcp:capture scope; demo workspaces are blocked at the route layer. Tokens are one-time display, revocable any time.