jira-worklog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_BASE_URL | Yes | Your Jira site URL, e.g. https://your-site.atlassian.net | |
| JIRA_API_TOKEN | Yes | Your Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens |
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 |
|---|---|
| add_worklogA | Log work against a Jira issue (POST worklog). issue_key is the ticket (e.g. LEGLINK-142), time_spent_seconds is the duration, started defaults to now (RFC3339; normalized to Jira's required format), and comment is optional. Jira records time at minute granularity (minimum 60s). |
| list_worklogsA | List the worklogs on a Jira issue (id, author, time, started, comment). Useful to verify what was logged or to check for duplicates before adding more. |
| whoamiA | Return the authenticated Jira user (display name, accountId, email). Use to confirm credentials. |
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 3 tools
Each tool serves a distinct purpose: adding a worklog, listing worklogs, and getting user info. There is no overlap or confusion between them.
Most tools follow verb_noun pattern (add_worklog, list_worklogs), but whoami breaks the pattern. Naming is mostly consistent with minor deviation.
Three tools is appropriate for a focused worklog management server. Each tool provides essential functionality without excess.
Covers basic add and list operations but lacks update and delete worklog functionality. The whoami tool is auxiliary. The surface is somewhat incomplete for full worklog lifecycle management.