MCP DevOps Test Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEST_SERVER_URL | Yes | URL to your Test server instance | |
| TEST_ACCESS_TOKEN | Yes | Base64 encoded personal access token for authentication | |
| TEST_INSECURE_TLS | No | Disable TLS certificate validation for self-signed or untrusted server certificates | false |
| TEST_TEAMSPACE_ID | Yes | Your Test teamspace identifier |
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 |
|---|---|
| get_projectsA | Retrieves all projects from the Test system |
| list_testsB | Retrieves tests from a specific project with optional test type filtering |
| execute_testA | Execute a test in a specific project by test name. TIMING: Tests typically take 60-180 seconds to complete. AGENT BEHAVIOR: After execution, inform user 'Test started, will complete in ~2 minutes', then wait at least 60 seconds before first status check. Use progressive back-off for subsequent checks: 30s → 45s → 60s → 90s intervals until completion. |
| get_test_resultsA | Get comprehensive test execution results and report data. PROGRESSIVE POLLING: If status is RUNNING, wait using progressive back-off: 30s → 45s → 60s → 90s between checks. Tests typically complete in 60-180 seconds. |
| prepare_test_downloadC | Prepare test result download and extract download ID from location header |
| get_test_log_resultsC | Download and analyze test log results from the zip archive |
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 6 tools
Most tools have clearly distinct purposes: projects, tests, execution, results, logs, and download preparation. The only potential confusion is between get_test_results and get_test_log_results, but their descriptions differentiate comprehensive report data from log archive analysis.
Tool names follow a consistent verb_noun pattern (get_, list_, execute_, prepare_) and all use snake_case. Minor inconsistency exists between get_ and list_ for retrieval operations, but this is a common and acceptable variation.
With 6 tools, the server is well-scoped for a DevOps test management workflow: project discovery, test listing, execution, result retrieval, log retrieval, and download preparation. Each tool serves a distinct step without unnecessary redundancy.
The tool set covers the core lifecycle of test execution: discover projects, list tests, execute tests, retrieve results, and download logs. Minor gaps exist (e.g., no explicit test detail view, no cancellation mechanism), but agents can accomplish primary workflows without dead ends.