Skip to content

Claude chat shows system:init as an error card when an MCP server failed to connect #28856

Closed as duplicate

Description

@airematters

Operating system

macOS 15 (Darwin 24.6.0, arm64)

Orca version

1.4.224

Details

When any configured MCP server fails to connect, a Claude native chat session starts with a red claude · message:system:init error card, whose disclosure dumps the raw init frame (tool list, MCP servers, plugins, ...).

Cause: classifyProviderFrame runs hasProviderError over the whole payload before consulting the catalog. Claude's system:init lists every MCP server with its connect status, so one entry like { "name": "marimo", "status": "failed" } matches the status → fail* rule and promotes the catalogued status-chrome init frame to error-surface.

Repro: configure an MCP server that cannot connect (e.g. a URL nothing listens on), start a Claude chat, send any message.

Expected: no raw-frame card for init (it is session inventory, not an operation outcome), but a readable warning naming the MCP server(s) that failed to connect and how to find out why.

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