Notion

Notion’s own MCP server wraps its public API as agent tools — searching across a workspace, reading page and database content, creating and editing pages, and updating database properties — using the same integration-token permission model as any other Notion API integration, so access stays scoped to whatever pages the integration was explicitly shared with.

That scoping-by-sharing is the main thing to get right on setup: a token only sees what’s been shared with its integration, not the whole workspace by default, which makes it straightforward to hand an agent access to one project’s docs without opening up everything else.

Pairs well with Doc Coauthoring or Internal Comms in this catalog’s skills section when the actual editing work benefits from more structure than the raw MCP tools provide on their own.