Hi Community,
I noticed when adding an External MCP server as an admin, that it asked for my OAuth credentials to connect it. Fair enough for testing a valid server, but then when I asked Rovo, I was suprised at the response --
Which credentials are used (yours vs the admin’s)?
1) For an external MCP server
In most setups, the MCP server does not automatically “use your personal credentials.” Instead:
Rovo calls the MCP server endpoint that your admin connected in Atlassian Administration → Connected apps.
The gateway then authenticates however it was configured (commonly a service account / shared credential managed by admins).
Unless the server was explicitly built to do per-user delegated auth (for example, it triggers a user-specific OAuth/SSO flow or stores user tokens), the external system will typically see actions coming from that service account identity, not from “Nick”.
This was pretty limited -- https://support.atlassian.com/organization-administration/docs/configure-tools-for-an-external-mcp-server/
Has anyone configured an External MCP Server, and then when in Rovo, all users attempting to use that server were able to provide their credentials (OAuth flow) to that other service to use those tools exposed as that user?
thanks in advance,
nick
