How Notion used the Cursor SDK to embed coding agents

Summary

Notion integrated Cursor coding agents into its product so users can delegate work by tagging Cursor in a document, mentioning it in a thread, or assigning a database issue. Built with the Cursor SDK in a couple of weeks, the integration lets agents plan, build, test, verify work, and open pull requests while Notion focuses on product and user experience rather than agent infrastructure. Notion placed Cursor behind a provider-agnostic harness: a Notion thread maps to an agent, each message starts a run, and the first run can specify the prompt, repository, model, MCP servers, and automatic PR creation. Follow-up runs stream over SSE, support resumption after dropped connections, and use remote MCP to let Cursor read and write workspace state in real time; templates, custom instructions, selected tools, skills, subagents, and triggers provide further customization.

Takeaways

1. 1

   The first message in a Notion thread creates a Cursor agent with a prompt, selected repository, model, optional MCP servers, and automatic PR creation enabled.

2. 2

   Each follow-up message starts a new agent run streamed over SSE, allowing users to watch progress and resume from the last event after a dropped connection.

3. 3

   Remote MCP lets Cursor read and write Notion workspace state in real time, while templates, custom instructions, skills, subagents, and triggers customize agent behavior.