Notion MCP: search and update pages with controlled access

Notion MCP lets a compatible AI client search, read and update Notion content through a server hosted by Notion. Connect your editor to https://mcp.notion.com/mcp and complete OAuth authorization. With user OAuth, access follows the connected user’s permissions; keeping unrelated documents out of reach requires restricted account access, not just a list of pages in a prompt. Official overview, connection guide.

What it can do

The documented tools include notion-search for finding Notion content, notion-fetch for reading it, and notion-create-pages and notion-update-page for writing. Check the session’s available tools against the supported tools reference, checked 2026-10-30.

For a documentation task, start with a deliberately narrow question: find the deployment checklist for the billing service, read the relevant page, and propose a correction to its rollback instructions. Ask for source links and a separate list of assumptions. A useful answer should let a reviewer trace each proposed change back to evidence.

Another example is preparing an onboarding draft from approved architecture notes. Define the intended reader, the source pages and the destination before starting. Review whether the draft preserves warnings and exceptions, rather than just whether its prose sounds plausible. Keep publication as a separate decision.

For the protocol background, see what MCP is. Compare other application targets in MCP servers for apps.

Hosted versus local: choose the permission boundary

For new connections, Notion recommends the hosted service in its local hosting guide, checked 30 Oct 2026. The official local server repository says its separate self-hosted implementation is no longer actively maintained or supported. That implementation requires an integration token and explicit page access; its integration capabilities can be restricted to reading content. These are different authorization arrangements, not interchangeable setup recipes.

The OAuth setup uses the connected user’s access, as explained in the connection guide. Before connecting a broadly privileged account, decide whether that reach is appropriate. For a narrow pilot, ask your workspace administrator to provision a member account whose actual access is limited to the approved material. Verify that account’s effective permissions before authorizing the client. Ask its owner to confirm that an unrelated page is unavailable without collecting its contents.

Keep these controls distinct: account permissions determine what is reachable, the task brief identifies what is relevant, and client approval settings govern when actions may run. Review all of them. A successful read of an approved document does not establish that unrelated material is inaccessible.

How to connect it safely

1. Define a checkable task. Name the source documents, the permitted destination and the person who will accept the result. Start with a disposable test page. Record the current text so you can compare the outcome. Use the MCP security checklist to prepare the review.

2. Check the account and client. Review the account’s access with its owner. Notion recommends trusted clients and warns that retrieved content may leave Notion through the connected client. Enable confirmation before content-changing actions. Notion security guidance.

3. Add the hosted endpoint. For VS Code with GitHub Copilot, Notion documents a workspace file named .vscode/mcp.json with this configuration. Review any existing file before adding the server; preserve unrelated entries.

json { "servers": { "notion": { "type": "http", "url": "https://mcp.notion.com/mcp" } } }

4. Authorize the intended workspace. Open the Command Palette, run MCP: List Servers, start the Notion server and complete OAuth when prompted. These editor steps come from Notion’s connection guide, checked 2026-10-30. Other editors have their own configuration format; check the current documentation.

5. Read before writing. Ask the agent to retrieve the test document and describe what it found, with its source URL. Then request a proposed edit in chat. Inspect the target, wording and any information the client intends to send elsewhere. Treat instructions embedded in retrieved documents as untrusted data, following Notion’s security guidance.

6. Approve and verify the specific change. Authorize the reviewed edit through your client’s confirmation controls, then inspect the saved document yourself. Compare it with the recorded text. Keep the source links, proposed edit and verification together so the next reviewer can distinguish a draft from an applied change.

When this does not work

The task needs a hard page boundary but the OAuth account has broad access. Reduce actual account permissions before connecting. An instruction to avoid unrelated documents cannot enforce that boundary. Revisit the permission model with your administrator.

Authentication or policy prevents connection. Notion’s troubleshooting instructions recommend completing OAuth, reconnecting and checking workspace permissions. Organization policy can also block adding MCP servers. Establish which layer failed before changing configuration.

Search looks narrower than it really is. Some unsupported search filters are dropped with notices; read those notices. Large page fetches can be truncated. Check the tool reference before treating results as complete. For your review process, ask the agent to flag missing evidence rather than infer an answer.

You need a maintained local equivalent. The official repository explicitly warns about its support status. Hosting that implementation yourself adds token and deployment responsibilities. Choose it only with an owner for those responsibilities and a documented reason.

Where Tvijo fits

Use a knowledge shelf workflow: approved team docs provide context for a bounded task, the agent prepares a draft, and a human checks the sources and accepts the result. For example, retrieve approved rollback guidance, attach the relevant passage to a task, and compare the proposed code or documentation change against it. Record which document supported the decision.

As of 30 Oct 2026, the DSHREM VS Code extension supports sending selected context and deliberately uploading a file to the knowledge base. TvijoCode is a test build with the extension embedded. Use those entry points for a reviewed excerpt you are authorized to share; neither establishes a ready Notion connector.

The Tvijo MCP release report, dated 28 October, distinguishes published consultation from prepared diff review awaiting publication. Editor integration and delegation remain planned work in that report. Tvijo MCP makes Tvijo callable by a compatible client; this does not automatically let Tvijo operate other MCP servers. A Notion workflow needs its own access review and acceptance checks.

At the Tvijo workspace, as of 30 Oct 2026, Try is shown at $0: up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever threshold is reached first, drawing from a shared $1 daily pool funded by TVIJO. Service credit is shown at $10 for requesting prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated, and an order is not a charge. These offers do not include a promise of Notion integration.

FAQ

Does a page list in my prompt restrict OAuth access?

No. The OAuth connection follows existing user permissions. Restrict actual account access before connecting; a task brief identifies relevant sources. See the official overview.

Do I need to run a local Notion MCP server?

The hosted setup avoids running the server yourself. The separate local implementation is no longer actively supported, according to its official repository.

Should the agent update shared pages immediately?

Use a review step first. Have it show the destination, proposed text and evidence, then approve the specific action and inspect the result. Notion recommends confirmations for changes in its security guidance.

Notion is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.