jira-worklog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Atlassian account email. | |
| REDMINE_URL | No | Redmine base URL, e.g. https://redmine.example.com. | |
| ARTIA_SECRET | No | Artia integration Secret. | |
| GITHUB_TOKEN | No | GitHub personal access token (PAT). | |
| ARTIA_API_URL | No | Artia GraphQL URL. Default: https://api.artia.com/graphql. Optional. | |
| JIRA_BASE_URL | No | Jira Cloud URL, must be HTTPS and a *.atlassian.net host. | |
| WORK_PROVIDER | No | Active provider: jira, redmine, github, or artia. | jira |
| JIRA_API_TOKEN | No | Jira API token. | |
| JIRA_DAILY_JQL | No | JQL that resolves issue_key='daily' to a recurring monthly bucket issue. Optional. | |
| ARTIA_CLIENT_ID | No | Artia integration ClientId. | |
| ARTIA_FOLDER_ID | No | Default folder id for search_tasks. Optional. | |
| REDMINE_API_KEY | No | Redmine API key. | |
| ARTIA_ACCOUNT_ID | No | Account/workspace id used for get_task/worklogs. | |
| ARTIA_WORKLOG_STATUS_ID | No | Optional status id sent when creating a time entry. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_whoamiA | Checks whether Jira authentication works and returns identity when available. |
| jira_search_issuesA | Finds Jira issues. No args: current user's open issues. 'query': free text. 'jql': raw JQL. |
| jira_get_issueA | Returns a compact view of one issue: key, summary, status, type, assignee, priority, labels, and description text. |
| jira_add_commentA | Adds a comment to an issue. Plain text is converted to Jira ADF. |
| jira_log_workA | Logs one worklog. time_spent accepts 'H:MM' (for example '2:40') or '1h 30m'. started: 'YYYY-MM-DD' or 'YYYY-MM-DD HH:MM' (empty = now). Set issue_key='daily' to log into the configured monthly bucket (JIRA_DAILY_JQL) instead of guessing the key. |
| jira_log_work_batchA | Logs multiple worklogs. entries: list of {issue_key, time_spent, started?, comment?}. issue_key may be 'daily' to log into the configured monthly bucket (JIRA_DAILY_JQL). By default, entries that already have a worklog at the same date/time are skipped and returned for confirmation. Reports each row result. |
| jira_get_worklogsA | Lists worklogs from one issue. mine_only filters current user's worklogs. |
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 clear, distinct operation: auth check, issue search, single issue fetch, comment addition, single worklog entry, batch worklog entry, and worklog listing. Even the two worklog-logging tools are cleanly separated by singular vs. batch usage.
All tools follow a consistent jira_ + verb_noun pattern (search_issues, get_issue, add_comment, log_work, log_work_batch, get_worklogs). The only slight exception is jira_whoami, but it is a standard command-style name and does not break the overall consistency.
With 7 tools, the server is well-scoped for a Jira worklog-focused MCP. It provides all necessary supporting operations (auth, issue lookup, comments) without bloat, and every tool earns its place.
The core worklog operations of logging (single and batch) and retrieving are covered, along with issue search and comments. However, there are no tools to update or delete existing worklogs, which is a notable gap in the full lifecycle for a worklog management server.