[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)

+1 on this. Same issue across all surfaces (web app, CLI, Cowork).

I run a wealth advisory firm and a separate investment fund alongside personal accounts -- three Gmail/Workspace accounts total. Meeting prep is a core workflow: search email history with a contact, pull calendar context, cross-reference with relationship notes. Right now that prep only searches one-third of my correspondence.

The web app's Gmail integration has the same single-account limitation. This isn't just a Cowork/CLI issue -- it affects the entire Claude ecosystem.

Ideal: connect multiple Google accounts and specify which to search (or search all). Even a simple account switcher in settings would be a significant improvement over the current single-account constraint.

+1 . Especially interested in multiple Gmail accounts to manage my mailbox properly.

Same here!

Same here, I need two gmail accounts in claude desktop

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 !

+1

+1 A classic in CoWork I think many people could really need is to have more than one Gmail accounts/connectors for different email addresses...

+1

+1

+1

+1

+1, would be great for gmail connector

+1

+1 along with multiple google workspace profiles, multiple chrome profiles, multiple m365 profiles, multiple slack profiles

+1

+1

This would be very important to me, in using for work + personal use. I manage multiple GitLab instances. I have more than one Google account. Being able to connect to different accounts and keep them in separate profiles would be a huge win.

+1

+1

+1

+1. I have roughly 10 or so email address across personal , work, non-profit support, etc. Would be great to have a way to link them all quickly.

+1

+1

+1, multiple gmail accounts

+1

+1

+1

+1

+1 for multi gmail accounts support

+1

• 1

Need two gmail accounts with Claude!

+1

+1

+1

+1

+1 need this badly

+1

+1

+1

+1 I need 4 Gmail accounts, two Slack spaces, and two ClickUp workspaces...I have a personal, and own three businesses

+1

+1

+1

+1

+1

+1

+!

+1

+1

+1

+1 - Need this for managing different Airtable accounts. I manage most of these Airtable Workspaces or Bases from my own account, but some clients give me their own Airtable account, which would require me to have an additional MCP connection.

+1

Need this so much 🥺

+1

+1

+1

+1. Not just Github, other connectors too - Slack, Gmail, Drive etc.

+1 my wife is a freelance digital marketer and works with multiple clients. Some clients create separate work Google accounts for her to work in. She is limited on what she can do with Claude Cowork because she can’t connect multiple Google accounts. For example, a simple “plan my day” prompt doesn’t work well because it only pulls in context from one calendar.

Would love this for Slack — I have multiple workspaces and currently can only connect one at a time through the managed integration. Multi-workspace support would be a big quality-of-life improvement.

+1

+1

How about having them _per project?_ That could be a start nonetheless.

+1 👍 🙏

this is a big one for many people

+1 - I have 4 gmail / workspace accounts. personal, work, side business, volunteer

Adding a fractional/consulting use case to this request.
I'm a fractional CFO — I work across my firm's Slack workspace, multiple client Slack workspaces, and professional communities (e.g., Operators Guild) that each run their own Slack. I also straddle a corporate Google Workspace (firm) and personal Google accounts. This is the default configuration for anyone in fractional, consulting, or advisory roles — not an edge case.
The current workaround of disconnecting/reconnecting between workspaces, or maintaining separate Claude accounts, is impractical for people whose entire job is working across organizations simultaneously. In a single work session I might need to:

Search my firm's Slack for a proposal template
Reference a conversation in a client's Slack workspace
Pull context from a professional community's Slack (prospecting, peer advice)
Access Google Drive docs from both my firm's Workspace and a client's

This isn't just a convenience request — it's a core workflow gap for the growing fractional/consulting economy. The single-connector model assumes one employer, one workspace, one Google account. That assumption doesn't hold for fractional executives, consultants, agency operators, or anyone with a portfolio career.
Suggested approach: Allow multiple instances of the same connector, each authenticated to a different workspace/account, with a clear label (e.g., "Slack — COMPANY," "Slack — Operators Guild"). Bonus: scope connector visibility per-Project so that client data isolation is maintained — a fractional CFO working in a "Client A" project should only have Client A's Slack and Drive active, not every connected workspace.
This would be a strong differentiator for Pro and Max plans, where professional users are most likely to have this need.

