What is your set up?
Self Hosted Docker (Kubernetes)
Is your feature request related to a problem? Please describe
Our scheduled “30-minute checkpoint” watchers only need: status histogram + a short list of In Progress tickets (id, headline, project, assignee, modified, commentCount). Today they must call Tickets.getAll (huge payload), filter client-side, or fall back to read-only SQL against MariaDB when JSON-RPC is rate-limited / truncated in agent context.
Describe the solution you'd like
A first-class discovery endpoint (JSON-RPC and/or MCP tool), for example Tickets.getStatusSummary / list_tickets_summary, returning something like:
{
"counts": { "0": 12, "1": 3, "2": 5, "3": 20, "4": 4 },
"active": [
{
"id": 123,
"headline": "...",
"projectId": 16,
"status": 4,
"editorId": 2,
"dependingTicketId": null,
"modified": "2026-07-27T00:00:00Z",
"commentCount": 7
}
]
}Filters: optional projectId, status / statusType, modifiedAfter, include/exclude subtasks.
Additional context
Rate-limit increases (#3591 / 120 API, 300 MCP) help, but payload size and context flooding remain the bottleneck for agentic clients. A compact summary would make Leantime a much better “source of truth” for MCP-driven PM loops. We already prototype this client-side and would happily test an upstream shape.
What is your set up?
Self Hosted Docker (Kubernetes)
Is your feature request related to a problem? Please describe
Our scheduled “30-minute checkpoint” watchers only need: status histogram + a short list of In Progress tickets (id, headline, project, assignee, modified, commentCount). Today they must call
Tickets.getAll(huge payload), filter client-side, or fall back to read-only SQL against MariaDB when JSON-RPC is rate-limited / truncated in agent context.Describe the solution you'd like
A first-class discovery endpoint (JSON-RPC and/or MCP tool), for example
Tickets.getStatusSummary/list_tickets_summary, returning something like:{ "counts": { "0": 12, "1": 3, "2": 5, "3": 20, "4": 4 }, "active": [ { "id": 123, "headline": "...", "projectId": 16, "status": 4, "editorId": 2, "dependingTicketId": null, "modified": "2026-07-27T00:00:00Z", "commentCount": 7 } ] }Filters: optional
projectId,status/statusType,modifiedAfter, include/exclude subtasks.Additional context
Rate-limit increases (#3591 / 120 API, 300 MCP) help, but payload size and context flooding remain the bottleneck for agentic clients. A compact summary would make Leantime a much better “source of truth” for MCP-driven PM loops. We already prototype this client-side and would happily test an upstream shape.