aiTest MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AITEST_API_KEY | Yes | Your aiTest API key (aitest_sk_...) | |
| AITEST_API_URL | No | aiTest REST API base URL | http://localhost:8000/api/v1 |
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 |
|---|---|
| aitest_runA | Submit a browser test job to aiTest. Provide a URL and a natural-language description of what to test. The AI engine will plan, execute, and analyze the test, then return a report. Example: 'Test that the login form accepts valid credentials and shows the dashboard.' |
| aitest_statusA | Check the status of a previously submitted test job. Returns the current status (created, queued, executing, completed, failed) and timing info. |
| aitest_reportA | Get the complete test report for a finished job. Includes step-by-step results, pass/fail summary, root-cause analysis of failures, and UX improvement insights. |
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: run submits tests, status checks progress, report retrieves results. No overlap or ambiguity.
All tools follow the consistent pattern 'aitest_<verb>', with clear imperative verbs (run, status, report).
Three tools cover the essential workflow (submit, monitor, retrieve results) with no redundancy. Slightly minimal but appropriate for the focused scope.
Covers the full lifecycle of testing: submission, status polling, and report retrieval. Missing operations like cancellation or listing are minor gaps.