+1

Was excited about using Cowork for coordination across personal and several different organization's google, slack and notion instances and found this a dealbreaking limitation. +1

+1

+1

+1

+1

A Notification start hook can switch connector configurations based on project:

PROJECT=$(basename "$PWD")
CONNECTOR_DIR="$HOME/.claude/connectors"
PROFILE="$CONNECTOR_DIR/$PROJECT.json"
if [ -f "$PROFILE" ]; then
    echo "[Connector] Loading profile for: $PROJECT" >&2
    cp "$PROFILE" "$HOME/.claude/active-connector.json"
else
    echo "[Connector] Using default profile" >&2
fi
exit 0

Structure:

~/.claude/connectors/
├── work-project.json      # Work Google account
├── personal-project.json  # Personal Google account
└── client-project.json    # Client's account

Each profile contains the connector credentials for that context. The hook auto-loads the right one when you cd into a project.

+1

+1 - I really want to have cowork work with my 3 multiple gmail accounts in one task: personal, professional, work account

i am connecting to multiple supabase/postman organizations and would like to have the same.

+1

+1

+1

+1

+1

Hey everyone. I built a plug-in that solves this problem.

I can share it if you want, but I'd encourage you to build your own.

Even with my code, you will need your own Google Cloud Console project for validation of OAuth requests, and a internet connection you control.

If you have the repo, claude will install the plug-in. You'll need to keep port 5001 clear for the local mcp server, and 5000 clear for the access terminal.

It will run on app startup.

+1 - it works fine within claude code for Atlassian, with local repo MCP connectors. but it would be helpful for this in the cloud as well as i use the latter for research, writing, and presentation and spec creation (and dissemination to clients via Confluence & partner devs via Jira) but then do the coding & deployments via Claude Code.

+1 - it works fine within claude code for Atlassian, with local repo MCP connectors. but it would be helpful for this in the cloud as well as i use the latter for research, writing, and presentation and spec creation (and dissemination to clients via Confluence & partner devs via Jira) but then do the coding & deployments via Claude Code.

I totally agree. It would work best as a cloud based service. I just wont be the one to build it.

I don't have enough experience in security to responsibly handle people's data, the cost of the infrastructure would likely outpace a reasonable payment structure, and I imagine that anthropic will solve this issue on their own rather shortly.

You're welcome to build on top of my program if you find it useful.

Have at em: https://github.com/ethanliebermanjude/multi-gmail

I would also love this feature

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1, I need multiple Notion workspaces.

+1. Need this.

+!

+1

Absolutely needed !

+1

+1

+1

+1

+1

+1

+1, I’d like to have the ability to use both Gmail accounts in Claude

Really need this! +1

+1

+1

+1

+1

+1

+1

+11

+1 :)

+1

+1

+1

+1

+1

+1

+1

+1

+1 - would be great for slack and gmail

+1

+1
gmail would be so needed!

+1!!!!

+1
this is really needed

+1

+1

+1

+1

+1 would love this in notion

+1

+1 - I need multiple of the same connector for Google Drive, Canva

+1

+1

+1

A simple MCP to support multiple gmail accounts connecting: https://github.com/gx-55/multi-gmail-mcp

+1 gmail & asana

+1

My workaround:
Add gmail MCP manually (Connectors -> Add Custom Connector -> Enter any custom name -> "https://gmailmcp.googleapis.com/mcp/v1?" for the URL).
Note that we have a "?" in the end of the URL. We do it so Claude allows us adding more same MCPs.

This worked for my second email address. Theoretically, you can play around for adding some other stuff into the query params to add other gmail accounts.

I doubt anyone from Anthropic will read this, but this limitation is the primary reason people are using OpenClaw. Seems so simple to fix and would literally kill the value-add of your competition

@bcherny What do you think of this proposal? It seems like it's garnering quite the response, and as someone points, it would steal a lot of OpenClaw's thunder by making one of its core competencies a first-class capability of Claude.

+1

@mashkovtsevlx you are a life saver thank you!!

Gmails connector gives you a lot less flexibility than a custom mcp server. I'm running 2 custom gmail mcps (with tagging, email sending and much more that gmail mcp restricts) on railway, 2 notion servers, Xero, clockify, and a load more remote servers behind oauth which means I can run my entire business and personal life from Claude desktop AND mobile without security concerns and for under $1 a month.

