jira-worklog-mcp
Allows logging work on Jira issues, listing worklogs, and verifying credentials via the Jira Cloud API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jira-worklog-mcp log 1.5 hours to PROJECT-42 for code review"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jira-worklog-mcp
A small local MCP server for Jira Cloud worklogs — the piece the Atlassian MCP doesn't cover. Pairs with toggl-mcp to push tracked time into Jira at the end of the day.
Tool | What it does |
| Log work on an issue ( |
| List an issue's worklogs (verify / check for duplicates). |
| Confirm the configured credentials. |
The Jira quirks are baked in: Basic-auth, the started format yyyy-MM-dd'T'HH:mm:ss.SSSZ (offset without a colon, no bare Z), and ADF-wrapped comments.
Prerequisites
Node.js 18+.
A Jira API token — create one at https://id.atlassian.com/manage-profile/security/api-tokens.
Your Atlassian account email and your Jira site URL (e.g.
https://your-site.atlassian.net).
Related MCP server: AtlassianJira MCP Integration Server
Build
git clone https://github.com/MikeAtPinnacle/jira-worklog-mcp.git
cd jira-worklog-mcp
npm install
npm run buildCompiles to dist/index.js — note its absolute path for the config below.
Configuration
The server reads three env vars (provide them via the MCP client's env block):
Var | Example |
|
|
|
|
| (from the link above) |
Auth is HTTP Basic base64(email:api_token) — the server does that for you.
Register with Claude Code
claude mcp add jira-worklog --scope user \
--env JIRA_BASE_URL=https://your-site.atlassian.net \
--env JIRA_EMAIL=you@example.com \
--env JIRA_API_TOKEN=<your_jira_api_token> \
-- node /absolute/path/to/jira-worklog-mcp/dist/index.jsRegister with Claude Desktop
Edit the Claude Desktop config (%APPDATA%\Claude\claude_desktop_config.json on Windows; ~/Library/Application Support/Claude/... on macOS; ~/.config/Claude/... on Linux):
{
"mcpServers": {
"jira-worklog": {
"command": "node",
"args": ["/absolute/path/to/jira-worklog-mcp/dist/index.js"],
"env": {
"JIRA_BASE_URL": "https://your-site.atlassian.net",
"JIRA_EMAIL": "you@example.com",
"JIRA_API_TOKEN": "<your_jira_api_token>"
}
}
}
}Tool inputs
add_worklog — started defaults to now; Jira records at minute granularity (min 60s).
{ "issue_key": "LEGLINK-142", "time_spent_seconds": 5400, "started": "2026-06-26T13:00:00Z", "comment": "Code review" }list_worklogs
{ "issue_key": "LEGLINK-142" }whoami — no arguments.
End-of-day flow (with toggl-mcp)
Claude orchestrates the two servers:
toggl-mcp→list_time_entries { start_date, end_date, exclude_tag: "jira-logged" }— each entry hastask_name(the Jira key),start,duration; skip running timers.jira-worklog-mcp→add_worklog { issue_key: task_name, time_spent_seconds: duration, started: start, comment: description }per entry.toggl-mcp→tag_time_entry { time_entry_id, tags: ["jira-logged"] }so the entry isn't logged again.
Because step 1 excludes jira-logged, the whole flow is safe to re-run.
Smoke test
export JIRA_BASE_URL="https://your-site.atlassian.net" # PowerShell: $env:JIRA_BASE_URL="..."
export JIRA_EMAIL="you@example.com"
export JIRA_API_TOKEN="<your_jira_api_token>"
npm run build && npm run smokeA self-cleaning end-to-end worklog test (writes to a real issue, then deletes it — use a throwaway ticket):
npm run worklogtest -- TEST-123Notes
stdio server: logs go to stderr only; stdout is reserved for the MCP protocol.
Rate limits: 429/5xx are retried with backoff (honoring
Retry-After).Dedupe is handled on the Toggl side via the
jira-loggedtag;list_worklogsis available if you also want to check the Jira side.
Available Tools
3 toolsadd_worklogAdd a Jira 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).
Inputs: issue_key (required), time_spent_seconds (required), comment, started.
list_worklogsList worklogs on an issueARead-only
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.
Inputs: issue_key (required).
whoamiVerify Jira authARead-only
Return the authenticated Jira user (display name, accountId, email). Use to confirm credentials.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.
Log time on Trello cards and read time reports. Free during early access.
Read time entries, projects, clients, tasks and invoices; log and update tracked time.
Log time on GitHub issues and pull requests: timers, entries, missing days, client hours.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables time tracking in Tempo with automatic timesheet generation from git commits, worklog management with roles and accounts, and integration with Jira for seamless project time logging.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Jira integration with dynamic configuration, time logging, task creation, issue updates, and bulk imports through natural language.MIT
- FlicenseNot gradedqualityDmaintenanceEnables logging time to Tempo (Jira time tracker) via natural language in Claude Desktop or OpenCode.-
- -licenseNot gradedqualityCmaintenanceEnables local time tracking for Jira cards/subtasks with a stopwatch, breaks, corrections, manual logging, and reports, storing data in a local JSON file without depending on the Jira API.-