Vibe Notion

Your agent edits Notion as you — not as a bot

For Notion, automation is easy. Acting as you isn't. vibe-notion reads the session your Notion desktop app already holds, so your agent edits, comments, and searches as your logged-in account — not as an integration bot. If you do want a bot identity (server, CI/CD), vibe-notionbot ships alongside it and speaks the official Integration API.
Table of Contents
Why Vibe Notion?
You shouldn't need a bot to edit your own notes.
The Notion MCP and the official Integration API are fine for automation. They share one thing by design: the agent acts as an integration bot, not as you.
Concretely, that means:
- Bot identity on writes. Pages, blocks, and comments created through the official API are attributed to the integration, with its own name and avatar. The
last_edited_by and created_by fields return a bot user, not you. (Notion docs)
- Access is integration-scoped. The integration only sees pages that have been explicitly shared with it via "Add connections." Your private drafts and pages you haven't connected stay invisible. (Notion docs)
- Setup needs a workspace owner. Creating an internal integration requires workspace owner privileges — regular members can't.
- No user impersonation. The API has no "act on behalf of" mode. Integration-scoped is the only mode.
That's the right fit for a shared automation or a CI bot. It's the wrong fit when the agent is yours and the work is yours — when a comment should show your face, a page edit should show your name, and your agent should be able to read the private doc you never "connected" anything to.
vibe-notion reads the token_v2 your Notion desktop app is already using, so your agent inherits your session directly.
- Act as you —
vibe-notion extracts token_v2 from the Notion desktop app. Edits, comments, and pages are attributed to your account
- See what you see — Anything your logged-in session can open is accessible. No per-page "Add connections" step
- Bot mode included —
vibe-notionbot uses official Integration tokens (NOTION_TOKEN) when a bot identity is what you actually want
- Full API coverage — Pages, databases, blocks, users, search, comments, workspaces
- Agent memory — Remembers workspace IDs, page names, and preferences across sessions
- CLI, not MCP — One command per action, loaded through a skill. Smaller tool surface per prompt. (More)
Installation
npm install -g vibe-notion
Or use your favorite package manager. This installs both vibe-notion and vibe-notionbot.
Agent Skills
Vibe Notion ships with Agent Skills that teach your AI agent how to use each CLI. Install only what you need:
vibe-notion — Act as you (private API, token_v2)
vibe-notionbot — Act as a bot (official Integration API, NOTION_TOKEN)
SkillPad
SkillPad is a GUI app for Agent Skills. See skillpad.dev for more details.

Skills CLI
Skills CLI is a CLI tool for Agent Skills. See skills.sh for more details.
npx skills add devxoul/vibe-notion
Claude Code Plugin
/plugin marketplace add devxoul/vibe-notion
/plugin install vibe-notion
OpenCode Plugin
Add to your opencode.jsonc:
{
"plugins": [
"vibe-notion"
]
}
Quick Start