Skip to main content
Glama
jira-worklog-mcp

jira-worklog-mcp

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

add_worklog

Log work on an issue (POST /issue/{key}/worklog).

list_worklogs

List an issue's worklogs (verify / check for duplicates).

whoami

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

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 build

Compiles 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

JIRA_BASE_URL

https://your-site.atlassian.net

JIRA_EMAIL

you@example.com

JIRA_API_TOKEN

(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.js

Register 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:

  1. toggl-mcp → list_time_entries { start_date, end_date, exclude_tag: "jira-logged" } — each entry has task_name (the Jira key), start, duration; skip running timers.

  2. jira-worklog-mcp → add_worklog { issue_key: task_name, time_spent_seconds: duration, started: start, comment: description } per entry.

  3. 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 smoke

A self-cleaning end-to-end worklog test (writes to a real issue, then deletes it — use a throwaway ticket):

npm run worklogtest -- TEST-123

Notes

  • 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-logged tag; list_worklogs is available if you also want to check the Jira side.

Available Tools

3 tools
add_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 issueA
Read-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 authA
Read-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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: adding a worklog, listing worklogs, and getting user info. There is no overlap or confusion between them.

    Naming Consistency4/5

    Most tools follow verb_noun pattern (add_worklog, list_worklogs), but whoami breaks the pattern. Naming is mostly consistent with minor deviation.

    Tool Count5/5

    Three tools is appropriate for a focused worklog management server. Each tool provides essential functionality without excess.

    Completeness3/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers