{"version":"2.1.268","anchor":"claude-code-remote-auto-trusts-built-in-slackteams-bot-mcp","canonical_anchor":"claude-code-remote-auto-trusts-built-in-slackteams-bot-mcp","heading":"Built-in Slack\/Teams bot MCP servers bypass normal allowlist checks under CLAUDE_CODE_REMOTE","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/claude-code-remote-auto-trusts-built-in-slackteams-bot-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Built-in Slack\/Teams bot MCP servers bypass normal allowlist checks under CLAUDE_CODE_REMOTE\n\nUnder CLAUDE_CODE_REMOTE, built-in Slack\/Teams bot MCP servers are marked CCR-injected and skip the usual allowlist and type restrictions\n\n**What**\n\nWhen 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.\n\n- These CCR-injected configs bypass the user's `allowedMcpServers` allowlist check entirely, instead of being blocked like other unlisted servers.\n\n- 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.\n\n**Why**\n\nThis 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.\n\n- Area: MCP\n- Names: `CLAUDE_CODE_REMOTE`, `allowedMcpServers`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}