← ClaudeAtlas

notion-docslisted

Notion workspace management via MCP - create databases, pages, comments, and knowledge bases. Use when building Notion documentation, organizing project wikis, or managing Notion content.
bg-szy/TOP-SKILLS · ★ 1 · AI & Automation · score 70
Install: claude install-skill bg-szy/TOP-SKILLS
# Notion Documentation > Tech Stack Target / Version: Notion API current version, Markdown-to-Notion transforms, and local template scripts. Use this skill when Notion is the system of record for specs, runbooks, project tracking, or knowledge management. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Current MCP Reality As of March 2026, Notion documents two supported ways to use its MCP server: - Hosted remote MCP endpoint: `https://mcp.notion.com/mcp` - Local stdio server package: `@notionhq/notion-mcp-server` Hosted mode uses OAuth. Local mode uses an internal integration token. Official docs also list supported tools for searching content, reading pages, comments, users, and working with pages and databases. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - Creating or updating Notion pages - Building project trackers or engineering knowledge bases - Organizing specs, ADRs, and onboarding docs in Notion - Adding review comments or using database-backed workflows ## Practical Workflow 1. Confirm whether the client exposes the hosted Notion MCP server or a local stdio connection. 2. Read or search existing pages before creating duplicates. 3. Use databases for tracked work and pages for long-form documents. 4. Keep properties simple: owner, status, last reviewed, tags. 5. If MCP is unavailable in the current client, fall back to local con