Notion MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow Notion API and write-tool scope because workspace operations change

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI agents that search, read and update shared Notion workspaces

What we know

Community Notion API MCP with discovery, page reading, data-source queries, editing and raw API operations.

Maintenance / activity evidence

Observed Jul 12, 2026 (UTC)Merge pull request 87 from suekou/dependabot/github actions/actions/…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Integration capabilities + explicitly shared Notion content. Writes: Create/append/update content when granted.
NOTION_API_TOKEN.
Sensitive access: Workspace pages, Databases, Comments, Users

Scope the Notion integration carefully because the server exposes write and raw API operations.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

920 repository stars

Stars observed Oct 6, 2026.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

All limitations / Review context

Which Notion read and update operations and auth scopes are documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Scope the Notion integration carefully because the server exposes write and raw API operations.
Integration capabilities + explicitly shared Notion content.
NOTION_API_TOKEN.
Workspace content is accessed through Notion API.
Reviewed write actions: Create/append/update content when granted
Sensitive access: Workspace pages, Databases, Comments, Users
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Requires a Notion internal integration and explicit page/database sharing.
Raw API tools can be broad.

Original activity observations

2026-07-12T05:42:22Z: Merge pull request 87 from suekou/dependabot/github actions/actions/…

Technical identity

github.com/suekou/mcp-notion-server

Exact implementation source: https://github.com/suekou/mcp-notion-server ↗
Reviewed resource type: MCP Server
Repository identity: suekou/mcp-notion-server
Package identity: npm:@suekou/mcp-notion-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
suekou/mcp-notion-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Notion MCP Server uses a Notion internal integration token.
publisher setup entry · Publisher instructions · Review before use
```
npx -y @suekou/mcp-notion-server
```
Configure / authenticate
MCP100 setup guide
Create a Notion internal integration, grant least necessary capabilities, share selected pages/databases with the integration, then set NOTION_API_TOKEN in the MCP client environment.
Check connection
Suggested check
List accessible pages/data sources without updating content.
Remove / uninstall / revoke
MCP100 setup guide
Remove the Notion MCP registration from the client under its configured name (example `claude mcp remove notion`). Uninstall a global npm package only if globally installed. Notion integration token deletion is a separate optional provider action. Client remove command is an MCP100 composed example: replace the registration name with your actual installed name.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove notion

Official Documentation & Sources

What it does

Community Notion API MCP with discovery, page reading, data-source queries, editing and raw API operations.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: AI agents that search, read and update shared Notion workspaces

Representative uses

Find/read pages
Query databases/data sources
Create items
Append/edit page content

Limitations

Requires a Notion internal integration and explicit page/database sharing.
Raw API tools can be broad.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: NOTION_API_TOKEN.
Permissions: Integration capabilities + explicitly shared Notion content.
Data handling: Workspace content is accessed through Notion API.
Cost: unknown
Risk and cautions: Scope the Notion integration carefully because the server exposes write and raw API operations.

Access scope and cautions

Write actions: Create/append/update content when granted
Sensitive access: Workspace pages Databases Comments Users
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Find/read pages; Query databases/data sources; Create items; Append/edit page content.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @suekou/mcp-notion-server. Recorded transport: stdio. Recorded environment-variable notes: NOTION_API_TOKEN. No configuration values are supplied here. Prerequisites: Node.js. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Notion internal integration token.

Can it modify data or perform write operations?

Documented write actions include: Create/append/update content when granted. Recorded permission boundary: Integration capabilities + explicitly shared Notion content.

What data-handling boundary should I consider?

Workspace content is accessed through Notion API. Recorded sensitive-access context: Workspace pages; Databases; Comments; Users.

What limitations and risks should I check before use?

Scope the Notion integration carefully because the server exposes write and raw API operations. Requires a Notion internal integration and explicit page/database sharing. Raw API tools can be broad. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

suekou is listed as Community implementation in MCP100’s current evidence.