notion-connect
Skill293 starsChanged 11 days agoMITView on GitHub
Use for 'connect notion', 'notion status', or 'disconnect notion' — connects the current agent runtime directly to Notion's official hosted MCP for search and fetch, or checks/revokes that connection.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 32
Do not claim that the MCP is read-only or limited to selected pages.
- Very specific: line 52
Use the path for the current runtime.
- Distinctive: line 63
If the tools do not appear after login, say:
- Very specific: line 93
Add https://mcp.notion.com/mcp as a Streamable HTTP server named notion, then complete Notion's OAuth flow.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Connect the current agent runtime directly to Notion's official hosted MCP.
Arguments: $ARGUMENTS (Optional: status or revoke)
When to invoke
- "connect notion", "set up notion", "link notion" → run the connection flow
- "notion status", "is notion connected" → status
- "disconnect notion", "revoke notion" → revoke
/ingest notionalso enters this flow automatically when the MCP tools are missing. Users do not need to run this skill first.
Product boundary
Notion provides the bridge. Egregore does not register a Notion OAuth app and
does not receive or store the user's Notion OAuth token. The current agent
runtime connects directly to https://mcp.notion.com/mcp; Notion owns the
login and consent screen, and the runtime stores its own authorization.
Say this before opening the login flow:
Notion will connect directly to this agent. Egregore Labs does not receive your Notion login or token. The agent can see what your Notion account can see. Search and fetched content pass through this session; pages you approve are additionally saved as curated shared memory.
Do not claim that the MCP is read-only or limited to selected pages. Notion MCP
uses the signed-in user's permissions. Normal Egregore session capture may
include tool results the agent inspected. The /ingest notion review step is
the boundary for what becomes a curated Notion source in shared memory.
Readiness check
First discover available tools using the runtime's tool registry:
- Claude Code: use ToolSearch with
notion. - Codex/OpenAI clients: search for Notion MCP tools. OpenAI may expose
notion-searchandnotion-fetchassearchandfetch. - Other MCP-aware runtimes: inspect the loaded tools for the Notion server.
The connection is ready when both search and fetch are available. Prefer a
notion-get-self/get-self call for status when present; otherwise a small
search is enough to verify access.
Setup
Use the path for the current runtime. These commands register Notion's official remote MCP only; they do not install an Egregore connector.
Claude Code
claude mcp get notion >/dev/null 2>&1 || \
claude mcp add --transport http --scope project notion https://mcp.notion.com/mcp
claude mcp login notionIf the tools do not appear after login, say:
Notion is connected. Restart this Claude Code session, then run
/ingest notionagain.
Codex
Notion is optional and is not registered by a fresh Egregore installation. On an explicit connection request, register it if absent, then sign in:
codex mcp get notion >/dev/null 2>&1 || \
codex mcp add notion --url https://mcp.notion.com/mcp
codex mcp login notionIf the tools do not appear after login, say:
Notion is connected. Restart this Codex session, then run
$ingest notionagain.
Pi
Pi does not provide MCP support. Do not fall back to the legacy REST connector. Say:
Notion MCP is not available in Pi yet. Open this Egregore in Claude Code or Codex to connect and import Notion pages.
Stop.
Other MCP clients
Add https://mcp.notion.com/mcp as a Streamable HTTP server named notion,
then complete Notion's OAuth flow. If the client only loads new servers at
startup, ask the user to restart and return to /ingest notion.
Continue into ingest
Once search and fetch are available, return directly to the calling
/ingest notion flow. When this skill was invoked on its own, close with:
Connected. Run
/ingest notionand tell me what you want to bring into memory.
Status
Discover the Notion tools and call notion-get-self/get-self when available.
Report only connected workspace/user information returned by Notion. Do not
read .egregore-state.json; MCP authorization belongs to the runtime.
Revoke
- Claude Code:
claude mcp logout notion - Codex:
codex mcp logout notion - Other clients: disconnect Notion from that client's MCP settings.
Confirm:
Disconnected here. Pages already imported into Egregore memory remain until you remove them.
Telemetry, fire-and-forget:
bash bin/telemetry.sh emit "command" '{"command":"notion-connect","transport":"mcp"}' 2>/dev/null &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.

