MCP Workboard MCP Server

Secure MCP server for WorkBoard OKR and strategy execution platform

Local serverstdioPython

What is the MCP Workboard MCP server?

MCP Workboard MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Secure MCP server for WorkBoard OKR and strategy execution platform.

What you get

  • Minimal CVE exposure — - Built with a minimal package set, dramatically reducing attack surface
  • Regular updates — - Security patches applied promptly
  • Optimized for Python — - Pre-configured with uv package manager
  • Production-ready — - Proper signal handling and non-root user defaults

What the assistant can call

Once MCP Workboard is connected, these are the calls the assistant has available:

  • workboard_get_user — Get a user by ID or the current authenticated user
  • workboard_list_users — List all users (Data-Admin role required)
  • workboard_create_user — Create a new user (Data-Admin role required)
  • workboard_update_user — Update an existing user
  • workboard_get_objectives — Get objectives associated with a user (API capped at 15)
  • workboard_get_objective_details — Get details for a specific objective with key results
  • workboard_get_my_objectives — Get the current user's owned objectives by ID (recommended)
  • workboard_create_objective — Create a new objective with key results (Data-Admin required)
  • workboard_get_my_key_results — List current user's key results with metric IDs and progress
  • workboard_update_key_result — Update key result progress for weekly OKR check-ins
  • workboard_get_workstreams — Get team workstreams accessible to the authenticated user
  • workboard_get_workstream_activities — Get workstream details with all action items

Setting it up

mcp-workboard-crunchtools on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: WORKBOARD_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Workboard's toolset — workboard_get_user, workboard_list_users, workboard_create_user and 11 more — is a fair guide to whether it matches your workflow. It is maintained by crunchtools; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Workboard.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp workboard mcp server does with a few real requests.

Available tools

ToolWhat it does
workboard_get_userGet a user by ID or the current authenticated user
workboard_list_usersList all users (Data-Admin role required)
workboard_create_userCreate a new user (Data-Admin role required)
workboard_update_userUpdate an existing user
workboard_get_objectivesGet objectives associated with a user (API capped at 15)
workboard_get_objective_detailsGet details for a specific objective with key results
workboard_get_my_objectivesGet the current user's owned objectives by ID (recommended)
workboard_create_objectiveCreate a new objective with key results (Data-Admin required)
workboard_get_my_key_resultsList current user's key results with metric IDs and progress
workboard_update_key_resultUpdate key result progress for weekly OKR check-ins
workboard_get_workstreamsGet team workstreams accessible to the authenticated user
workboard_get_workstream_activitiesGet workstream details with all action items
workboard_get_team_workstreamsGet all workstreams belonging to a specific team
workboard_create_workstreamCreate a new workstream for a team

How to install the MCP Workboard MCP server

{
  "mcpServers": {
    "workboard": {
      "command": "uvx",
      "args": ["mcp-workboard-crunchtools"],
      "env": {
        "WORKBOARD_API_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
WORKBOARD_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Workboard to workboard get user.
  • Use MCP Workboard to workboard list users.
  • Use MCP Workboard to workboard create user.

Frequently asked questions

It connects MCP Workboard to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (workboard_get_user, workboard_list_users, workboard_create_user, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Workboard directly.