If anyone is interested I would happily set up remote mcp servers for others at the same cost.

The thing about the workaround @mashkovtsevlx proposes is that it only seems to work for _exactly_ two accounts: adding ? to the URL passes, but then adding any parameters will cause the OAuth handshake to fail - tested so far with name=foo and 0=0 (just in case name is a reserved parameter key).
On a hunch I also tried #, since the fragment should not be parsed on the server-side, but could create a different URL. That is also a non-starter, since Claude validates the URL _after_ stripping away the fragment, and then it no longer passes the duplication gate.

So it's a step in the right direction, but not an end-run around the limitation.

The thing about the workaround @mashkovtsevlx proposes is that it only seems to work for _exactly_ two accounts: adding ? to the URL passes, but then adding any parameters will cause the OAuth handshake to fail - tested so far with name=foo and 0=0 (just in case name is a reserved parameter key). On a hunch I also tried #, since the fragment should not be parsed on the server-side, but could create a different URL. That is also a non-starter, since Claude validates the URL _after_ stripping away the fragment, and then it no longer passes the duplication gate. So it's a step in the right direction, but not an end-run around the limitation.

Have you tried ending the URL with &? Maybe the OAuth flow is failing because the parameters are being concatenated incorrectly. Not a solution, of course, but easy and worth trying.

@IlanVivanco I did now, and my initial thought was correct: will not work.

It _should not work_, because https://gmailmcp.googleapis.com/mcp/v1& is definitely an invalid URL, as the & is part of the reserved characters in the URI scheme:

reserved      = gen-delims / sub-delims
gen-delims    = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims    = "!" / "$" / "&" / "'" / "(" / ")"
                 / "*" / "+" / "," / ";" / "="

I did just try every one of the sub-delims set, and all of them produced an error. This is telling me that the only reason ? works is that it produces a valid URI with a query of null, which is equivalent to _not having_ a query at all.
I even went a step further, trying a percent-encoded URI or https://gmailmcp.googleapis.com/mcp/v1%20, which should produce an equivalent result after a trim, but this also failed.

My working theory is that the OAuth flow on Google's side uses strict equivalency checking, which would make sense given the sensitive nature of the access being granted.

So for _two_ accounts, @mashkovtsevlx 's workaround is viable; for three or more, we would native support for multi-account MCPs in Claude.

adding my +1 to requiring this. I have several accounts that are even for one organization - shared sales accounts, my own email with that company, etc. Then also personal emails, family shared emails/calendars, as a contractor too i have several other emails that need to all be scanned in one workflow in order to get a full picture.

+1

@thunderbird89 @IlanVivanco is the /v1? workaround still working for y'all? looks like once i try and auth it errors for me. see below

Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: "ofid_c43e9d588c964c02"

@thunderbird89 @IlanVivanco is the /v1? workaround still working for y'all? looks like once i try and auth it errors for me. see below

It does work for me with Notion connectors.

+1 Working at a company with a history of mergers and acquisitions, this feature is desperately needed to enable Claude to switch between projects and Google Drive contexts.

My workaround: Add gmail MCP manually (Connectors -> Add Custom Connector -> Enter any custom name -> "https://gmailmcp.googleapis.com/mcp/v1?" for the URL). Note that we have a "?" in the end of the URL. We do it so Claude allows us adding more same MCPs. This worked for my second email address. Theoretically, you can play around for adding some other stuff into the query params to add other gmail accounts.

Thanks for the workaround, but it doesn't work for me

<img width="527" height="92" alt="Image" src="https://github.com/user-attachments/assets/c84a5340-fa8f-4711-b218-dc521a1b94df" />

@maikol-solis Looks like Google patched their MCP infrastructure to throw a 404 for any URL that isn't the "official" one, including equivalent-but-not-equal ones.

Notably, existing connections are also broken now, so @mashkovtsevlx 's workaround no longer works, even for previously-added connections.

@bcherny looks like interest will start to mount soon for multi-account connections...

@nathanmargaglio

Found a fix for this! An MCP Broker like Bellatrix One aggregates all your MCP Server connections into a single connection. I was able to set it up in just a few minutes.

