Inline plugins (zoom-plugin, pdf-viewer, prisma) reconnect after Disable; zoom-plugin has an Authorization header the account never set
Summary
Several bundled/inline plugins keep re-enabling themselves and cannot be
permanently disabled from the Plugins UI, even with only a single device
signed in. One of them (zoom-plugin) fails auth with a credential the
account never created.
Symptoms
- Zoom (3 servers:
zoom-mcp,zoom-docs-mcp,zoom-whiteboard-mcp)
fail every session with AUTH_HEADER_REJECTED / HTTP 401
Invalid access token, e.g.:
````
Server rejected the configured Authorization header (HTTP 401). Check that
the token is valid for this MCP endpoint — OAuth fallback is disabled when
headers.Authorization is set.
The account has never connected a Zoom account, so there is no
user-created token to be invalid or to revoke. The error implies a
pre-populated Authorization header exists for this connector that the
user never configured.
pdf-viewer:pdfandprisma:Prisma-Localfail to connect every
session (Skipping connection (recent failure cached retries). No local config or executable reference
automatically in 15 min...)
for either exists anywhere under ~/.claude/plugins/ — the on-disk data
directories (~/.claude/plugins/data/prisma-inline,
~/.claude/plugins/data/pdf-viewer-inline) exist but are empty, so there
is nothing on the local machine to fix or remove.
- Disabling these plugins from the Plugins UI does not persist.
Toggling a plugin to "Disabled" is reflected in the UI at the time, but
on a later check the same plugins reappear as active (listed again under
"requires authentication" / "failed to connect" in a fresh session),
even with only one device signed into the account at the time.
Expected behavior
- Disabling a plugin should permanently stop it from being loaded/attempted
in future sessions until re-enabled.
- A plugin should not carry a pre-configured Authorization credential the
user never supplied, and should not perpetually retry a connection using
it.
Environment
claude plugin list(local CLI) reports "No plugins installed" — these
plugins do not appear in any locally managed marketplace or project/user
mcpServers config. They are account-level "inline" plugins not
represented in ~/.claude.json or ~/.claude/plugins/marketplaces/.
- macOS (darwin), Claude Code CLI.
Reproduction
- Start a Claude Code session with the
zoom-plugin,pdf-viewer, and
prisma plugins enabled (default/inline for this account).
- Observe the connection-failure system reminders listed above at session
start.
- Disable the three plugins via the Plugins UI.
- Start a new session (single device signed in) — the same plugins still
appear as enabled/attempting connection.