jira-aio-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | The URL of your Jira instance (including port if necessary) | |
| JIRA_TOKEN | Yes | Your Jira API token for authentication |
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 |
|---|---|
| get_aio_testcaseC | Get test case details from AIO |
| search_aio_testcaseB | Search test cases by project and/or folders |
| get_aio_foldersB | Get folder structure of a project |
| get_aio_projectsA | Get list of all projects in AIO |
| update_caseA | Update an AIO test case. Changes only explicitly passed fields (title, description, precondition, status, priority, steps). Response includes rollback with previous values, especially for steps. |
| create_caseA | Create an AIO test case. Required: projectKey, title, folderId. Optional: description, precondition, status, priority, steps, requirements. Status/priority IDs are taken from the project config. Steps and Jira requirements are saved after create. |
| create_folderA | Create an AIO test case folder. Required: projectKey, name. Optional: parentId or parent (folder ID, name, or path). Without parent the folder is created at the project root. |
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 7 tools
Each tool targets a distinct action or resource: get vs search, projects vs folders vs test cases, and create vs update are clear. There is no meaningful overlap that would cause an agent to select the wrong tool.
The tool naming is readable but inconsistent: four tools follow a get_aio_* pattern, while three use bare verb_noun forms like create_case and create_folder. This mix of conventions makes the set feel less unified, even though the verb and noun components are clear.
Seven tools is well-scoped for an AIO test-case management server: project discovery, folder navigation, test-case search/retrieval, creation, and update are all represented. Each tool serves a clear purpose without redundancy.
The set covers project listing, folder handling, and test-case create/read/update/search, but there is no delete operation for either test cases or folders. This notable lifecycle gap prevents full end-to-end management of AIO test cases.