{"version":"2.1.314","anchor":"mcp-serve-notifies-tool-list-changes-when-repo-hooks-setting","canonical_anchor":"mcp-serve-notifies-tool-list-changes-when-repo-hooks-setting","heading":"claude mcp serve tells connected apps when repository hook settings change","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-serve-notifies-tool-list-changes-when-repo-hooks-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### `claude mcp serve` tells connected apps when repository hook settings change\n\n`claude mcp serve` now sends a tool-list-changed notice when the repository's settings files change, so connected apps can update\n\n**What**\n\n`claude mcp serve` runs Claude Code as an MCP server, so another program (the host) can use Claude Code's tools. MCP is the protocol Claude Code uses to talk to outside tools and programs.\n\nIt now watches the repository's settings files, which include the hooks configured for that repository. A hook is a command Claude Code runs automatically at certain moments. Each response now carries a `claudecode\/repoHooksStamp` value worked out from those files. When the files change, the server sends a notice that its list of tools has changed.\n\n**Why**\n\nA program that uses `claude mcp serve` can now pick up changes to a repository's hooks while it is running, without a restart.\n\n- Area: MCP\n- Names: `claude mcp serve`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}