Workspace MCP
Designed for SAP ADT and other virtual filesystems, providing access to workspace files through VS Code's FileSystemProvider with tools for listing directories, reading and editing live documents, saving, searching, and fetching diagnostics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Workspace MCPList the workspace roots and show me the active editor's content."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Workspace MCP
Connect MCP clients such as Codex and Claude Code to the workspace open in VS Code, including virtual filesystems such as SAP ADT. Read live editor content, inspect symbols and diagnostics, and apply edits without saving automatically.
Unlike a local filesystem server, this extension uses VS Code's workspace APIs and preserves full URIs. Unsaved editor changes are included in reads.
MIT licensed. No telemetry or shell tools. Initial preview: compatibility with a real SAP backend still requires acceptance testing. Independent project, not affiliated with SAP or OpenAI.
Install and connect
Requires VS Code 1.137+ and Node.js 24+ on the MCP client host. The client must be able to run the bundled adapter in the same network environment as the VS Code extension host; hosted web sessions cannot connect directly.
Open a successful CI run on main, download the
workspace-mcp-vsixartifact and extract the ZIP. GitHub sign-in is required. Alternatively, build the VSIX.In the VS Code Command Palette, run Extensions: Install from VSIX and select
workspace-mcp.vsix.Open and trust your workspace. Turn Files: Auto Save off before allowing agent edits; the bridge refuses edits when Auto Save is enabled.
Run Workspace MCP: Start. By default, it asks for write permission; dismissing the prompt keeps the bridge read-only. Editing and saving are separate operations.
Run Workspace MCP: Show Connection Details, select your client and copy the generated stdio configuration into its private user settings. It contains a secret token: never commit or share it. Restart the client connection.
Ask the agent to list workspace roots and read the active document.
Use Workspace MCP: Stop to disconnect. See client setup for client-specific instructions, write policies, ports and remote-host limitations. There is no Marketplace release; CI artifacts expire after 14 days. A manual preview release workflow can prepare versioned VSIX drafts after acceptance and Security gates; it does not publish to the Marketplace.
Related MCP server: lsp-mcp
Build from source
Requires Git and Node.js 24 LTS with npm (use the latest 24.x patch).
git clone https://github.com/hendrik-101/vscode-workspace-mcp.git
cd vscode-workspace-mcp
npm ci
npm run packageInstall the resulting artifacts/workspace-mcp.vsix using the steps above.
Tools
Tool | Behavior |
| Full workspace-folder URIs |
| Scoped active editor, selection and open text tabs |
| Entries through |
| Live text, version and dirty state; optional line range |
| Version-checked symbol bodies with bounded continuation |
| Bounded literal search with filters and continuation cursors |
| Version-checked text edits; leaves the buffer unsaved |
| Separate version-checked save; may trigger provider dialogs |
| Diagnostics already available in VS Code |
| Reveal a document and optional selection; preserve focus by default |
| Query installed workspace symbol providers; only admitted targets |
| Bounded document structure through installed language providers |
| Compare two workspace documents or a versioned proposed text snapshot |
| Preview provider formatting edits; optionally apply without saving |
| Wait for a diagnostic event or timeout; no analysis-completion guarantee |
| Query installed language providers |
| Preview provider text edits; no automatic application |
Positions are zero-based UTF-16; ranges are end-exclusive. Full URIs are required. No file creation/deletion/renaming, arbitrary commands, activation or terminal tools. Search reports truncation/errors: it is not an exhaustive SAP repository index.
See the tool reference for parameters and limits.
Further documentation
Related MCP Connectors
Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.
Lean 4 MCP server: compile, prove theorems, and formalize math with Mathlib.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Browse and manage files in your Moxt AI workspace from any MCP client.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceExposes VSCode's Language Server Protocol features through MCP, enabling AI assistants to perform language-aware operations like symbol navigation, reference tracking, safe renaming, type information retrieval, and hover documentation across codebases.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with VS Code's language server protocol features (definitions, references, diagnostics) and debugger (breakpoints, stepping, variable inspection) via an MCP server.6 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access live VS Code editor state, symbol navigation, diagnostics, and language-aware editing through MCP, bridging the gap between what the agent can infer from disk and what the editor actually knows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with a real Windows workspace by providing tools for file operations, code search, Git, command execution, and managing long-running development processes, all under the current user's context.1MIT