$ loading_
Gives AI assistants VSCode context and file operations for development workflows.
This MCP tool claims to provide VSCode context and filesystem operations, and system checks indicate local code execution capability. No credentials or remote endpoints are declared, so there is no clear exfiltration red flag from the materials, but caution is still warranted due to code execution and filesystem access. It is open source and partially auditable, yet trust is limited by third-party registry distribution, no declared license, low adoption, and unknown maintenance status.
The materials explicitly state that no keys or environment variables are required, and no API tokens, account credentials, or other sensitive authentication secrets are mentioned; based on the provided facts, credential exposure or abuse risk appears low.
No remote endpoints are declared, and the README does not describe any external service connections; based on the available description, there is no factual indication of user data being sent to third-party services.
The system has flagged executes-code capability; as an MCP tool, this implies it may start local processes or execute code on the host. This is consistent with its stated role of providing VSCode context and filesystem operations, but it remains an inherently sensitive capability that warrants constrained use.
The description explicitly mentions filesystem operations, indicating access to the local filesystem and potentially to VSCode workspace-related data. The materials do not define precise read/write scope or permission boundaries, so it should be treated cautiously as a local data access tool.
A positive factor is that a public open-source repository exists, making the code in principle auditable. However, it comes via a third-party registry, has no declared license, shows 0 stars, has unknown maintenance status, and provides very limited documentation. These factors reduce source trust, though they do not by themselves constitute a high-risk red flag.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "VSCode Context MCP" yet — see the docs or source repo.
Read my current VSCode workspace structure and key source files, then summarize the tech stack, module layout, and main entry points.
A project overview with core file explanations and a summary of the code organization.
Inspect all API-related files in the workspace, replace the old error-handling logic with a new implementation that includes logging, and list the changes made.
A list of modified files, the exact changes applied, and an explanation of the standardized implementation.
Using the error message I provide and the current VSCode project context, find the root cause, propose a fix, and directly update the relevant files.
The root cause analysis, the applied code fix, and brief validation suggestions.
Gives AI file access and project context for full-stack development help.
Connect VSCode to MCP so AI can inspect code context in real time.
Provide coding standards context so AI-generated code follows team conventions.
Give LLMs persistent, searchable access to project knowledge and session context.
Let AI assistants use OpenCode CLI and multiple models through one interface.
Lets AI inspect and modify code symbols through Neovim LSP.