deploytest MCP server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_fixturesA | List all available test fixtures |
| run_fixtureB | Run a specific test fixture against a deployment URL |
| run_all_fixturesB | Run all test fixtures (or filtered by tags) against a deployment URL |
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 3 tools
Each tool has a distinct purpose: listing fixtures, running a single fixture, and running all fixtures. No overlap or ambiguity exists.
All tool names follow a consistent verb_noun pattern with snake_case: list_fixtures, run_fixture, run_all_fixtures. The naming is predictable and uniform.
With only 3 tools, the server is tightly scoped to its purpose of running test fixtures. Each tool is essential and there is no bloat.
The tool set covers the full lifecycle for this domain: discovering fixtures, executing a specific fixture, and executing all fixtures. No critical operations are missing for a deployment test runner.