jira-issue-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Email address for Atlassian Cloud API token authentication | |
| JIRA_BASE_URL | Yes | Base URL of your Jira instance, e.g. https://your-domain.atlassian.net | |
| JIRA_API_TOKEN | No | API token for Atlassian Cloud authentication | |
| JIRA_ISSUE_KEY | No | Fallback issue key if not provided in tool call | |
| JIRA_COOKIE_NAME | No | Name of the session cookie (default is tenant.session.token) | |
| JIRA_BEARER_TOKEN | No | Bearer token for authentication | |
| JIRA_MAX_IMAGE_MB | No | Maximum image size in MB for attachments (default 8) | |
| JIRA_SESSION_TOKEN | No | Session cookie value for cookie-based 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_issue_contextA | Devuelve contexto read-only de una issue concreta: titulo, descripcion, comentarios y adjuntos de imagen. Cuando el usuario escriba una clave Jira en el chat, pasala como issueKey. |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap.
With a single tool, naming is trivially consistent.
A single tool for a Jira domain is insufficient; typical Jira servers have multiple tools for CRUD and search operations.
Only read-only context is provided; missing essential operations like listing issues, updating, or creating issues, making the surface severely incomplete.