Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.268 ·

Built-in Slack/Teams bot MCP servers bypass normal allowlist checks under CLAUDE_CODE_REMOTE

Under CLAUDE_CODE_REMOTE, built-in Slack/Teams bot MCP servers are marked CCR-injected and skip the usual allowlist and type restrictions

Group of 2 You'll notice Improvements
JSON All of v2.1.268
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.268,
ImprovementsSection of the release

What

When Claude Code is running under CLAUDE_CODE_REMOTE (its remote/bridge mode), MCP server configs that match known built-in Claude-Code-Remote (CCR) endpoints for Slack and Teams bots (slackbot, slackbot_read, ccr-slack-thread, teamsbot) are now marked as CCR-injected.

  • These CCR-injected configs bypass the user's allowedMcpServers allowlist check entirely, instead of being blocked like other unlisted servers.
  • The server reconciliation logic that normally only lets type === 'sdk' MCP servers through in restricted or remote scenarios now also admits these non-sdk, CCR-injected servers (tracked in a ccrInjectedConfigs set), as long as Claude Code is not running as a bridge-carrier child process.

Why

This lets the built-in Slack and Teams bot integrations keep working over MCP in remote mode without requiring users to manually add them to their MCP server allowlist.

Read from
What the documentation says
Since it was published

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.

Confirmed since Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Customize sessions in self-hosted environments. | `CLAUDE_CODE_REMOTE_SESSION_ID` | Session ID in the tagged `cse_...` form. This is the same session the [lifecycle hooks](#lifecycle-hooks) see as `CLAUDE_RUNNER_SESSION_ID` in `session_...` form; the UUID variables match across both, an… self-hosted-environments-configuration see the edit
Added since A small documentation edit on Control MCP server access for your organization touched a line naming allowedMcpServers after this was published. * [Server-managed settings](/docs/en/server-managed-settings): deliver `allowedMcpServers` and `deniedMcpServers` from the claude.ai admin console managed-mcp see the edit
Added since A small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published. * **No cloud-only scoping**: hooks run in both local and cloud sessions. To skip local execution, exit early unless the `CLAUDE_CODE_REMOTE` environment variable is `true`, the way the [dependency install script](#install-dependencies-with… cloud-environments see the edit
Confirmed since Anthropic's documentation has since written up allowedMcpServers, on All settings. | Restriction allowlists | Takes the list whole from the highest source that sets it, without adding entries from lower sources. When the highest source doesn't set one, takes it whole from the next source down | [`availableModels`](#avail… settings-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up allowedMcpServers, on All settings.

See this entry in the whole of v2.1.268 →

Feedback