One MCP list for Claude Code, Codex, Gemini CLI and more.
Global MCPs are one list of MCP servers that your chats in Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor and OpenCode all get. You add a server once, choose its projects and sign in to it once, and that sign-in works on every account and follows you to your other computers.
The problem
Every agent wants its own MCP config, and every account its own sign-in.
MCP servers are set up per agent and often per project: a config file for Claude Code, another for Codex, another for Gemini CLI, and a sign-in that belongs to wherever you first approved it. Switch accounts or start a new project and you set the same servers up again.
How Shuriken handles it
How it works
-
Add a server.
Pick one of 57 ready-made connectors, or add any server by its address or command.
-
Choose its projects.
All projects, or just the ones that need it.
-
Sign in once.
Approve it in your browser one time. The sign-in is kept for that server.
-
Use it in every agent.
Every chat in those projects gets it, in Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor or OpenCode, whichever account it runs on.
The details
57 connectors
GitHub, Linear, Notion, Slack, Figma, Sentry, Stripe, Supabase and more, ready to add.
Handed to each agent
A chat is given the servers when it starts, so you never copy a config file from one agent to another.
Two accounts of one server
Work and personal Notion? Add it twice, sign each in to its own workspace, and give each the projects that need it.
Synced, end-to-end encrypted
Sign-ins travel between your computers sealed. The cloud sees a hash and a sealed box.
Good to know
- Switching accounts never asks you to sign in to an MCP again: the sign-in belongs to the server, not the account.
- Add server adds it on each of your computers that's online at the time.
- The list reaches chats, and Claude Code opened in a Shuriken terminal. Other agents opened in a terminal read their own config files, as they would without Shuriken.
- The cloud never sees an MCP token, only a hash and a sealed box.
Every server, one sign-in.
Your MCPs sit in the middle of everything: your projects, your accounts and your agents' chats.
- All projects or just some
- Sign-ins sync, end-to-end encrypted
- 57 ready-made connectors
57 connectors, ready to add
Or add any other server by its address or command.
- GitHub
- Linear
- Notion
- Slack
- Figma
- Asana
- Atlassian
- Sentry
- Datadog
- Canva
- Stripe
- PayPal
- HubSpot
- Intercom
- monday.com
- Airtable
- Box
- Cloudflare
- Vercel
- Supabase
- Neon
- Webflow
- Wix
- Netlify
- PostHog
- Square
- Context7
- DeepWiki
- Hugging Face
- Filesystem
- Git
- Fetch
- Playwright
- Memory
- Sequential Thinking
- Time
- Chrome DevTools
- Brave Search
- MongoDB
- Mobbin
- Exa
- Prisma
- Render
- Apify
- Amplitude
- Mixpanel
- Sanity
- Expo
- Jam
- Attio
- Todoist
- Clerk
- Socket
- PagerDuty
- Close
- Granola
- Trello
Questions
Which agents get the servers?
Your chats in Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor and OpenCode. Each chat is handed the list when it starts, and so is Claude Code opened in a Shuriken terminal. Other agents opened in a terminal read their own config files instead.
Do I sign in again when Shuriken switches accounts?
No. The sign-in belongs to the MCP server, not to your AI account, so switching accounts or projects never asks again.
Can I use two Notion workspaces?
Yes. Add Notion twice and sign each in to its own workspace, then give each the projects that need it. For one project only, the server's menu also has Use a different account.
Which servers can I add?
Any of the 57 ready-made connectors, such as GitHub, Linear, Notion, Sentry and Playwright, or any other server by its address or command.
Can the cloud read my MCP tokens?
No. Sign-ins travel between your computers sealed, end to end. The cloud sees a hash and a sealed box.
Bring your agents. Keep your accounts.
Free forever, with 2 sources and 2 linked devices. No card.