vscode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileB | Read the contents of a file. Optionally specify a line range. |
| write_fileA | Write or overwrite a file with new content. Creates parent directories automatically. |
| edit_fileC | Replace an exact string in a file. The old_string must appear exactly once. |
| list_directoryB | List files and directories at a given path. |
| create_directoryA | Create a directory (and all parent directories). |
| delete_pathB | Delete a file or directory. |
| move_pathB | Move or rename a file or directory. |
| search_filesB | Search for a regex pattern inside files. Returns matching lines with file and line number. |
| find_filesB | Find files by name glob pattern (e.g. '.ts', 'index.'). |
| run_commandA | Execute a shell command in the given working directory. Returns stdout, stderr, and exit code. |
| get_workspace_infoA | Get information about the current workspace: root directory, platform, Node version, git status summary. |
| get_file_infoB | Get metadata about a file or directory (size, modification time, type). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct file or workspace operation: create, delete, edit, find, get info, list, move, read, run, search, write. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_directory, read_file, write_file). No deviations or mixed conventions.
12 tools is well-scoped for a file system and workspace utility server, covering essential operations without being overwhelming or too sparse.
The tool set covers fundamental file/directory operations and workspace info. Minor gaps exist such as no copy tool (can be done via read+write) and no line-based editing, but core workflows are supported.