Notion Multi Workspace
Connects multiple Notion workspaces and provides tools for listing workspaces, searching across connected workspaces, and fetching page contents, with results labeled by source workspace.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Notion Multi Workspacesearch for the project brief across all my workspaces"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Notion Multi Workspace
A distributable Codex plugin backed by one OAuth-protected remote MCP server. It connects any number of Notion workspaces while exposing only four tools:
notion_connect_workspacenotion_list_workspacesnotion_searchnotion_fetch
The number of tools is constant. Adding workspaces adds encrypted connection rows, not MCP servers or duplicate tools.
Why one MCP instead of one MCP per workspace?
A separate MCP server for every workspace multiplies the exposed tool surface. With N workspaces and M Notion tools, the client can end up seeing roughly N × M tools. That increases tool-selection ambiguity, configuration work, and the chance of querying the wrong workspace.
This plugin keeps one remote MCP server and stores workspace authorizations as data:
Codex
└─ one Notion Multi Workspace MCP
├─ connection A → workspace A
├─ connection B → workspace B
└─ connection N → workspace NThe MCP surface therefore stays at four tools regardless of how many workspaces are connected. Search fans out across the selected connections and labels every result with its source workspace.
Related MCP server: Notion MCP Server
Install in Codex
Add this repository as a Codex marketplace, then install the plugin:
codex plugin marketplace add psh4607/notion-multi-workspace
codex plugin add notion-multi-workspace@notion-multi-workspaceRestart Codex if prompted. The first use opens OAuth for both the MCP service and the first Notion workspace. No Notion developer account or integration token is required for installers.
What installers do
Install the plugin from the marketplace.
Complete the Notion OAuth screen and choose the first workspace.
Ask Codex to connect another workspace. Open the one-time URL returned by
notion_connect_workspaceand choose that workspace in Notion.
Installers do not create integration tokens, use macOS Keychain, or maintain workspaces.json. The plugin publisher operates one Notion public integration and the remote MCP service.
Architecture and security boundary
Codex authenticates to
/mcpusing OAuth 2.1 with PKCE.Notion authorization is a separate upstream OAuth flow.
D1 rows are scoped by
(user_id, bot_id).bot_idpreserves multiple authorizations even when they target the same workspace.Notion access and refresh tokens are encrypted with AES-256-GCM before D1 storage.
The encryption key and Notion client secret are Cloudflare Worker secrets.
Additional-workspace links are random, one-use states in KV with a 10-minute TTL.
The MCP surface is read-only. Search fans out; fetch requires one explicit connection ID.
Troubleshooting
Symptom | Likely cause | Resolution |
Marketplace says the connection cannot be found | Creator dashboard is using a different Notion account | Switch to the account that owns the public developer connection and reload the listing form |
Plugin installs but tools are not visible | Codex has not reloaded the new plugin | Restart Codex, then confirm the plugin is enabled |
First OAuth succeeds but another workspace is missing | The additional one-time URL expired or the wrong Notion workspace was selected | Run |
Search returns no pages from a connected workspace | The integration was not granted the relevant pages | Reopen the connection in Notion and grant the required pages; the connector only sees authorized content |
Development and self-hosting
Contributions are licensed under the Apache License 2.0. Please review the contributing and security guidelines before opening a pull request or reporting a vulnerability.
Service documents
For bugs and support requests, use this repository's GitHub Issues or email psh30095@gmail.com. Do not include Notion page content, OAuth tokens, or other secrets in a public issue.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-quality-maintenanceEnables secure interaction with Notion through a suite of tools for searching, reading, and modifying pages and databases. It features OAuth 2.1 authentication with PKCE and encrypted token storage to provide an enterprise-ready interface for MCP clients.Last updated
- Alicense-qualityAmaintenanceStateless MCP server exposing the full Notion API as 33 tools, enabling users to manage pages, databases, blocks, comments, users, and file uploads using their own integration token.Last updatedApache 2.0
- Flicense-qualityDmaintenanceEnables interaction with Notion workspaces, allowing users to search, query databases, create/update pages, and manage content via natural language through MCP.Last updated
- Alicense-qualityAmaintenanceNotion-like workspace of pages and customizable databases with a remote MCP server (OAuth 2.1 + PKCE, scoped read/write tokens, full audit log). 14 tools to search, read, and write pages, database rows, and database schemas.Last updated61AGPL 3.0
Related MCP Connectors
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions.
MCP-native open-source Notion alternative: read & write pages, databases and kanban boards.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/psh4607/notion-multi-workspace'
If you have feedback or need assistance with the MCP directory API, please join our Discord server