Notion MCP and the Yalc Framework
The most installed MCP across Yalc workflows. Read and write to your CRM, campaigns DB, and content tracker from a single Claude prompt without HTTP plumbing.
Add Notion to Claude Code in one command
claude mcp add notion --env NOTION_TOKEN=secret_xxx -- npx -y @notionhq/notion-mcp-server
Generate a Notion integration token at notion.so/profile/integrations. Grant access to the workspaces and databases Yalc should read or write. Replace `secret_xxx` with the token, run the command, restart Claude Code.
Notion, plainly
Notion ships an official MCP server (`@notionhq/notion-mcp-server`) with 22 plus operations spanning data sources, databases, pages, comments, and search. The integration is officially maintained by Notion, MIT licensed, and stable enough to use in production.
For Yalc operators, Notion is already the canonical CRM and database layer. The MCP turns every Notion read and write into a native Claude tool call. When a Yalc workflow needs to "create a row in the Q3 outbound DB", "update this campaign's status to Sent", or "summarize last week's Posts Published", the MCP makes that a one shot prompt instead of a custom integration.
Position in the GTM operating system
The Notion MCP sits at the **route** node of every Yalc workflow that needs to remember state across runs. When Yalc creates a campaign, enriches a lead, or logs a reply, that state lives in Notion via this MCP.
Pair the MCP with Yalc's first party `notion-page-writer` skill for batch operations (40 page batches, schema discovery, format conventions). The MCP handles single ops; the skill handles batches.
Deploying the Notion MCP inside Yalc workflows
Workflow position
The CRM and database layer. Yalc's source of truth for campaign state, lead lists, content pipelines, and agent run logs. Most other MCPs and skills eventually write to or read from Notion via this server.
Prompt patterns
Copy paste prompts for Claude Code that invoke the Notion MCP.
Chaining recommendations
Anti patterns to avoid
Compatibility
Stable in Claude Code (primary surface). Compatible with Claude Desktop and Cursor via the same npm package. The MCP works on the Free Notion plan and above. Webhooks for real time events require Notion's Business plan.
Pros, cons, who it's for
Pros
- Official Notion server. MIT license. Active maintenance.
- 22+ operations cover the full Notion surface, no escape hatches needed.
- Token based auth with per workspace scoping. No OAuth dance for personal use.
- Reads and writes to data sources, databases, pages, comments, and search.
- Free to install and run. You only pay for Notion itself.
Cons
- Schema discovery is slow on first call. The MCP has to introspect the database structure.
- Some operations (bulk creates) are sensitive to Notion's API rate limits. Yalc skill enforces 40-page batches.
- Real time events require Notion Business plan webhooks. The MCP itself does not poll.
- Token grants are per integration. Yalc workflows that touch multiple workspaces need multiple tokens.
Who it's for
- Yalc operators using Notion as a CRM, campaign tracker, or content workspace
- Agencies running per client Notion workspaces with consistent schemas
- GTM engineers who don't want to write per-Notion-database integration code
The Notion ecosystem inside Yalc
MCPs to consider instead
Frequently asked
Does the Notion MCP work on the free Notion plan?
Yes. Reads and writes work on Free, Plus, Business, and Enterprise. Webhooks require Business or above.
How do I scope which databases the MCP can access?
When you create the integration token at notion.so, you grant explicit access to the pages and databases you want exposed. Anything not explicitly shared is invisible to the MCP.
Is the MCP a replacement for Yalc's notion-page-writer skill?
They compose. The MCP handles single operations from natural language. The skill wraps batched operations (40-page chunks, schema validation, dedupe) for production workflows.
How does this compare to Airtable's MCP?
Notion's MCP is more mature and comes from the vendor directly. Airtable's options are mostly third party. For GTM use cases (CRM, campaigns, content), Notion plus this MCP is the easier path.
Will the MCP burn through my Notion API limits?
Notion's API is generous. For typical Yalc volumes (a few hundred ops a day), you won't hit limits. For batch jobs above 1k ops, the Yalc skill chunks and rate limits.
Can I use multiple Notion workspaces?
Yes. Register multiple integration tokens and add the MCP server multiple times with different `--env` values and different server names. Yalc workflows can then route to the right workspace by name.
Install the Notion MCP
Drop it into Claude Code and orchestrate from your next Yalc prompt.
claude mcp add notion --env NOTION_TOKEN=secret_xxx -- npx -y @notionhq/notion-mcp-server