MCP GETS REAL: VS CODE BRIDGES AGENTS, COPILOT CLI HARDENS TERMINALS, AND SKILLS HELP VET SERVERS
VS Code 1.113 and Copilot CLI 1.0.12 make MCP servers first‑class across IDE and CLI agents, tightening reliability and simplifying agent workflows. Microsoft’...
VS Code 1.113 and Copilot CLI 1.0.12 make MCP servers first‑class across IDE and CLI agents, tightening reliability and simplifying agent workflows.
Microsoft’s latest VS Code (1.113) adds a chat customizations editor and bridges MCP servers registered in the editor to both Copilot CLI and Claude agents, plus fixes Claude session listing by using the official SDK API. It also enables subagents to call subagents and surfaces a Thinking Effort control in the model picker InfoWorld.
Copilot CLI 1.0.12 focuses on stability: MCP servers from .mcp.json start correctly at the git root, persist across /clear, and are visible to the agent. It fixes Windows clipboard/PowerShell flag quirks, avoids OOM on high‑volume output, stabilizes sessions, and shows the active reasoning effort level; it also reads .claude/settings.json for repo config (release, releases page).
The antigravity-awesome-skills 8.10.0 update adds clarvia-aeo-check to score MCP servers/APIs/CLIs for agent-readiness and ships a new social-reading skill, expanding a 1,328+ skill catalog for Claude/Cursor/Codex/Windsurf/Cline users release. A recent walkthrough shows AI stitching Google Drive, GitHub, and BigQuery into an end-to-end DS workflow using agents and MCP article.
MCP servers now span VS Code, Copilot CLI, and Claude, reducing duplicate setup and config drift between developer tools.
Copilot CLI reliability fixes make agent workflows safer in real terminals and CI, especially on Windows.
-
terminal
Register an MCP server in VS Code and confirm it appears and works in Copilot CLI and Claude sessions (workspace mcp.json vs user-defined).
-
terminal
Stream a noisy long-running command via Copilot CLI to verify no OOM, stable scroll, clickable OSC 8 links, and correct PowerShell flag handling on Windows.
Legacy codebase integration strategies...
- 01.
Standardize existing plugins/integrations as MCP servers and centralize per-tool configs into mcp.json; audit Windows PATH (clip.exe) and OneDrive trust prompts.
- 02.
Update team docs for session naming, alt-screen always on, and MCP persistence across /clear to avoid surprises in shared environments.
Fresh architecture paradigms...
- 01.
Design new agent workflows around a single MCP registry and use clarvia-aeo-check to vet internal APIs/CLIs before exposing them to agents.
- 02.
Use VS Code’s chat customizations editor to version prompt files, custom agents, and skills in-repo for reproducible setups.