For CLI users hitting the multi-account pain in this thread, there's a config-dir-level workaround that's been
working reliably on Windows since 2026-05-15:

1. CLAUDE_CONFIG_DIR environment variable scopes the entire .claude.json + skills + projects directory.
2. Pair with a junction/symlink so Claude Desktop and Claude Code each read a separate config dir — each with its

own MCP + Connector set.

1. Wrapper scripts (per-account claude-personal.cmd / claude-work.cmd) toggle which config the CLI launches

with.

End result: two account contexts coexist on one machine with separate Connector setups, no logout/login churn.

Doesn't help the Desktop-only case asked here directly, but the env-var pattern is the closest existing primitive —
porting it to Desktop ("which .claude.json does this window read") would address the bulk of the multi-account
complaints in this thread without needing in-app account switching UI.

Detailed runbook + scripts: https://github.com/MankhongGarden/claude-code-multi-context-windows

+1 Need this feature to work on cloud environments .

While I wait for a fix on this, can anyone recommend a third-party Gmail MCP they've had a good experience with? Looking for the widest Gmail feature coverage (filters, labels, send, drafts, etc.) from one you also consider safe to install.

+1

+1

+1

+1 Needed for switching between Notion workspaces and Linear workspaces

+1 there should be some way of working on multiple accounts, I want my personal stuff and work stuff to be separated. but Control both from same claude.

+1 heavy apart of a lot of my workflows for connectors like notion

+1 notion

For developers hitting this on the web app while also using Claude Code CLI on the same machine, the CLI side of the multi-account pain has an operator-side bridge that shipped this week (the desktop/web/mobile sides still need the harness-layer fix this issue is asking for).
For the CLI specifically, two new MIT-licensed hooks in cc-safe-setup catch the "wrong account loaded" failure mode at session start:

• account-routing-preflight.sh (SessionStart) — refuses the session with exit 2 when ANTHROPIC_ACCOUNT_LABEL doesn't match .claude/expected-account for the project.
• account-billing-log.sh (Stop) — per-session pipe-separated billing log for consultants invoicing clients off the same machine.

These don't help with the Connectors per-account issue on the web app — they're CLI-only. But for the cohort that runs CLI alongside web, they at least keep the CLI billing clean while the web app waits on the fix.
Field guide for the five-pattern operator-side workaround (shell alias / direnv / ~/.claude symlink / SessionStart preflight / billing log): https://gist.github.com/yurukusa/d880ecc984af5d664f003daf85f956e3
Cluster context: this issue + #18435 + #36151 = ~1,178 cumulative reactions across three platforms. The signal seems large enough to warrant prioritization but the platform-specific shape of each is the part that still needs the official UX fixes.
— independent operator; not affiliated with Anthropic

+1 notion

+1

+1

+1 GitHub

+1

+1

+1 how is this not a thing?

The ask
Let users connect more than one instance of the same MCP connector, each authenticated against a different workspace/account/tenant of the underlying service.

Current behavior
The connector registry models each MCP server as a singleton. The "Linear" entry, for example, can be in one of two states: connected (one OAuth grant, one workspace) or not connected. There's no UI affordance to add a second Linear connection pointing at a different Linear workspace. The same shape applies to every connector whose underlying product has a workspace/org/tenant boundary — Slack, GitHub, Notion, Atlassian, etc.

What I tried to do
I run two Linear workspaces:

MossBD — Moss Building & Design's Linear org
Renolution — separate Linear org (separate Linear tenant)

I asked Claude to build a personal Cowork live artifact that pulls in-progress issues, recently completed issues, and open PRs from both workspaces. Claude built the dashboard against the connected MossBD workspace, then we discovered:

list_teams on the Linear MCP only returns teams from the one authenticated workspace (MossBD). Renolution is invisible.
The MCP registry exposes a single "Linear" entry. It's already connected: true. There's no "add another instance" / "duplicate connection" path in the UI.
The only ways forward today are (a) re-authenticate the existing connector against Renolution, losing live MossBD access, or (b) migrate Renolution work into MossBD's Linear as a team — a Linear-admin migration that's not justified for a dashboard.

