{"version":"2.1.296","anchor":"mcp-message-tool-respects-closed-project-mcp-servers","canonical_anchor":"mcp-message-tool-respects-closed-project-mcp-servers","heading":"Clear error when messaging a project MCP server that has been closed","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-message-tool-respects-closed-project-mcp-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Clear error when messaging a project MCP server that has been closed\n\nSending a message to a project's MCP servers after they are closed now fails with \"The repo's MCP servers have been closed\"\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Some are set up for a whole project. The tool for sending messages to MCP servers now looks them up separately for each scope. If the project's servers have been closed, it fails with the message \"The repo's MCP servers have been closed\".\n\n**Why**\n\nA failure after the project's servers have shut down now says plainly what happened.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}