jira-stories
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | The email address associated with the Jira account. | |
| JIRA_BASE_URL | Yes | The base URL of the Jira Cloud instance. | |
| JIRA_API_TOKEN | Yes | The API token for authenticating with Jira Cloud. |
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 |
|---|---|
| jira_list_projectsA | Lista os projetos Jira que a conta pode visualizar. |
| jira_get_issue_typesA | Lista os tipos de issue permitidos no projeto informado. |
| jira_get_create_fieldsA | Lista os campos disponíveis e obrigatórios ao criar uma issue para projeto e tipo. |
| jira_search_issuesA | Busca issues existentes por JQL para evitar duplicidade. |
| jira_preview_issueA | Gera os campos que seriam publicados, sem chamar o Jira. |
| jira_create_issueB | Cria uma issue no Jira. Exige confirmPublish: true após revisão. |
| jira_update_issueC | Atualiza campos de uma issue existente. Exige confirmPublish: true. |
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
Most tools target clearly distinct actions: list projects, get metadata, search issues, preview, create, and update. The main potential confusion is between jira_get_create_fields and jira_preview_issue, since both relate to issue creation fields, though one describes the schema and the other previews actual values.
Every tool follows the same jira_<verb>_<noun> pattern using snake_case. The verbs are clear and consistently used, making the tool set highly predictable.
Seven tools is well-scoped for a Jira issue creation/update workflow. Each tool serves a necessary step in the process without unnecessary redundancy.
The workflow covers project discovery, issue type/field metadata, duplicate checking, preview, creation, and update. A direct get-single-issue tool is missing but search can serve that purpose, and deeper Jira lifecycle operations like transitions are outside the apparent scope.