# Two Notion workspaces, one MCP list > Add Notion twice, once for work and once for personal, each with its own sign-in, and pick which projects get which. Switching accounts never asks again. Source: https://shuriken.sh/blog/two-notion-accounts-one-mcp-list Add Notion twice, once for work and once for personal, each with its own sign-in, and pick which projects get which. Switching accounts never asks again. Story By Shuriken Updated 27 October 2026 3 min read **Contents** Most of us have at least two of everything. A work Notion and a personal one. A work GitHub and the account with your side projects. A client's Linear next to your own. Your agents need the right one in the right project. Getting that right by hand is fiddly, and we kept running into it ourselves. ## Why it's fiddly # Notion's official MCP server signs you in through OAuth, and the connection reaches the workspace you select when you approve it. In Claude Code, the setup from [Notion's guide](https://developers.notion.com/guides/mcp/get-started-with-mcp) is one command, claude mcp add --transport http notion https://mcp.notion.com/mcp, then /mcp to sign in (read 22 October 2026). That's one server entry and one sign-in. A second workspace means a second entry under another name, its own sign-in, and remembering which project has which. Then you do it again on your other computer. And if you work across more than one AI account, you start wondering which sign-in lives where. None of it is hard. It's just the kind of thing you redo more often than you'd like. ## Add the server twice # In Shuriken, MCP servers live in one list for all your projects and accounts (Settings › Extensions › MCP servers). To use two Notion workspaces: - Add Notion, call it something like "Notion (work)", and sign in with your work workspace. - Add Notion again, call it "Notion (personal)", and sign in with the personal one. Each entry has its own sign-in, and each says whether it's signed in. You approve each one in your browser once. The same works for any server in the list. Notion, GitHub and Linear are among 57 ready-made connectors, and you can add any other server by its address or command. ## Give each one the projects that need it # Each server is assigned either to all projects or to the ones you choose. So: - "Notion (work)" goes to your client repos and the company site; - "Notion (personal)" goes to your side projects and the recipe app you keep meaning to finish. Every chat in those projects can use the server it's been given. That keeps the client's workspace out of your side project, and the other way round. Shuriken keeps one MCP list for all your agents, and an MCP sign-in follows you to every account and computer. [Try Shuriken](https://shuriken.sh/) ## The sign-in belongs to the server # This is the part we care about most. In Shuriken, an MCP sign-in belongs to the server entry, not to your AI account. That matters because Shuriken switches accounts for you. When one of your Claude accounts reaches its switch point, your chats move to another of yours. If the Notion sign-in were tied to the Claude account, every switch would ask you to sign in again, possibly mid-task. It isn't, so it doesn't. Switch sources, switch projects, switch between Claude Code and Codex: the Notion sign-in stays where it is. Shuriken also hands the same servers to every Claude Code and Codex chat in a project when it starts, so there are no config files to keep in step by hand. We got here the hard way. Back in 1.5 we moved MCP sign-ins off the AI account for exactly this reason; [global MCPs](https://shuriken.sh/features/global-mcps) shows how it works today. ## On every device, sealed # Sign in to "Notion (work)" on your laptop, and your desktop and your server have it too. MCP sign-ins sync between your devices, servers included, and they travel end-to-end encrypted. Our cloud sees a hash and a sealed box, never the token. The [security page](https://shuriken.sh/security) says what else our cloud can and can't read. ## Set it up once # That's the whole idea of [Global MCPs](https://shuriken.sh/features/global-mcps): set up a server once, sign in once, and stop thinking about it. Our guide to [MCP servers across all your projects](https://shuriken.sh/guides/mcp-servers-across-all-projects) goes through the setup step by step, with more examples than Notion. If you've been juggling two workspaces by hand, [try Shuriken](https://shuriken.sh/) and add the second one in a minute. Share [X](https://x.com/intent/post?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Ftwo-notion-accounts-one-mcp-list&text=Two%20Notion%20workspaces%2C%20one%20MCP%20list)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Ftwo-notion-accounts-one-mcp-list)[Hacker News](https://news.ycombinator.com/submitlink?u=https%3A%2F%2Fshuriken.sh%2Fblog%2Ftwo-notion-accounts-one-mcp-list&t=Two%20Notion%20workspaces%2C%20one%20MCP%20list)[Reddit](https://www.reddit.com/submit?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Ftwo-notion-accounts-one-mcp-list&title=Two%20Notion%20workspaces%2C%20one%20MCP%20list)[E-mail](mailto:?subject=Two%20Notion%20workspaces%2C%20one%20MCP%20list&body=https%3A%2F%2Fshuriken.sh%2Fblog%2Ftwo-notion-accounts-one-mcp-list) ## Sources - [Notion developers: Get started with Notion MCP](https://developers.notion.com/guides/mcp/get-started-with-mcp) (accessed 22 October 2026) ## Frequently asked questions **Can I add the same MCP server more than once?** Yes. Add Notion, GitHub, Linear or any other server as many times as you need. Each entry keeps its own sign-in. **Do I have to sign in to Notion again when I switch Claude accounts?** No. In Shuriken an MCP sign-in belongs to the server entry, not to your AI account, so switching sources or projects never asks again. **Do my other computers need their own Notion sign-in?** No. MCP sign-ins sync between your devices, servers included, sealed end to end. Our cloud sees a hash and a sealed box. **Does this work for Codex as well as Claude Code?** Yes. Every Codex and Claude Code chat in a project is handed the same servers when it starts, and so are Gemini CLI, GitHub Copilot, Cursor and OpenCode chats. Global MCPs One MCP list for every agent. Add an MCP server once, choose its projects and sign in once. Your Claude Code, Codex and Gemini CLI chats all get it. [Try Shuriken](https://shuriken.sh/) [How it works](https://shuriken.sh/features/global-mcps) ## Keep reading - [Best MCP servers for Claude Code (2026): Story 27 Oct 2026 4 min read Our MCP picks for Claude Code, by job: GitHub and Sentry, Linear and Notion, Context7 and DeepWiki, Playwright, Supabase, Neon, PostHog and Stripe.](https://shuriken.sh/blog/best-mcp-servers-for-claude-code) - [How to add an MCP server to Codex CLI: Guide 27 Oct 2026 4 min read Add an MCP server to Codex CLI with codex mcp add and the server's command, or write its table in config.toml. OAuth servers sign in with codex mcp login.](https://shuriken.sh/guides/codex-cli-mcp-servers) - [Codex MCP server failed to start or timed out: fixes: Guide 27 Oct 2026 6 min read In Codex, "MCP client failed to start" means the command or handshake broke; "timed out after N seconds" means a slow server: raise its startup timeout.](https://shuriken.sh/guides/codex-mcp-server-failed-to-start) - [Shuriken vs Agentastic (2026): Comparison 27 Oct 2026 7 min read Agentastic is a free Mac multi-agent IDE with Design Mode and cloud targets. Shuriken runs on Mac, Windows and Linux and moves chats between your accounts.](https://shuriken.sh/compare/agentastic) - [Claude Code MCP server failed to connect: how to fix it: Guide 27 Oct 2026 6 min read Claude Code says Failed to connect when an MCP server never starts or answers. claude mcp get prints the error; a relative path is a frequent cause.](https://shuriken.sh/guides/claude-code-mcp-server-failed-to-connect) ## Free tools - [Claude limit reset tracker](https://shuriken.sh/tools/limit-resets/claude) - [Codex limit reset tracker](https://shuriken.sh/tools/limit-resets/codex)