{"version":"2.1.323","anchor":"plugin-mcp-connect-tool-and-git-helpers-change","canonical_anchor":"plugin-mcp-connect-tool-and-git-helpers-change","heading":"Plugin helpers for connecting tools and running git behave differently","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-mcp-connect-tool-and-git-helpers-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin helpers for connecting tools and running git behave differently\n\nPlugins can connect listed tool servers and choose a provider, tool listing errors no longer stop things, and plugin git runs with a filtered environment\n\n**What**\n\nPlugins add features to Claude Code. Several of the helpers they use have changed. Some of these helpers deal with MCP servers. MCP, the Model Context Protocol, is a standard way of connecting Claude Code to outside tools.\n\n- Connecting to an MCP server: the helper now accepts a provider, and it can connect a server that is listed but not yet connected.\n\n- Listing tools and calling an MCP tool: these helpers now wait for a particular event before they run.\n\n- Tool listing errors: if a tool causes an error while tools are being listed, Claude Code logs that the tool has no description and carries on.\n\n- Git commands run by plugins: these now run with a filtered set of environment variables, so a plugin's git does not get everything in your environment.\n\n**Why**\n\nOne bad tool no longer stops a tool listing. Plugins can bring up servers that were listed but not connected. Git commands started by plugins now see less of your environment.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}