Report whether this server currently holds a usable WorkBoard credential.

Call this first. It says which auth mode is active, where tokens are stored, whether one exists, and verifies it with GET /user. If it is not usable, it says which tool fixes it.

Begin browser authorization and return the URL for the user to approve.

Open the returned URL. The user approves there, WorkBoard redirects back to this server, and the tokens are stored automatically -- nothing is copied back by hand. Then call workboard_auth_status_tool to confirm. Requires OAuth mode and WORKBOARD_OAUTH_REDIRECT_URI.

Report the outcome of the most recent authorization redirect.

Get a WorkBoard user by ID, or the current authenticated user.

List WorkBoard users.

scope="team" (default) returns members of teams you can see and works for any account. scope="org" returns every user in the organization and requires a Data-Admin token. Returns up to 100 users; use limit and offset to page.

Create a new WorkBoard user (requires Data-Admin role).

Update an existing WorkBoard user.

Get all teams the authenticated user belongs to.

Returns team IDs, names, and owner user IDs. Use workboard_get_team_members_tool to get the full member list (with user_ids) for a specific team.

Get all members of a WorkBoard team, including their user IDs and emails.

Use this to resolve a person's name or email to their WorkBoard user_id. Combine with workboard_get_objectives_tool(user_id) to fetch their OKRs.

Get objectives owned by a WorkBoard user by their user ID.

Returns all objectives the user owns, with full pagination. Also exposes workstreams and status_color fields on each objective when present.

Use workboard_get_user_tool (no arguments) to find the current user's ID. Use workboard_get_team_members_tool to resolve a name or email to a user ID.

Get a team's objectives whose dates overlap a window, past quarters included.

Use this for quarterly OKR reviews or snapshots, e.g. Q1 after March 31. Objectives on sub-teams are not included. Slow: it reads every objective you can see, which takes about a minute.

Use workboard_get_teams_tool to find team IDs.

Get full details for a single objective including all its key results.

Returns the objective name, progress, status, dates, and all key results (metrics) with their targets, progress, and update schedules.

Use workboard_get_user_tool (no arguments) to find the current user's ID.

Get the current authenticated user's objectives with key results.

This is the RECOMMENDED tool when users ask about "my objectives" or "my OKRs". It automatically determines the current user and discovers their objectives from their key results — no IDs needed.

List all key results (metrics) the current user owns or has access to.

Use this to find metric IDs and see current progress before updating with workboard_update_key_result_tool. Returns metric names, current values, targets, and IDs.

By default, only shows current year key results. Set include_prior_years=True to see key results from previous years.

List key results (metrics) for a specific WorkBoard user by their user ID.

Use this to see KRs owned by or associated with any user — for example, to review a direct report's key results before a 1:1. Skills layer maps organizational roles (e.g. "direct report") to user IDs; this tool only knows about WorkBoard user IDs.

Use workboard_get_teams_tool and workboard_get_team_members_tool to resolve a person's name to their user ID.

By default, only shows current year key results. Set include_prior_years=True to see key results from previous years.

Update progress on a key result (metric). This is the primary tool for weekly OKR check-ins — update a key result's value without logging into WorkBoard.

Use workboard_get_my_key_results_tool to find metric IDs first.

Create a new objective with optional key results.

Creates Team or Individual objectives. Requires an OAuth token whose account has the Data-Admin role; instant JWT tokens cannot create objectives. The API has no update or delete for objectives — those are UI-only.

Team objectives must be tied to a team: pass team (a team ID from workboard_get_teams_tool). Provide the objective name, owner, dates, and optionally key results with targets. Each key result has a name and optional start_value, target_value, and unit_type (e.g. "Number", "Currency", "Percent").

Get team workstreams accessible to the authenticated user.

Returns all team workstreams the user has access to. Personal workstreams are not included. Optionally filter to a single workstream by ID.

Get a workstream's full details including all action items.

Returns the workstream metadata plus every action item with descriptions, owners, due dates, comments, sub-actions, and attached files.

Get the custom Kanban columns in use on a workstream.

The API has no column endpoint, so columns are read off the workstream's action items. A column with no cards in it will not appear. Use the column_id values to tell which column a card sits in.

Get all workstreams belonging to a specific team.

Use workboard_get_teams_tool to find team IDs first.

Create a new workstream for a team.

Requires team manager or co-manager permissions.

Update an existing workstream's properties.

Performs read-before-write to confirm the workstream exists. Requires team manager or co-manager permissions. Pace must be "slow", "fast", or "steady". Health must be "ok", "good", or "risk". Priority must be "p1" through "p5".

List action items accessible to the authenticated user.

Returns up to 15 action items by default. Use limit and offset for pagination. Filter by owner, state, priority, or effort to narrow results.

Get a single WorkBoard action item by its ID.

Create a new action item (card) on a WorkBoard workstream.

State must be "next", "doing", "done", or "pause". Priority must be "low", "med", or "high". Effort must be "easy", "medium", or "huge".

Update an existing WorkBoard action item.

Performs read-before-write to confirm the action item exists. Only provided fields are updated. State must be "next", "doing", "done", or "pause". Priority must be "low", "med", or "high". Effort must be "easy", "medium", or "huge".