Copilot CLI v1.0.81-11 fixes MCP enterprise blocks: /mcp now shows 'blocked' instead of spinning. Update now for clearer status visibility in your agentic workflows.
Key Takeaways
- Copilot CLI v1.0.81-11 fixes MCP enterprise blocks: /mcp now shows 'blocked' instead of spinning.
- Update now for clearer status visibility in your agentic workflows.
What Changed
GitHub released copilot-cli v1.0.81-11 (pre-release, Aug 26, 2026) with a single but impactful fix: when an MCP server is blocked by an enterprise policy, the /mcp command now displays it as blocked instead of leaving it in a perpetual 'pending' state.
This might sound minor, but for developers running Copilot CLI in enterprise environments, it's a quality-of-life win that eliminates a confusing dead-end.
What It Means For You
If you work in an organization with strict MCP server policies (common in regulated industries like finance or healthcare), you've likely hit this scenario: you add an MCP server, run /mcp, and see it stuck on 'pending' — with no error, no timeout, just an endless spinner. You waste time debugging whether your config is wrong, if the server is down, or if there's a network issue.
Now, the CLI will tell you the truth: the server is blocked by policy. That means:
- No more guessing — you know immediately that the issue is policy, not your setup.
- Faster troubleshooting — you can skip the debugging loop and go straight to your admin or find an alternative server.
- Clearer team communication — when sharing MCP configs, you can quickly identify which servers won't work in your environment.
This also aligns with the broader MCP ecosystem trend: with 13,000+ MCP servers available (as we covered recently), enterprise governance is becoming a bottleneck. Tools that surface policy blocks transparently help you navigate that complexity.
Try It Now
- Update Copilot CLI to v1.0.81-11 (pre-release):
npm install -g @github/copilot@next
-
Run
/mcpin your Copilot CLI session. If you have any enterprise-blocked servers, they'll now show as 'blocked'. - Verify by checking a server that's allowed — it should still show as 'connected' or 'ready'.
If you're not seeing the fix, ensure your enterprise policy is actually blocking the server (not just a connection error). The 'blocked' status is specifically for policy-based blocks.
Why This Matters for Your Workflow
This fix is part of GitHub's ongoing investment in MCP support. Copilot CLI has been adopting MCP rapidly, and with Claude Code also pushing MCP hard, the two tools are converging on similar workflows. Knowing exactly what's blocked vs. broken saves you from the worst kind of debugging: staring at a spinner.
For Claude Code users who also use Copilot CLI (a common combo), this means you can trust /mcp status output more, making it easier to maintain consistent MCP setups across both tools.
Bottom Line
Update to v1.0.81-11, and the next time an MCP server is blocked by policy, you'll see it in black and white. No more infinite pending.
Source: github.com
[Updated 27 Aug via github_copilot_cli_releases]
A follow-up release, copilot-cli v1.0.81-12, adds Windows-only support for Microsoft Entra ID–protected remote MCP servers via the OS authentication broker (WAM), typically with no prompt. Other platforms and --device-code keep the browser flow. The release also fixes a crash when repeatedly resuming the same session during telemetry replacement. [per GitHub]
Originally published on gentic.news
Top comments (0)