Aio Tests MCP Server
Jira test cases within AIO Tests via read-only or read-write MCP integration.
Data last scanned today · Reviewed today
Overview
AIO Tests MCP Server is a self-hosted tool designed to integrate AIO Tests management features directly into AI workflows. It enables users to browse test case hierarchies, inspect field schemas, and filter test cases by status, owner, or folder, bringing Jira-based test management into the conversation space of your AI assistant. The server supports both Jira Cloud and Jira Server/Data Center environments. It provides ten distinct tools that allow for reading test data and, optionally, performing write operations to create or update test cases and folders.
Our verdict
This server carries a high risk level (33/100) and is not recommended for environments requiring high-assurance software. Because it is community-maintained rather than official vendor software, and has not yet been editorially reviewed, users must exercise caution. While it includes a read-only mode, the lack of an authenticated security review means that users should manually audit the code before granting it write access to production Jira instances.
- Supports both Jira Cloud and Jira Server/Data Center
- Zero direct dependencies reduce supply-chain surface area
- Includes a read-only mode for safer AI interaction
- Open-source Python implementation available under MIT license
- Community-maintained with no official vendor backing
- Not yet editorially reviewed for security patterns
- Low bus factor with only one contributor recorded
- Authentication methods have not undergone security review
Tools
| Tool | Description | Risk |
|---|---|---|
| aio_get_project | Confirm AIO Tests is enabled for a project and get its ID | low |
| aio_get_test_case_schema | Fields, custom fields, required fields and allowed values | low |
| aio_search_test_cases | Filter by title, key, folder, status, priority, type, tag, owner, covered Jira issue, automation status/key, and creation/update dates | low |
| aio_get_test_case | Full case detail including every step | low |
| aio_get_test_case_versions | Every saved version of a case | low |
| aio_create_test_case | Create a case with Classic or BDD steps | medium |
| aio_update_test_case | Update fields, steps, metadata, priority, status or tags | medium |
| aio_get_folder_hierarchy | Folder tree (or a flat list of full paths) for test cases, cycles or sets | low |
| aio_create_folder | Create a folder, creating missing parents along a path | medium |
| aio_get_tags | Every tag configured for a project | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Which Jira environments does this MCP server support?
It supports both Jira Cloud and Jira Server or Data Center instances.
›How can I prevent the AI from making changes to my test cases?
You can enable read-only mode by setting the READ_ONLY_MODE environment variable to true, which hides all write-capable tools.
›What are the authentication requirements for Jira Cloud versus Server?
Jira Cloud requires an AIO Tests API access token, while Jira Server or Data Center uses your Jira base URL and either a Personal Access Token or your username and API token.
›Can I restrict which tools are available to the AI?
Yes, you can use the ENABLED_TOOLS environment variable to provide a comma-separated allowlist of specific tools the server should expose.
›What are the system requirements for running this server?
The server requires Python 3.10 or higher and is typically installed using uvx.
›Does the server support BDD test cases?
Yes, the server allows for both reading and creating test cases formatted as Classic or BDD steps.
Alternatives
Badge
Maintain this server? Add the live badge to your README.