[docs-scanner] OAuth credentials sharing contradicts profile isolation model

[github-actions]

File: content/manuals/ai/mcp-catalog-and-toolkit/profiles.md

Issue

The documentation states that OAuth credentials are shared across all profiles, which contradicts the profile isolation model described throughout the MCP documentation.

From profiles.md:

OAuth credentials are shared across all profiles. When you authorize access to a service like GitHub or Notion, that authorization is available to any server in any profile that needs it.

This means all profiles use the same OAuth credentials for a given service. If you need to use different accounts for different projects, you'll need to revoke and re-authorize between switching profiles.

This contradicts the core concept of profiles as isolated collections. Throughout the documentation, profiles are described as separate workspaces for different projects or environments. Users would reasonably expect that a "web-dev" profile and a "data-analysis" profile would maintain separate credentials, especially when the documentation emphasizes that "each profile maintains its own isolated collection of servers and configurations."

Why this matters

Users creating separate profiles for different clients or projects will be confused when they discover that OAuth credentials are shared. For example:

• A developer with separate profiles for personal and work projects expects to use different GitHub accounts
• A consultant with profiles for different clients expects to use different service credentials
• A team member testing a profile expects it not to affect their production profile's credentials

The current behavior forces users to revoke and re-authorize between profiles, which undermines the value proposition of profiles as isolated workspaces.

Suggested fix

Either:

1. Change the implementation so OAuth credentials are scoped to profiles (if technically feasible), or
2. Add a prominent warning about this limitation at the top of the profiles documentation and in the "Creating and managing profiles" section, not just buried in the "OAuth credentials" subsection

If option 2, the warning should be clear and early:

Important: OAuth credentials are currently shared across all profiles. If you need to use different accounts for different projects, you'll need to revoke and re-authorize when switching profiles. This limitation may be addressed in future versions.

---

Found by nightly documentation quality scanner