Under the hood
The bridge's context-usage handler forwards a detail argument, so remote clients can ask for coarser reporting.
The bridge's onGetContextUsage handler now accepts an optional detail argument and forwards it through to context usage collection, allowing more granular usage reporting requests from a remote client.
Names in the bundledetail
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Create and distribute a plugin marketplace touched a line naming detail after this was published.
From the directory that contains `my-marketplace`, start Claude Code and run the following commands. The install command opens a plugin details view where you select an installation scope to confirm the install. Check the install summary: …plugin-marketplaces see the edit
Confirmed since
Anthropic's documentation has since written up detail, on Third party connectors with remote MCP.
* **Use Claude's published identity** (recommended): the server reads Claude's client details from a URL Anthropic hosts (Client ID Metadata Document). Nothing to set up; the server must support it.connectors/custom/remote-mcp see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up detail, on Third party connectors with remote MCP.