{"version":"2.1.319","anchor":"slack-channel-suggestion-now-connects-mcp-clients-first","canonical_anchor":"slack-channel-suggestion-now-connects-mcp-clients-first","heading":"The Slack channel suggestion now uses your connected MCP servers","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/slack-channel-suggestion-now-connects-mcp-clients-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The Slack channel suggestion now uses your connected MCP servers\n\nPicking the Slack channel suggestion now passes your connected MCP servers along before it runs\n\n**Unclear.** What picking the Slack channel suggestion now does differently for a user is not clear.\n\n**What**\n\nMCP, the Model Context Protocol, is a way to connect Claude Code to outside tools such as Slack. When you pick the \"slack-channel\" suggestion, Claude Code now first runs a step that takes your currently connected MCP servers, then does what the suggestion did before. Before, it ran a different step that did not take them.\n\n**Why**\n\nThis likely makes the Slack channel suggestion work with the MCP servers you have connected.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}