Cannot add two custom MCP connectors with the same server URL (blocks multi-account use cases)

[fullstck]

What happened?

Claude.ai rejects adding a second custom MCP connector if the Remote MCP server URL is already used by another connector, with the error:

Error: A server with this URL already exists

This blocks any legitimate multi-account use case where the same MCP server (e.g. Stripe, Notion, Linear) needs to be connected with different OAuth identities.

What did you expect to happen?

Allow multiple connectors with the same MCP server URL as long as the connector name is unique. Each connector would maintain its own independent OAuth session and credentials. The combination of (URL, name) should be the uniqueness key, not URL alone.

This is especially important for Claude Code routines, where per-routine connector selection is already supported but loses meaning if you can only have one Stripe (or one Notion, etc.) connector per account.

Steps to reproduce

1. Add a custom connector named Stripe Account A with URL https://mcp.stripe.com → authenticate via OAuth with Stripe account A ✅
2. Try to add a second custom connector named Stripe Account B with the same URL https://mcp.stripe.com → ❌ blocked with "A server with this URL already exists"

Area

MCP Connector (adding/managing servers)

MCP Server (if applicable)

No response

Error messages or logs

Error: A server with this URL already exists

Additional context

No response

[jeannen]

My users are experiencing the same issue, would be great to fix that...

A small fix I found for them in the meantime: Add a query parameter at the end of the URL, which makes it unique for claude.

Ex: mcp.adkit.so => mcp.adkit.so?project-name

The issue is that CLaude seems to silently strip the query parameters after, so there is no way for it to know which one is which. Since the URL is the same it assume it's a duplicated MCP and default to the first one

[jpduckwo]

It'll be really, really good to see this one. Having multiple different accounts on the same MCP server is a very common use case going forward, I think. For example, I have work and personal accounts on Notion MCP, but there's no way to authorise both at the same time. The chat should also take into consideration the name you've given the connection so that it can distinguish which one to interact with at inference time.

[robinsondan87]

This is something I would like to see as i also work with multiple personal accounts for the same MCP.

[aupuzikov]

hi everybody, this kind of a bug is the smallest as it can be, can you guys fix it?

[jaanttil]

+1 on this.

Hit the exact same issue trying to connect two separate Salesforce orgs (two orgs due to recent acquisition) to the same Claude Enterprise account. Both orgs use Salesforce's standard hosted sobject-reads server which has a single global URL for all production orgs (https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads). Each org has its own External Client App with distinct OAuth credentials, but the duplicate URL check blocks the second connector entirely.

I could create custom MCP server in Salesforce side to get custom URL, but then I would also need to reimplement basic standard tools such as:

• Query Records (SOQL) (soqlQuery)
• Search Across Objects (SOSL) (find)
• Get Object Schema (Enhanced) (getObjectSchema)
• Get Related Records (getRelatedRecords)

[jaanttil]

+1 on this.

Hit the exact same issue trying to connect two separate Salesforce orgs (two orgs due to recent acquisition) to the same Claude Enterprise account. Both orgs use Salesforce's standard hosted sobject-reads server which has a single global URL for all production orgs (https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads). Each org has its own External Client App with distinct OAuth credentials, but the duplicate URL check blocks the second connector entirely.

I could create custom MCP server in Salesforce side to get custom URL, but then I would also need to reimplement basic standard tools such as:

• Query Records (SOQL) (soqlQuery)
• Search Across Objects (SOSL) (find)
• Get Object Schema (Enhanced) (getObjectSchema)
• Get Related Records (getRelatedRecords)

Update: Claude Enterprise duplicate URL workaround found

Adding a dummy query parameter to the URL bypasses Claude Enterprise's duplicate URL check:

https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=foo
https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=bar

At least Salesforce ignores the extra parameter so the MCP connection still works normally. This unblocks the immediate multi-org registration problem on the Claude side.

[robinsondan87]

Update: Claude Enterprise duplicate URL workaround found

Adding a dummy query parameter to the URL bypasses Claude Enterprise's duplicate URL check:

https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=foo https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=bar

At least Salesforce ignores the extra parameter so the MCP connection still works normally. This unblocks the immediate multi-org registration problem on the Claude side.

I have used the same but am concerned this workaround is a ticking timebomb that could break on any future release.

[douglasbhillsong]

+1 so we can connect to multiple instances of PlanningCenterOnline. + Stripe.

[rogersmj]

Adding a dummy query parameter to the URL bypasses Claude Enterprise's duplicate URL check:

I tried this workaround for Google, because I want to use the official Google MCP servers for multiple accounts, but it didn't work -- Claude wouldn't connect.

Anthropic really needs to fix this, this is ridiculous the hoops I'm trying to jump through just to get Claude to talk to more than one Gmail account.

[naji247]

It'll be really, really good to see this one. Having multiple different accounts on the same MCP server is a very common use case going forward, I think. For example, I have work and personal accounts on Notion MCP, but there's no way to authorise both at the same time. The chat should also take into consideration the name you've given the connection so that it can distinguish which one to interact with at inference time.

Worked for my use-case with Superhuman connector :) thanks!

[JackieGrubbs]

+1 would love to see a fix.

We tried this but unfortunately didn't work for us.

Update: Claude Enterprise duplicate URL workaround found
Adding a dummy query parameter to the URL bypasses Claude Enterprise's duplicate URL check:
https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=foo https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads?org=bar
At least Salesforce ignores the extra parameter so the MCP connection still works normally. This unblocks the immediate multi-org registration problem on the Claude side.

I have used the same but am concerned this workaround is a ticking timebomb that could break on any future release.