$ loading_
Use VS Code language services for cross-language code analysis and editing.
This is an open-source MIT project with no declared secrets or remote endpoints, and the provided materials show no clear high-risk red flags. However, its stated purpose—programmatic code analysis and editing via VS Code/LSP—implies local code-execution and file-access capabilities that warrant caution.
The materials explicitly state that no keys or environment variables are required; no API keys, OAuth tokens, or other sensitive credentials are requested, so credential exposure risk appears low.
No remote host endpoints are declared, and the description does not state any need to connect to external services; based on the provided information, there is no clear data-egress path.
The objective checks confirm executes-code. Combined with its purpose of exposing VS Code/LSP features as MCP tools for programmatic code analysis and editing, it likely starts local processes and invokes editor/language-service capabilities; this is a typical but privileged local capability and should be scoped carefully.
By design, it analyzes and edits code, so it is expected to read and write workspace source files. The provided materials do not show requests for broader system-level or unrelated data access, but repository file access itself should still be treated with caution.
Positive evidence includes a reviewable open-source repository and an MIT license. Caution is still warranted because the source is a third-party registry, community adoption is 0 stars, and maintenance status is unknown; trust is limited, but no concrete red flags justify a high-risk rating from the provided materials alone.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "vsc-mcp" yet — see the docs or source repo.
Use vsc-mcp to scan this TypeScript project for type errors, list the affected files and causes, and provide directly applicable fixes or edits.
A result listing error locations, explanations, and suggested code edits to quickly resolve type issues.
Use vsc-mcp to refactor the old interface name UserDTO to UserProfile across the repository, updating all references, imports, and related type definitions.
A list of affected files and updated code changes, ensuring the rename is applied consistently across the project.
Use vsc-mcp to find the definition, all call sites, and related implementation files for processOrder, then summarize its inputs, outputs, and potential risks.
A summary with the function definition, reference map, related files, and concise analysis to understand the code structure.
Connect VSCode to MCP so AI can inspect code context in real time.
Expose read-only code intelligence like hover, definitions, references, and diagnostics.
Access semantic code tools like definitions, references, rename, and diagnostics.
Control Visual Studio 2022 via MCP for file, build, and debugging tasks.
Safely run Python code with AI and MCP tool integration.
Lets AI inspect and modify code symbols through Neovim LSP.