{"version":"2.1.296","anchor":"monitormcptask-kill-stops-streamed-monitors","canonical_anchor":"monitormcptask-kill-stops-streamed-monitors","heading":"Background monitors from MCP servers can be stopped as tasks","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/monitormcptask-kill-stops-streamed-monitors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Background monitors from MCP servers can be stopped as tasks\n\nA new task type for MCP monitors can be stopped, which also stops the monitor streaming updates for it\n\n**Unclear.** Whether this kind of task can be started at all yet, and what switches it on, is not known.\n\n**What**\n\nClaude Code has a new kind of task, `monitor_mcp`, for monitors that come from MCP servers. MCP, the Model Context Protocol, is the standard way Claude Code connects to outside tools and services. A monitor is something that keeps sending updates while it runs.\n\nWhen one of these tasks is stopped, Claude Code also stops the monitor that was streaming updates for it and removes the task from its list.\n\n**Why**\n\nThis suggests that monitors streamed from MCP servers can be ended the same way as other running tasks.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}