claude-code - 💡(How to fix) Fix Support per-project OAuth sessions for MCP plugins (e.g. Figma) [2 comments, 3 participants]

TL;DR

Implementing project-scoped OAuth sessions for MCP plugins, such as storing OAuth tokens per project path or adding an optional account field in the plugin config, is likely to resolve the issue.

Guidance

• To verify the need for project-scoped OAuth sessions, check if multiple projects require different OAuth accounts for the same plugin (e.g., Figma).
• Consider storing OAuth tokens in a project-specific configuration file, such as ~/.claude.json, to allow for separate sessions per project.
• Evaluate the feasibility of adding an account or profile field to the plugin config to map to different stored sessions.
• Assess the impact of this change on affected plugins, including Figma, Atlassian, Slack, and other OAuth-based MCP servers.

Example

No code snippet is provided as the issue focuses on the conceptual solution rather than a specific implementation.

Notes

The proposed solution requires changes to the MCP plugin architecture and configuration handling. The exact implementation details may vary depending on the specific requirements and constraints of the MCP ecosystem.

Recommendation

Apply a workaround by manually logging out and logging back in via /mcp → select plugin → re-authenticate, until a proper solution is implemented, as this is the current practical approach to manage different OAuth accounts for multiple projects.