Notion CoachWork smarter.

Notion MCP lets external assistants start and follow Custom Agent sessions

TL;DR

On August 27, 2026, Notion added MCP tools for working with Custom Agent sessions. An authorized external assistant can find sessions, start work, follow progress, send follow-up messages, and stop a run when the connection exposes those tools.

An external assistant uses Notion MCP to work with a Custom Agent session.
Editorial diagram of session orchestration, subject to the connection’s available tools and permissions. Source: Notion developer documentation. View full size
Status
Live
Released
Plans
Not specified

What changed

Notion MCP added a session interface for Custom Agents. It supports finding earlier sessions and interacting with new or running work through the connection's available tools.

This is separate from the later MCP page, comment, and calendar tools.

Why it matters

An external assistant can coordinate with a workspace agent instead of reproducing its instructions elsewhere. A useful workflow might ask an existing reporting agent for a result, wait for completion, and bring that result back for review.

Keep responsibility clear: identify which agent owns the job, what completion means, and who reviews its output.

Frequently asked questions

Can every Notion MCP connection call a Custom Agent?

No. The workspace needs access to Notion AI and Custom Agents, and the connection must expose the relevant capability and session tools.

Can an assistant send another message while a session is running?

The current documentation says follow-up messages can return a conflict while a run is active. Wait for that run before sending another message.

No. Session operations remain subject to connection and workspace permissions.

Sources