Jira worklog retrieval limit on MCP

[tcunha]

We are currently hitting a limitation on the MCP where we can only retrieve and view up to 20 Jira worklogs at a time.

Because we rely on this data for accurate daily time tracking and team reporting, we need visibility into the full set of logs. Is this 20-item cap a hard limit on the MCP side, or can we adjust the parameter/payload to return a larger dataset or enable pagination?

Let me know what our options are here.

Best regards,

[David Day]

I'm curious, what's the total item size you're aiming to retrieve in one call, hundreds  or over 1000?

[zoltanersek _outpostlabs_dev_]

hopefully someone from atlassian can clear this up, is the worklog limit coming from the mcp or from the underlying jira rest api call? 

[Jason Krewson]

I'm not sure on this one and all I could find is Worklogs beyond the first 20 per issue cannot be retrieved — no tool exposes GET /rest/api/3/issue/{issueIdOrKey}/worklog . 

I did look for an Atlassian reference on if this is a bug or a feature and came up with nothing. 

I would recommend following up with Atlassian Support to verify, and if you do please let us know their response.

Others in the community might know and respond here as well so we will see.

Update: Maybe I did find it here Support pagination for getJiraIssue and searchJiraIssuesUsingJql tools in MCP , if this is what you are looking for also you can log in, vote and follow it.

[Jason Krewson]

You could always do this using the Jira REST API instead of MCP as it supports pagination. 

Reference: Issue worklogs