Skip to content

[Bug]: Claude threads show a sign-in notice for every installed plugin's MCP server #40083

Open

Description

@Umais-Adeed

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. In Claude Code, install plugins that ship OAuth MCP servers, and don't connect them (for example the legal, engineering and design plugins from the official marketplace).
  2. In T3 Code on main (after feat: sign in to an agent's MCP server from its warning #39921), start any Claude thread, for example Haiku with "Reply with just: hi".

Expected behavior

No sign-in notices for servers the user never set up. Plugin servers should be skipped the same way unconnected claude.ai connectors already are.

Actual behavior

The thread gets one "The plugin:: MCP server needs a sign-in before Claude can use it." row per plugin server. With three plugins that's 9 rows (Slack, Egnyte, Atlassian, Linear, Notion, PagerDuty, Datadog, Figma, Intercom) on a one-word reply, and again in every new session.

ClaudeAdapterV2.announceMcpSignIns skips only scope === "claudeai". Plugin servers report source: "plugin" (and are named plugin:<plugin>:<server>), so they pass the filter.

Impact

Major degradation or frequent failure

Version or commit

f680c20 (main)

Environment

Linux, web client from vp run dev, Claude provider (Haiku 5.5).

Screenshots, recordings, or supporting files

9 plugin sign-in rows after a one-word reply

Workaround

Disable the unused plugins in Claude Code (/plugin).

Activity

  1. advwebin commented on Nov 21, 2026

    @advwebin

    Same thing here on the macOS desktop app.

    • T3 Code: 0.1.12-nightly.20261121.5038 (desktop, macOS)
    • Claude Code CLI: 2.1.329
    • Rows shown: plugin:firecrawl:firecrawl, plugin:design:slack, plugin:design:linear, plugin:design:atlassian, plugin:design:notion, plugin:design:intercom

    The design plugin here is the one synced from claude.ai (it lives under ~/.claude/plugins/synced/), not one installed from a marketplace, so plugins arrive this way too.

    This started with the update. The provider event logs from Nov 15 and Nov 19 contain the same "status":"needs-auth" entries with "source":"plugin" for these servers, but no notices were shown back then. The Claude side hasn't changed; only the display is new. Nothing is actually broken: Claude is authenticated and the turn completes normally.

    Screenshot below.
    e687bc9b-5427-4fcc-a1b6-2d7d4acd5898-ac29a9e9-6672-434d-9787-4381230b912c

  2. Haddadios commented on Nov 22, 2026

    @Haddadios

    Note

    🤖 Gemini 4 Neon responding on behalf of @Haddadios

    Confirming this also reproduces on the latest nightly with claude.ai synced plugins:

    • T3 Code: 0.1.12-nightly.20261122.5071 (macOS arm64 desktop)
    • Claude Code CLI: 2.1.330
    • Observed: 17 sign-in notices per Claude thread for unconnected MCP servers bundled in claude.ai synced plugins (productivity, marketing, engineering, design, data), e.g. plugin:productivity:slack, plugin:marketing:canva, plugin:engineering:datadog, plugin:design:intercom, plugin:data:hex.

    In the provider system/init log frame, all 17 entries report "status": "needs-auth" and "source": "plugin" with a plugin: name prefix, while the unconnected claude.ai connector reports "source": "claudeai" and is already skipped. #40085's isClaudePluginMcpServer check matches all 17 entries cleanly.

  3. Ilyed commented on Nov 22, 2026

    @Ilyed

    Hi, Just want to add in and say that I use the latest T3 code nightly as well and I have the same issue

    image

    And I have never used some of those tools or ever linked them to my claude mcps.

  4. nitinkhannaio commented on Nov 22, 2026

    @nitinkhannaio

    Related: user-added MCP servers produce the same stack of rows, and #40085 keeps announcing them on purpose. Filed separately as #40785, with a proposal to collapse adjacent sign-in notices into one row.

  5. realhasanshoaib commented on Nov 22, 2026

    @realhasanshoaib
    Contributor

    Same thing here with plugin:context7:context7 (from context7@claude-plugins-official), on T3 Code Desktop 0.1.12-nightly.20261122.5071 (commit 047fb5b), macOS 26 arm64, Claude provider.

    One more problem with the notice that #40085 doesn't cover: its Sign in button stops working once the Claude session unloads, but the button stays on the thread. In my case the thread was waiting on a delegated task, so its own turn had ended long before. Clicking Sign in opened the dialog, which immediately showed "The agent session has ended. Send a message, then sign in again."

    Server trace at the click:

    McpSignIn.resolve  exit Failure: ProviderMcpSignInError: The agent session has ended. Send a message, then sign in again.
    McpSignIn.start    exit Failure: (same)
    

    McpSignIn.resolve (apps/server/src/mcpApps/McpSignIn.ts) needs a live provider session and fails when providerSessionId is null or ProviderSessionManagerV2.get finds no runtime. ProviderSessionManager unloads idle sessions after DEFAULT_IDLE_TIMEOUT_MS (30 min). But the persisted system_notice keeps mcpSignIn: { server }, and McpSignInAction renders the button without checking whether the session is still live. So on any thread idle for more than 30 minutes, which includes every thread waiting on a delegate, the button can only fail. "Send a message, then sign in again" also means sending a throwaway message to that thread and clicking before the new session unloads too.

    Repro:

    1. Enable a plugin that ships an OAuth MCP server and don't sign in to it.
    2. Send a message in a Claude thread. The notice appears.
    3. Leave the thread idle for more than 30 minutes.
    4. Click Sign in. The dialog fails with the message above.

    Possible fixes: start or reattach a session on demand for the sign-in, or hide or disable the button when the thread has no live session. For user-configured servers this still matters after #40085.

    Workaround: run claude, open /mcp and authenticate the server there. Claude Code stores the credential, and every later session uses it.

    Posted from T3 Code triage by Claude Code (Claude Opus 5.5, claude-opus-5-5).

  6. creativeincode commented on Nov 22, 2026

    @creativeincode

    Same issue here, caused by Claude's "Design" plugin. I wanted to keep the plugin enabled & only turn off the MCP servers I don't use, so I found a workaround.

    Screenshot 2026-11-22 at 3 21 26 AM

    Workaround until #40085 lands: deny the MCP servers by name in ~/.claude/settings.json (use the names from your own sign-in warnings):

    "deniedMcpServers": [
      { "serverName": "plugin:design:slack" },
      { "serverName": "plugin:design:figma" },
      { "serverName": "plugin:design:linear" },
      { "serverName": "plugin:design:atlassian" },
      { "serverName": "plugin:design:notion" },
      { "serverName": "plugin:design:intercom" }
    ]

    Claude Code then never loads those servers, so there's nothing for T3 Code to announce. The plugin stays enabled, and its skills still load. Confirmed on Claude Code 2.1.330: a new Claude thread on the latest Nightly shows no warnings! 🙌

    NOTE: Disabling the servers in Claude Code's /mcp panel doesn't fix this. That toggle is saved per project in ~/.claude.json (disabledMcpServers), so it only applies to the folder you ran it in. T3 threads in any other folder still show the warnings.

    Trade-off: the denylist also blocks those servers in the terminal and the Claude desktop app's Code mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions