{"version":"2.1.299","anchor":"mcp-task-stop-reports-mcp-task-stop-for-sep2663-tasks","canonical_anchor":"mcp-task-stop-reports-mcp-task-stop-for-sep2663-tasks","heading":"Stopping certain MCP tasks now also sends a stop report","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-task-stop-reports-mcp-task-stop-for-sep2663-tasks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Stopping certain MCP tasks now also sends a stop report\n\nStopping an MCP task that uses the sep2663 protocol now also reports the stop, besides deleting the task's records\n\n**Unclear.** What the stop report does, and whether it reaches the MCP server, is not known.\n\n**What**\n\nAn MCP task is a longer-running job handled by an MCP server, an outside program that gives Claude Code extra tools. When you stop such a task and it uses the sep2663 protocol, Claude Code now also reports the stop. Before, it only deleted the task's stored details.\n\n**Why**\n\nThis changes what happens when you stop one of these tasks.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}