Notion 3.8 opens your workspace to MCP agents. Scope it first

Notion 3.8 turns your workspace into shared context for AI agents. The October 13 release lets any MCP-compatible agent read your pages and update docs and task trackers. It also adds the controls to limit that access. For a small team that runs the business out of Notion, the controls are the part to set up first.

What actually happened

Notion's release notes list these changes for 3.8:

• MCP for any agent. Connect an MCP-compatible agent to read workspace context and update docs and trackers. Notion names Claude, Muses, GrokBots and Dots as examples. Notion's own agents can also act in outside tools such as HubSpot, Stripe and Cloudflare, with "150+ MCP connections" to browse.
• Admin MCP controls. Admins can see who connected each AI tool and when it was last used, and revoke one person's access without breaking other connections. Admins can also limit connections to tools Notion has verified, or to a list they choose.
• Column permissions. Database owners can set which properties each person or agent can view or edit. Notion's examples: hide compensation fields from a recruiting team, keep restricted customer data away from support agents.
• Skills API. Write a Skill once in Notion and sync it to ChatGPT, Claude and other agents, or load it into GitHub. Notion's Skills post adds an open-source GitHub sync kit and support in Vercel's skills CLI (npx skills add <notion url>).

The release also rebuilds synced databases (GitHub, Jira and Salesforce first), upgrades version history with attribution, and adds new models.

Why it matters for your business

For many small companies, Notion is the business. SOPs, client notes, pricing, hiring, sometimes passwords nobody moved. Connect an agent through MCP and it can see all of it, under the identity of the person who connected it. Notion now gives you the tools to fix that. They only help if someone sets them up.

Our order of operations: restrict connections to an approved tool list. Audit the databases that hold money, people or customer data, and use column permissions to hide the sensitive fields from agents. Check the connection log monthly and revoke tools nobody uses. Then use the Skills API for what it is good at. Write your process docs once, version them in GitHub, and give every agent the same instructions. One source of truth for how your business runs is worth more than any model upgrade.

Sources: Notion 3.8 release notes, Notion blog: A skills library for every agent.