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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrchris2000/mcp-devops-test'
If you have feedback or need assistance with the MCP directory API, please join our Discord server