"VSCO" matching MCP servers:

MCP server to expose VS Code editing features to an LLM for AI coding

Enables AI agents to control VSCode workspaces, including file operations, terminal commands, search, and workspace management.

An MCP server that exposes Language Server Protocol features to external clients, allowing access to hover information, definitions, completions, references, and rename functionalities.

Exposes the Jupyter notebooks open in VS Code to MCP-compatible AI agents, letting them edit cells in the open editor and execute them in the live kernel without file conflicts. Agents can make partial edits, track stale cells, inspect variables, and manage kernels while preserving the user's interpreter choices and unsaved work.

Exposes Jupyter notebook operations as MCP tools over plain HTTP, allowing AI agents to explore, edit, run, and debug notebooks in a live VS Code session using local or remote kernels.

A lightweight bridge extension that enables Claude Desktop to connect to VSCode workspaces via Model Context Protocol, allowing Claude to read and write files, create directories, and list contents in your workspace.

Gives AI agents full control of VS Code's debugging engine — set breakpoints, launch/attach sessions, step through code, inspect call stacks and variables, and evaluate expressions in the paused frame.

Exposes VSCode Jupyter notebooks to MCP-compatible AI agents, enabling them to read, edit, and run cells against the same kernel.

An MCP server and VS Code extension that enables AI clients to interactively debug code using breakpoints, execution control, and state inspection. It is language-agnostic and works with any debugger that supports VS Code's launch.json configurations.

A server that likely facilitates integration between GitHub Copilot and Visual Studio Code, though the README lacks specific details about its functionality.