Notion MCPNotion MCP
Notion 官方自己的 MCP server:纯远程托管(mcp.notion.com/mcp),agent 能搜工作区、 读写页面与数据库。要点一句话:agent 的可见面 = 你连的那个账号的页面权限。
Notion's own MCP server: fully hosted (mcp.notion.com/mcp) — agents search the workspace and read/write pages and databases. One line matters: the agent's visibility equals the page permissions of the account you connect.
适合与不适合When to use it, when not to
适合:知识库检索进 agent 上下文、会议记录/任务自动写进 Notion。 不适合:要自托管或离线(无本地形态);要工具级细粒度审批(未见官方机制)。
Fits: knowledge-base retrieval into agent context; auto-writing meeting notes/tasks into Notion databases. Not a fit: self-hosting or offline (no local form); tool-level fine-grained approval (no official mechanism found).
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21
- 出品属地Origin
- 国外出品foreign-made Notion Labs, Inc.(美国)。Notion Labs, Inc. (US).
- 国内使用Direct access
- 大陆可直连direct OK developers.notion.com 直连实测 200(2026-10-21);notion.mcp.run 直连 000(网络受限,非死亡判定)。developers.notion.com measured 200 direct (2026-10-21); notion.mcp.run measured 000 direct (network-limited, not a death verdict).
- 备案状态CAC filing
- 未见于备案名单not in filing list:未见于网信办公示名单(2026-10-21 检索);该产品未面向大陆公众提供服务,备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准(按批次滚动更新,本站只抄编号不解读);「大陆可直连」是本站从大陆网络直连实测的结果,不是厂商承诺。GitHub 类站点当日实测有波动,口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
它自己不调模型——被 MCP 客户端调用的接口实现。它把 Notion 工作区能力 (搜索、页面读写、数据库查询)包装成工具给 agent 用。
It calls no model itself — an interface implementation called by MCP clients. It wraps Notion workspace capabilities (search, page read/write, database queries) as tools for agents.
- 运行位置Where it runs
官方托管远程 server(端点 mcp.notion.com/mcp——直抓 401=存在需鉴权,非死链); 无本地形态的官方说明。notion.mcp.run 直抓 000(网络受限标注)。
Official hosted remote server (endpoint mcp.notion.com/mcp — direct fetch 401 = exists but needs auth, not a dead link); no official docs for a local form. notion.mcp.run direct-fetched 000 (noted as network-restricted).
- 本地文件Local files
不碰本机文件系统——作用域是 Notion 云端工作区(页面、数据库、评论)。
Never touches the local file system — the scope is the Notion cloud workspace (pages, databases, comments).
- 关机后的任务Tasks after shutdown
服务在 Notion 侧常驻;MCP 会话是请求-响应,无后台任务语义。
The service is resident on Notion's side; MCP sessions are request-response, no background-task semantics.
- 工具与扩展Tools & extensions
搜索、取页面、建/改页面与数据库条目等;完整工具清单以官方文档为准,未逐条清点。 写能力存在(建页/改块),边界按工作区共享与权限走。
Search, fetch pages, create/edit pages and database entries, etc.; the complete tool inventory follows the official docs, not enumerated item by item. Write capabilities exist (create pages/edit blocks); the boundary follows workspace sharing and permissions.
- 上下文与记忆Context & memory
无 server 侧跨会话记忆——状态在 Notion 工作区本身;Notion AI 的记忆线是另一产品,不算它。
No server-side cross-session memory — state lives in the Notion workspace itself; the Notion AI memory line is a separate product and does not count as this one.
- 权限与限制Permissions & limits
OAuth 用户鉴权 + 工作区权限模型:agent 能看到/改什么,跟着连接的那个 Notion 账号的 页面共享权限走——这是选型要点:连谁的账号=谁的可见面。
OAuth user auth + the workspace permission model: what the agent can see/change follows the page-sharing permissions of the connected Notion account — this is the selection key: whose account you connect = whose visibility.
- 适合什么任务Best for
适合:agent 读写团队知识库、把会议记录/任务写进 Notion 数据库、从 wiki 检索上下文。 不适合:要离线/自托管(无本地形态);要细于账号权限的工具级隔离。
Fits: agents reading and writing the team knowledge base, writing meeting notes/tasks into Notion databases, retrieving context from the wiki. Not a fit: offline/self-hosted needs (no local form); tool-level isolation finer than account permissions.
- 传输方式Transport
Streamable HTTP 远程托管(mcp.notion.com/mcp);无本地 stdio 形态的官方说明。 核验:官方文档页 200、端点 401(2026-10-21 直抓)。
Streamable HTTP remote hosting (mcp.notion.com/mcp); no official docs for a local stdio form. Verified: official docs page 200, endpoint 401 (direct fetch 2026-10-21).
- 认证机制Authentication
OAuth 浏览器授权流(首次连接登录 Notion 账号);无 token 明文配置路线的官方说明。 工作区管理员可管控连接(admin 审批面细节未逐条核验)。
OAuth browser authorization flow (log into the Notion account on first connection); no official docs for a plaintext-token configuration route. Workspace admins can control connections (admin-approval surface details not verified item by item).
- 权限范围Permission scope
作用域=所连账号的工作区可见面;读写都有(搜索/取页/建页/改块)。 工具级审批机制未见官方说明——写面收紧靠账号权限与客户端侧确认。
Scope = the connected account's workspace visibility; both read and write (search/fetch pages/create pages/edit blocks). No official docs seen for a tool-level approval mechanism — tightening the write surface relies on account permissions and client-side confirmation.
头号误解Top misconception
- 把「连上 Notion MCP」当「agent 能看全工作区」——可见面=所连账号的页面权限Assuming 'connected to Notion MCP' means 'the agent sees the whole workspace' — visibility equals the connected account's page permissions
- 把 notion.mcp.run 000 当服务死了——现役端点是 mcp.notion.com/mcp(401=需鉴权)Reading notion.mcp.run 000 as the service being dead — the live endpoint is mcp.notion.com/mcp (401 = auth required)
- 写操作无独立审批——agent 建页改块直接生效,接 agent 前先想清楚写面Writes take effect with no separate approval — think through the write surface before plugging in an agent
未知项清单Known unknowns
- 完整工具清单(未逐条清点)
- 工作区管理员对 MCP 连接的管控粒度(未逐条核验)
- 速率限制细则(官方文档未给数字)
- The complete tool inventory (not enumerated item by item)
- The granularity of workspace-admin control over MCP connections (not verified item by item)
- Rate-limit details (official docs give no numbers)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30,内容更新日content updated on 2026-10-21。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| docs | Notion · 官方 MCP 文档(端点与鉴权口径,2026-10-21 直抓核验)Notion · official MCP docs (endpoint and auth wording, direct-fetched and verified 2026-10-21) | https://developers.notion.com/docs/mcp |
| changelog | Notion · 官方更新日志(changelog)Notion · official release notes (changelog) | https://www.notion.com/releases |
| docs | Notion · 开发者文档首页Notion · developer docs home | https://developers.notion.com |
实测记录Measured runs
本档未在真实客户端逐项跑通;工具清单与权限来自官方 README。
This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.
相关条目Related entries
- Slack MCPSlack MCP Server同为协作 SaaS 官方 remote server:Slack 版 admin 审批面更重,Notion 版写面更直接。Both official remote servers for collaboration SaaS: the Slack version has a heavier admin-approval surface, the Notion version's write surface is more direct.
- CursorCursor另一层 · AI 编程Other layer · AI coding
- Windsurf / Devin DesktopWindsurf / Devin Desktop另一层 · AI 编程Other layer · AI coding
本页由This page is generated from the ai-handbook 数据层生成(CC BY 4.0)。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.