Schema | MCP DevOps Test Server

MCP DevOps Test Server

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

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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