vsc-mcp - VSCode MCP Server

Created By
0xh3xa year ago
MCP server for interacting with VSCode and forks (Cursor, Windsurf and others)
Overview

what is vsc-mcp?

vsc-mcp is a server designed for interacting with Visual Studio Code (VSCode) and its forks, such as Cursor and Windsurf, enabling enhanced functionality and integration.

how to use vsc-mcp?

To use vsc-mcp, install the extension from the VSCode marketplace. The server will start automatically when VSCode launches, and you can manually start or stop the server using the commands: Start MCP Server and Stop MCP Server.

key features of vsc-mcp?

  • File Management: Retrieve a list of currently opened files and close files based on provided labels.
  • Theme Management: List available VSCode themes, get the current theme, and change the theme by display name.

use cases of vsc-mcp?

  1. Managing files efficiently within VSCode.
  2. Customizing the development environment with different themes.
  3. Integrating with other tools and extensions that require MCP server functionality.

FAQ from vsc-mcp?

  • How do I install vsc-mcp?

Install the extension from the VSCode marketplace to get started.

  • Can I manually control the MCP server?

Yes! You can start and stop the server using the provided commands in VSCode.

  • What tools are currently supported?

Currently, vsc-mcp supports file and theme management.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
0xh3x
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago