Autotest AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTOTEST_AI_URL | Yes | The URL of the Autotest AI server (e.g., http://localhost:3000) | |
| AUTOTEST_AI_API_KEY | Yes | Your Autotest AI API key |
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_projectsA | List all projects configured in the test automation system. |
| list_screensB | List all screens under a specific project by project ID. |
| list_test_casesB | List test cases. Can filter by screen ID. |
| get_test_case_detailsA | Get all steps and detailed definitions of a specific test case. |
| get_latest_test_runsA | Get recent test execution runs and their status. |
| run_test_caseB | Trigger the execution queue for a specific test case ID. |
| create_projectB | Create a new project. |
| create_screenB | Create a new screen under a specific project. |
| create_test_caseB | Create a new test case under a screen. |
| create_test_stepB | Add a step to a test case. |
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 10 tools
Each tool targets a distinct entity (project, screen, test case, test step, test runs) with clear actions (create, list, get, run). No ambiguity among tool purposes.
All tools consistently use verb_noun pattern in snake_case (e.g., create_project, list_screens), with verbs like create, list, get, run and nouns matching domain entities.
10 tools is well-scoped for a test automation system, covering project setup, test case management, and execution without excess or deficiency.
Missing update and delete operations for all entities (project, screen, test case, test step) and no tool for individual test run details or cancellation, creating significant gaps for agent workflows.