workbench-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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_infoA | Return sanitized workspace and server capability information. |
| list_filesC | List files in a workspace-contained directory. |
| read_fileC | Read a workspace-contained UTF-8 text file. |
| search_text | Search workspace text files with bounded results. |
| apply_patch | Apply one expected-content guarded replacement. |
| run_command | Run one allowlisted command using argument-array execution. |
| run_tests | Run a named predefined test command. |
| git_status | Return read-only Git status for the configured workspace. |
| collect_artifact | Collect an approved artifact from the artifact root. |
| diagnose_workspace | Return structured diagnostic findings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_info | Return safe server metadata for MCP clients. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing files, reading a file, and returning workspace information. No ambiguity or overlap.
All tools follow a consistent verb_noun snake_case pattern (list_files, read_file, workspace_info), making them predictable and easy to understand.
Three tools is minimal but reasonable for a focused workspace file server. The count feels slightly low but not problematic given the apparent scope.
The set covers listing and reading files but lacks write, delete, or directory operations, leaving significant gaps for typical file management workflows.