mcp-testbed
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 |
|---|---|
| create_workspaceA | Creates an isolated temporary directory and returns its id. Optionally seeds it with files. Every other tool addresses a workspace by this id; paths are always relative to it. Call destroy_workspace when finished. |
| write_filesA | Writes or overwrites files in an existing workspace, creating parent directories as needed. Paths must be relative and stay inside the workspace. Either every file is written or none is. |
| run_testsA | Runs a command in a workspace under a fixed environment and a wall clock timeout, then parses the output into a pass/fail summary with failing test names. Output is normalized (paths, durations, timestamps and colour codes removed) so two identical runs produce identical text. Returns the verdict plus both normalized and raw output. |
| read_workspaceA | Lists the files in a workspace, or returns the contents of one file when path is given. node_modules and .git are excluded from listings. Listings are sorted, so repeated calls match. |
| destroy_workspaceA | Deletes a workspace and everything in it. Safe to call on an id that no longer exists. |
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 has a clearly distinct role: create workspace, read/list files, write files, run tests, and destroy workspace. There is no overlap in purpose, so an agent can easily select the right tool.
All tool names follow a consistent verb_noun pattern (create_workspace, read_workspace, write_files, run_tests, destroy_workspace), using snake_case throughout. The naming is predictable and intuitive.
Five tools is appropriate for the scope of managing isolated test workspaces and running tests. Each tool serves a necessary function without redundancy or bloat.
The set covers the full lifecycle of a test workspace: creation, reading, writing, test execution, and destruction. No essential operations are missing; write_files handles overwrites, and read_workspace supports both listing and file content retrieval.