jira-sisoog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | The base URL of the Jira instance. Defaults to https://jira.sisoog.com | https://jira.sisoog.com |
| JIRA_USERNAME | Yes | The Jira username | |
| JIRA_API_TOKEN | Yes | The Jira password or Personal Access Token | |
| JIRA_AUTH_TYPE | No | Authentication type: 'basic' (default) or 'bearer' | basic |
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_myselfA | Verify Jira authentication and return the current user profile. |
| jira_searchA | Search Jira issues with JQL. Example: assignee = currentUser() AND resolution = Unresolved ORDER BY updated DESC |
| jira_get_issueA | Get full details for a Jira issue by key (e.g. APP-1851). |
| jira_add_worklogC | Log work on an issue. timeSpent uses Jira format like 1h, 30m, 2h 15m. |
| jira_get_worklogsB | List worklogs for an issue. |
| jira_update_worklogA | Update an existing worklog (timeSpent, started, comment). Prefer this over UpdateWorklog.jspa. |
| jira_delete_worklogB | Delete a worklog from an issue. |
| jira_update_issueB | Update common issue fields (summary, description, labels, assignee username). |
| jira_get_transitionsA | List available status transitions for an issue. |
| jira_transition_issueA | Transition an issue to another status using a transition id from jira_get_transitions. |
| jira_add_commentA | Add a comment to an issue. |
| jira_my_open_issuesB | Shortcut: list unresolved issues assigned to the current user. |
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 12 tools
Each tool has a distinct resource and action: search vs. get issue vs. worklog operations vs. transitions vs. comments. The only potential overlap is jira_search and jira_my_open_issues, but the latter is clearly a shortcut for a specific filtered search, so ambiguity is minimal.
Most tools follow a consistent verb_noun pattern (jira_get_issue, jira_add_worklog, jira_update_issue). Two exceptions jira_myself and jira_my_open_issues break the pattern, but they are easy to understand and do not cause confusion.
With 12 tools covering issue retrieval, updates, worklogs, transitions, comments, and user info, the scope is well-sized for a Jira integration without being overwhelming.
The set covers read, update, transition, comment, and worklog operations, but notably lacks any way to create a new Jira issue. This is a significant gap for a Jira server, as issue creation is a core workflow that agents would likely need.