{"version":"2.1.321","anchor":"mcp-resource-listing-commits-after-the-result","canonical_anchor":"mcp-resource-listing-commits-after-the-result","heading":"MCP resource tools can now run a follow-up step after their result is saved","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-resource-listing-commits-after-the-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP resource tools can now run a follow-up step after their result is saved\n\nListing, browsing and reading MCP resources can now trigger a follow-up action once the result is saved, when there is anything to return\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools and resources. Resources are files or data a server makes available. The tools that list resources, read a resource folder and read a resource now come back with a follow-up action as well as their data. That action runs once the result has been saved into the conversation, and it is only attached when there are resources or contents to return.\n\n**Why**\n\nThis is groundwork that lets Claude Code do something after an MCP resource result lands. It does not change what the tools return.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}