mcp-agent-to-vsc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | No | The OpenAI model to use (e.g., gpt-5.6). | |
| OPENAI_API_KEY | Yes | Your OpenAI API key. | |
| WORKSPACE_ROOT | No | The root directory for workspace file access. |
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 |
|---|---|
| ask_aiC | Send a prompt to OpenAI and return the answer. |
| read_fileA | Read a file inside the VS Code workspace. |
| write_fileC | Write a file inside the VS Code workspace. |
| list_filesB | List files and directories in the workspace. |
| workspace_infoA | Show MCP workspace and model configuration. |
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 5 tools
Each tool targets a distinct function: AI query, file read, file write, file listing, and workspace configuration. There is no functional overlap, so an agent can reliably select the correct tool.
Most names follow a verb_noun pattern (ask_ai, read_file, write_file, list_files), but workspace_info breaks the pattern as a noun phrase. Overall the naming is clear and predictable.
Five tools is a well-scoped set for an agent-to-VS Code integration covering the essential file operations, AI interaction, and workspace context. Each tool earns its place without redundancy.
The set covers core file read/write/list and AI query, which covers common agent workflows. Minor gaps include delete or rename file operations, but these are not critical for the apparent purpose.