MCP WorkBoard CrunchTools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKBOARD_API_TOKEN | Yes | Your WorkBoard JWT API token used for authentication. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workboard_get_user_toolA | Get a WorkBoard user by ID, or the current authenticated user. |
| workboard_list_users_toolA | List all WorkBoard users (requires Data-Admin role). Returns: List of all users |
| workboard_create_user_toolA | Create a new WorkBoard user (requires Data-Admin role). |
| workboard_update_user_toolC | Update an existing WorkBoard user. |
| workboard_get_teams_toolA | 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. Returns: List of teams with team_id, team_name, team_owner_id, is_team_owner |
| workboard_get_team_members_toolA | 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. |
| workboard_get_objectives_toolA | Get objectives owned by a WorkBoard user by their user ID. Returns all objectives the user owns, with full pagination. Also exposes
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. |
| workboard_get_objective_details_toolA | 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. |
| workboard_get_my_objectives_toolA | 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. |
| workboard_get_my_key_results_toolA | 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. |
| workboard_get_user_key_results_toolA | 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. |
| workboard_update_key_result_toolA | 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. |
| workboard_create_objective_toolA | Create a new objective with optional key results (requires Data-Admin token). Provide the goal name, owner, dates, and optionally key results with targets. Each key result dict can include: metric_name, metric_start, metric_target, metric_type. |
| workboard_get_workstreams_toolA | 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. |
| workboard_get_workstream_activities_toolA | 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. |
| workboard_get_team_workstreams_toolA | Get all workstreams belonging to a specific team. Use workboard_get_teams_tool to find team IDs first. |
| workboard_create_workstream_toolA | Create a new workstream for a team. Requires team manager or co-manager permissions. |
| workboard_update_workstream_toolA | 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". |
| workboard_list_activities_toolA | 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. |
| workboard_get_activity_toolB | Get a single WorkBoard action item by its ID. |
| workboard_create_activity_toolA | 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". |
| workboard_update_activity_toolA | 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". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/crunchtools/mcp-workboard'
If you have feedback or need assistance with the MCP directory API, please join our Discord server