member badge
Arunkumar Kumaresan
Users with more than one Document360 project (for example, a product knowledge base and a separate API docs project) cannot access both within the same Claude session. The current design allows one project context per session, requiring a reconnect to switch. This means users who manage multiple projects must interrupt their workflow to switch context, and Claude cannot draw on content from more than one project at a time.
Workaround Limitations:
  1. Switching projects requires a manual reconnect step, interrupting the session
  2. Claude cannot cross-reference content across projects in a single session
  3. Users with related projects (e.g., product docs + API docs) lose the ability to get unified answers
Requested Solution: Allow users to connect more than one Document360 project to a Claude session simultaneously. Specifically:
  1. Let users select multiple projects during MCP connector setup
  2. Give Claude access to content from all connected projects within the same session
Benefits:
  1. Users managing multiple related projects can work without interruption
  2. Claude can provide answers that draw on content from multiple project contexts
  3. Reduces friction for teams with split documentation across projects
Use Cases: Teams with separate product docs and API docs projects, organizations with regional or language-specific projects, teams migrating content between projects