Two Notion workspaces, one MCP list

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 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:

1. Add Notion, call it something like "Notion (work)", and sign in with your work workspace.
2. 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.

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 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 says what else our cloud can and can't read.

Set it up once#

That's the whole idea of Global MCPs: set up a server once, sign in once, and stop thinking about it. Our guide to MCP servers across all your projects goes through the setup step by step, with more examples than Notion.

If you've been juggling two workspaces by hand, try Shuriken and add the second one in a minute.