So the request died at the connector layer, not the dashboard layer.
Desired behavior
When a user clicks Connect on a connector that's already connected:

Either let them add a second instance with its own OAuth grant, labelled by something distinguishing (workspace name, account email, custom nickname)
Or, when they invoke a connector's tool from chat / from a live artifact, let them pass an instanceId so the right one is targeted

In Claude's tool surface, each instance would appear as its own tool namespace (e.g. mcp__linear_mossbd__list_issues and mcp__linear_renolution__list_issues), or the existing mcp__<uuid>__<tool> pattern would gain a second uuid per instance.
Why it matters
This isn't a niche edge case. Anyone who:

consults across multiple clients (each with their own workspace)
runs a parent company and a subsidiary
works across personal and employer accounts in the same tool
needs to view a customer's data alongside their own (e.g., a vendor with multiple customer Slack guest seats)

…runs into the same wall. Cowork's value proposition leans heavily on "all your tools in one place," and that proposition breaks the moment "your tools" includes two workspaces of the same product.
It also blocks a category of high-value live artifacts: cross-workspace dashboards, cross-tenant digests, unified inboxes. Today every one of these hits the same singleton constraint.
Workarounds I've considered

Disconnect and reconnect per session — operationally painful, kills the "live" property of live artifacts.
Move Renolution into MossBD's Linear org as a team — wrong migration for the wrong reason; mixes billing, permissions, and search across two distinct businesses.
Build a parallel dashboard from a different connector — only works when the second workspace's data happens to also live in a second product (e.g., a construction-management MCP). Doesn't generalize.

Suggested rollout
Even a minimal version would unblock most of the pain:

Allow "Add another instance" on already-connected connectors, with a user-provided label.
Surface instances clearly in the registry UI ("Linear — MossBD" / "Linear — Renolution").
Expose each instance as its own tool namespace to Claude.

That's enough to make the Linear dashboard above work for both workspaces simultaneously, and unlocks every other "multi-workspace" use case at the same time.

+1

+1

A simple MCP to support multiple gmail accounts connecting: https://github.com/gx-55/multi-gmail-mcp

This implementation worked for me! Thanks man!

+1

I really need this. Kinda silly I can't use my Claude code on iOS/web for both my personal GitHub and my portfolio GitHub. They're separate things!

this must be most requested feature, how can't we get it.

+1

+1

+1

+1

This is a requirement. As software developers, we need to have access to multiple Notion workdspaces. @claude is this going to be fixed?

+1 on this! For Notion and Gmail and M365

+1

+1 especially for Notion (multiple workspaces)

Connecting via Composio was the fix for me. It also opened up so many more tools.

Connecting via Composio was the fix for me. It also opened up so many more tools.

Thanks @imex-git, Composio worked for me. All my Gmail accounts and Notion workspaces connected to Claude after a 4min setup 🙌🏼

Now I'm exploring what else to connect from the directory

> Connecting via Composio was the fix for me. It also opened up so many more tools. Thanks @imex-git, Composio worked for me. All my Gmail accounts and Notion workspaces connected to Claude after a 4min setup 🙌🏼 Now I'm exploring what else to connect from the directory

Its an amazing tool! and they give you 20K free tool calls per month, which is more then plenty for individual users.

+1

+1

Two notes that might be useful:

1. Gmail / multi-account handling

Haven’t really solved this cleanly in code yet, but there are a couple of practical workarounds I’ve seen work:

In my setup, I’ve mostly consolidated multiple email addresses into a single Gmail account, which sidesteps the multi-account issue entirely.
If you do need multiple accounts, a workaround is splitting them across providers/integrations:
1 Gmail → direct to Claude
1 Gmail → via Zapier
1 Gmail → via Make

It works for a small number of accounts, but doesn’t scale well beyond that.

1. Klaviyo + Claude

We ran into the multi-account limitation more directly with Klaviyo, so we ended up solving it by building a small “dash” app that sits in between.

The app connects to multiple Klaviyo accounts
Claude connects once via a custom MCP
The app handles routing across all accounts internally

So instead of Claude managing multiple integrations directly, everything goes through the dash layer.

Link to the app here: [dash.razico.co](url)

+1 This would be a great feature

+1 I would love this

+1