setup-notion
Skill304 starsChanged 2 months agoMITView on GitHub
Connect Claude Code to Notion's official hosted MCP, complete OAuth, verify the intended workspace with a read, and stop before any write. Use when the user asks to connect Notion, set up Notion, export to Notion, or diagnose an unavailable Notion connection.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- FooJiaYin/dev-skillstheir own version, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- FooJiaYin/dev-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository65 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- always-compareSkill
- analysis-designSkill
- analyst-coreSkill
- archaeologySkill
- archive-analysisSkill
- auth-preflightSkill
- businessSkill
- causalSkill
- chart-to-driveSkill
- close-the-loopSkill
- codex-reviewSkill
- compare-datasetsSkill
- connect-dataSkill
- connect-snowflakeSkill
- context-compareSkill
- context-traceSkill
- data-inspectSkill
- data-mapSkill
- data-profilingSkill
- data-quality-checkSkill
- datasetsSkill
- distribution-profilerSkill
- evalSkill
- evaluate-graderSkill
- experiment-briefSkill
- experimentSkill
- exploreSkill
- exportSkill
- forecastSkill
- google-doc-exportSkill
- google-slides-exportSkill
- guardrailsSkill
- historySkill
- improve-contextSkill
- knowledge-bootstrapSkill
- log-correctionSkill
- maintain-contextSkill
- metric-specSkill
- metricsSkill
- monitor-evalsSkill
- notion-exportSkill
- paceSkill
- patternsSkill
- question-framingSkill
- question-routerSkill
- reliabilitySkill
- resume-pipelineSkill
- run-pipelineSkill
- runsSkill
- score-analysisSkill
- session-handoffSkill
- setup-dev-contextSkill
- setupSkill
- setup-slackSkill
- setup-snowflakeSkill
- srm-checkSkill
- stakeholder-communicationSkill
- stress-testSkill
- switch-datasetSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 14 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Read .mcp.json if it exists.
- Distinctive: line 33
Check whether a Notion server already points to the official endpoint.
- Distinctive: line 34
If Notion tools are already available, skip configuration and verify the connection.
- Distinctive: line 35
Before editing anything, show the user the exact non-secret change and ask for approval.
- Distinctive: line 37
Never replace the entire MCP configuration merely to add Notion.
- Very specific: line 41
After approval, add this project-local server entry while preserving the rest of .mcp.json:
- Distinctive: line 58
Do not put tokens or credentials in the configuration.
- Very specific: line 62
If this session did not load the new server, tell the user to restart Claude Code.
- Distinctive: line 65
Before the user authorizes access, remind them to confirm:
- Distinctive: line 72
Do not claim that OAuth proves the destination or makes every future action safe.
- Distinctive: line 76
Ask the user for the title of a page they expect in the approved workspace.
- Distinctive: line 97
Use only Notion's official hosted endpoint unless the user explicitly requests another server.
- Distinctive: line 99
Stop for approval before editing MCP configuration.
- Distinctive: line 100
Never request or store a Notion API key for this OAuth path.
- Distinctive: line 101
Verify the workspace with a read before any write.
- Distinctive: line 103
Never claim that hosted Notion MCP can upload files.
- Distinctive: line 104
If access is wrong, disconnect or revoke it rather than continuing with a nearby workspace.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setup Notion
Purpose
Configure Notion's official hosted MCP for this project, help the user complete browser OAuth, and verify the intended workspace before any content is created.
Current supported path
- Official endpoint:
https://mcp.notion.com/mcp - Transport: remote HTTP
- Authentication: OAuth in the browser
- Project configuration:
.mcp.json
Notion's hosted MCP does not currently support file uploads. Do not promise that a local chart or other file can be uploaded through this server. Create the text page first. If the user needs an attachment, they can add it manually or use a separately approved API workflow.
Instructions
1. Inspect before changing configuration
- Read
.mcp.jsonif it exists. - Preserve every existing MCP server.
- Check whether a Notion server already points to the official endpoint.
- If Notion tools are already available, skip configuration and verify the connection.
- Before editing anything, show the user the exact non-secret change and ask for approval.
Never replace the entire MCP configuration merely to add Notion.
2. Add the official server
After approval, add this project-local server entry while preserving the rest of .mcp.json:
{
"notion": {
"type": "http",
"url": "https://mcp.notion.com/mcp"
}
}An equivalent supported Claude Code command is:
claude mcp add --transport http --scope project notion https://mcp.notion.com/mcpDo not put tokens or credentials in the configuration.
3. Authenticate
If this session did not load the new server, tell the user to restart Claude Code. Then have the
user run /mcp, select Notion, and complete OAuth in the browser.
Before the user authorizes access, remind them to confirm:
- the Notion account;
- the workspace;
- whether that workspace is approved for the intended work; and
- that the connected client can act with the access granted to that user.
Do not claim that OAuth proves the destination or makes every future action safe.
4. Verify with a read
Ask the user for the title of a page they expect in the approved workspace. Use the available Notion search tool to find it without changing anything.
Show the workspace and matching page titles. If the expected page is missing, the workspace is wrong, or the tool call fails, stop and report the exact blocked step. Do not create a page.
5. Report the result
Report only what was verified:
Notion connection
Server: official hosted MCP
Endpoint: https://mcp.notion.com/mcp
Workspace: [verified workspace, if exposed]
Read test: [page title found, or exact blocked step]
Ready for an approved write: [yes or no]Rules
- Use only Notion's official hosted endpoint unless the user explicitly requests another server.
- Preserve existing MCP servers.
- Stop for approval before editing MCP configuration.
- Never request or store a Notion API key for this OAuth path.
- Verify the workspace with a read before any write.
- Preview the destination and content before any later write.
- Never claim that hosted Notion MCP can upload files.
- If access is wrong, disconnect or revoke it rather than continuing with a nearby workspace.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

