Access + Refresh Tokens get overwritten with multiple MCP configs

[tomekchime]

New issue?

• I have reviewed the Existing Issues and confirm this is not an existing issue.

Bug

I have 2 separate MCP configs, one pointing to a sandbox Okta instance, and another pointing to our production instance. I noticed that if I have both enabled, one of them does not work.

I believe what's happening here is that the okta-mcp-server will fetch access + refresh tokens and store them as OktaAuthManager entries. Since they use the same name and account, they are overwriting each other.

Expected behavior

I would expect the okta-mcp-server to be able to handle MCP configs for 2 separate Okta instances simultaneously.

Observed behavior

No response

Relevant log output

Additional information

No response