vscode-editor-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_selectionA | Returns the name and path of the file open in VS Code's active editor along with the line range(s) of the current selection(s). Line and character numbers are 1-based. |
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 1 tool
With only one tool, there is no possibility of overlap or confusion. get_selection has a clearly distinct purpose.
The single tool follows the clear verb_noun pattern (get_selection), and since there are no other tools, there are no inconsistencies.
A single tool is far too few for an editor MCP, which would normally require operations like opening files, editing text, or managing tabs. This feels severely under-scoped.
The tool surface is severely incomplete: it only reads the current selection and provides no way to modify files or interact with the editor in other ways, making most editor workflows impossible.