# How Notion used the Cursor SDK to embed coding agents

Source: [Cursor](https://cursor.com/blog/notion)  
Feed7 permalink: https://feed7.dev/p/notion-07d02so  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

Notion used the Cursor SDK to embed coding agents in a few weeks: users tag Cursor in docs or assign it issues, and it plans, codes, tests, and opens PRs. A pattern for embedding agents in your own product.

## Source Summary

**The gist** Notion embedded coding agents into its product with the **Cursor SDK**, built in **a few weeks** and detailed on **June 25, 2026**. Users tag Cursor in docs, threads, or database issues; it plans, builds, tests, and opens a PR. Notion threads map to agents, messages map to runs streamed over **SSE** with resumption after dropped connections.

## Practical Implication

**Why it matters** If you're adding agent features to your own product, this is the buy-not-build data point: the SDK supplies the agent runtime, **remote MCP** connections, and configurable **skills and subagents**, leaving you to map your product's objects — threads, issues — onto **agents and runs**.

## Agent-Ready Context

**The gist** Notion embedded coding agents into its product with the **Cursor SDK**, built in **a few weeks** and detailed on **June 25, 2026**. Users tag Cursor in docs, threads, or database issues; it plans, builds, tests, and opens a PR. Notion threads map to agents, messages map to runs streamed over **SSE** with resumption after dropped connections.

**Why it matters** If you're adding agent features to your own product, this is the buy-not-build data point: the SDK supplies the agent runtime, **remote MCP** connections, and configurable **skills and subagents**, leaving you to map your product's objects — threads, issues — onto **agents and runs**.

**Watch out** This is a **vendor case study**: no failure rates, costs, or limitations are stated, and the **months-to-weeks** claim comes from the companies involved. Weigh **SDK lock-in** and run pricing before wiring it into core workflows.

## Context Map

- Layer: tools
- Domains: coding
- Topics: agent-sdks, coding-agents

## Uncertainty

- This is a **vendor case study**: no failure rates, costs, or limitations are stated, and the **months-to-weeks** claim comes from the companies involved. Weigh **SDK lock-in** and run pricing before wiring it into core workflows.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.