Summary
We need MCP access to team-scoped, date-range-filtered objectives so weekly/quarterly OKR snapshots can include objectives from past quarters (e.g. Q1 after March 31). Today workboard_get_objectives_tool is user-scoped and silently drops objectives whose target date is in the past, which does not match how the WorkBoard web UI behaves.
Proposed direction
Use the same endpoint the UI uses for this view, e.g.:
GET /goal/goalSummary with query parameters such as userTeamid, startDate, endDate, exDate, team_people, status, performance, etc.
Implementation draft: #24 (workboard_get_team_objectives_tool).
Blocker
Blocked on the WorkBoard API: the upstream product/API does not yet reliably support what this PR implements (team goalSummary-style access from the documented/authenticated API surface we use in this server). Until WorkBoard exposes and supports this behavior for our integration path, the PR remains speculative / integration-blocked even though the client code can be merged when the repo maintainers agree.
Tracking this issue explicitly so downstream consumers (e.g. weekly OKR snapshot skills) know the capability is pending API support, not only an MCP change.
Acceptance criteria (when unblocked)
Summary
We need MCP access to team-scoped, date-range-filtered objectives so weekly/quarterly OKR snapshots can include objectives from past quarters (e.g. Q1 after March 31). Today
workboard_get_objectives_toolis user-scoped and silently drops objectives whose target date is in the past, which does not match how the WorkBoard web UI behaves.Proposed direction
Use the same endpoint the UI uses for this view, e.g.:
GET /goal/goalSummarywith query parameters such asuserTeamid,startDate,endDate,exDate,team_people,status,performance, etc.Implementation draft: #24 (
workboard_get_team_objectives_tool).Blocker
Blocked on the WorkBoard API: the upstream product/API does not yet reliably support what this PR implements (team
goalSummary-style access from the documented/authenticated API surface we use in this server). Until WorkBoard exposes and supports this behavior for our integration path, the PR remains speculative / integration-blocked even though the client code can be merged when the repo maintainers agree.Tracking this issue explicitly so downstream consumers (e.g. weekly OKR snapshot skills) know the capability is pending API support, not only an MCP change.
Acceptance criteria (when unblocked)
goalSummary(or equivalent) is supported for the same auth model as other read tools in this MCP server.get_objectives/ single-goal endpoints.