I have built an MCP plugin for our ERP software in Cursor & Grok Bot, several iterations. Initially Local only, then a fully hosted MCP on my personal developer domain to thoroughly test Cloud Agent MCP connections before publishing to marketplace.
No matter what I do, every line of documentation crossed, you guys do not allow me to configure multiple MCP connections on the same MCP plugin, for example, how Notion will let me “Add Another Environment” within the Cursor UI to auth into various Notion spaces. See screenshot.
Steps to Reproduce
Create your own cloud MCP plugin for Cursor and set it up.
Be disappointed.
Expected Behavior
I expect my clankers to be able to code & create MCP/Cursor Plugins that work the same as first party enterprise MCP/Plugins like Notion and similar. I do not want a second class Cursor Plugin/MCP experience.
Multiple accounts per MCP server isn’t limited to first-party plugins. It works the same way for any remote (HTTP) MCP plugin, including ones you publish yourself, as long as the server authenticates with OAuth.
Could you share how your hosted server authenticates (OAuth or API key)?
Looks like it is via API Key, as that is the only option available from the software vendor we built this MCP server for. They don’t expose OAuth for middleware, only API Keys.
Hey @durden, thanks for confirming, that explains what you’re seeing!
“Add Another Account” is tied to OAuth sign-in. For a server that authenticates with an API key, a plugin install holds one set of credentials right now, so there’s no second account to add. Multiple API keys on a single plugin isn’t supported yet, and I’ve passed the request along.
In the meantime, there are two ways to get the same result:
Add your server as separate custom MCP entries, each with its own name and its own API key header (for example odoo-prod and odoo-sandbox). Give each entry a slightly different URL, such as https://odoo-json2.tylerjharden.dev/mcp?env=prod, so they’re not treated as the same server. For Cloud Agents, add these entries from the MCP settings on cursor.com/agents.
Since you host the MCP server yourself, you could add OAuth in front of it: your server handles sign-in and asks for the Odoo instance and API key on its own login page. Cursor will then treat it like any other OAuth server, and “Add Another Account” will show up in the desktop app. Cloud Agents currently use one account per server, so option 1 is the better fit there.