{"version":"2.1.301","anchor":"background-shell-commands-exposed-over-mcp-serve-with-lists","canonical_anchor":"background-shell-commands-exposed-over-mcp-serve-with-lists","heading":"mcp serve can track and stop background shell commands","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-shell-commands-exposed-over-mcp-serve-with-lists","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### `mcp serve` can track and stop background shell commands\n\nWhen Claude Code runs as an MCP server, the connected app can now see and stop shell commands left running in the background\n\n**Unclear.** It is not clear what decides whether `mcp serve` announces this capability.\n\n**What**\n\n`mcp serve` runs Claude Code as an MCP server, so another app (the host) can use its tools. MCP stands for Model Context Protocol. Claude Code now keeps a list of shell commands it has left running in the background, and the host can manage them:\n\n- A `StopBackgroundCommand` tool stops a background command, and another tool reads them.\n\n- The server announces the `anthropic\/backgroundCommands` capability, so the host knows this is supported.\n\n- Background commands have a time limit.\n\nIf a command is moved to the background after it has already finished, Claude Code reports an error saying its output was not kept.\n\n**Why**\n\nAn app that connects to Claude Code through `mcp serve` can follow and stop shell commands Claude Code started, instead of losing track of them.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}