Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

MCP Workboard

by crunchtoolsversion 0.6.1i★ –iRuns on your computer
Registry nameio.github.crunchtools/workboard

Install

Overview

Description from the maker (original English)

Secure MCP server for WorkBoard OKR and strategy execution platform

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "workboard": {
      "command": "uvx",
      "args": [
        "mcp-workboard-crunchtools"
      ]
    }
  }
}

Run this in your terminal

claude mcp add workboard -- uvx mcp-workboard-crunchtools

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "workboard": {
      "command": "uvx",
      "args": [
        "mcp-workboard-crunchtools"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "workboard": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-workboard-crunchtools"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account crunchtools, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32464 servers in this category
  • Published to the registry more recently than 3% of the other 32464 servers in this category
  • Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Workboard safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.6.1) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MCP WorkBoard CrunchTools

A secure MCP (Model Context Protocol) server for WorkBoard OKR and strategy execution platform.

Overview

This MCP server is designed to be:

  • Secure by default - Threat modeling, input validation, and token protection
  • No third-party services - Runs locally via stdio, your API token never leaves your machine
  • Cross-platform - Works on Linux, macOS, and Windows
  • Automatically updated - GitHub Actions monitor for CVEs and update dependencies
  • Containerized - Available at quay.io/crunchtools/mcp-workboard built on Hummingbird Python base image

Naming Convention

ComponentName
GitHub repocrunchtools/mcp-workboard
Containerquay.io/crunchtools/mcp-workboard
Python package (PyPI)mcp-workboard-crunchtools
CLI commandmcp-workboard-crunchtools
Module importmcp_workboard_crunchtools

Why Hummingbird?

The container image is built on the Hummingbird Python base image from Project Hummingbird, which provides:

  • 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

Features

User Management (4 tools)
  • workboard_get_user_tool - Get a user by ID or the current authenticated user
  • workboard_list_users_tool - List all users (Data-Admin role required)
  • workboard_create_user_tool - Create a new user (Data-Admin role required)
  • workboard_update_user_tool - Update an existing user
Objective Management (5 tools)
  • workboard_get_objectives_tool - Get all objectives a user owns
  • workboard_get_team_objectives_tool - Get a team's objectives overlapping a date window, past quarters included (slow: reads every visible objective)
  • workboard_get_objective_details_tool - Get details for a specific objective with key results
  • workboard_get_my_objectives_tool - Get the current user's owned objectives by ID (recommended)
  • workboard_create_objective_tool - Create a new objective with key results (Data-Admin required)
Key Result Management (2 tools)
  • workboard_get_my_key_results_tool - List current user's key results with metric IDs and progress
  • workboard_update_key_result_tool - Update key result progress for weekly OKR check-ins
Workstream Management (6 tools)
  • workboard_get_workstreams_tool - Get team workstreams accessible to the authenticated user
  • workboard_get_workstream_activities_tool - Get workstream details with all action items
  • workboard_get_workstream_columns_tool - List the Kanban columns in use on a workstream
  • workboard_get_team_workstreams_tool - Get all workstreams belonging to a specific team
  • workboard_create_workstream_tool - Create a new workstream for a team
  • workboard_update_workstream_tool - Update workstream properties (name, dates, pace, health, priority)
Authorization (3 tools)
  • workboard_auth_status_tool - Report auth mode, token store, and whether the credential works (GET /user)
  • workboard_auth_start_tool - Return the WorkBoard authorize URL for browser approval (OAuth mode)
  • workboard_auth_result_tool - Report the outcome of the most recent authorization redirect

Installation

With uvx (Recommended)
uvx mcp-workboard-crunchtools
With pip
pip install mcp-workboard-crunchtools
With Container
podman run -e WORKBOARD_API_TOKEN=your_token \

quay.io/crunchtools/mcp-workboard

Configuration

Getting a WorkBoard API Token
  1. Log in to your WorkBoard instance
  2. Navigate to Admin Settings > API Configuration
  3. Generate a JWT API token
  4. Copy the token immediately - store it securely
Add to Claude Code
claude mcp add mcp-workboard \

--env WORKBOARD_API_TOKEN=your_token_here \ -- uvx mcp-workboard-crunchtools

Or for the container version:

claude mcp add mcp-workboard \

--env WORKBOARD_API_TOKEN=your_token_here \ -- podman run -i --rm -e WORKBOARD_API_TOKEN quay.io/crunchtools/mcp-workboard

OAuth on a Server (Container Behind a Reverse Proxy)

In OAuth mode (WORKBOARD_CLIENT_ID + WORKBOARD_CLIENT_SECRET), a server reachable over HTTPS can be re-authorized without a shell:

  1. Register the public callback URL, e.g. https://workboard.example.com/callback, as the redirect URI of the WorkBoard app.
  2. Run the server with an HTTP transport and set WORKBOARD_OAUTH_REDIRECT_URI to that same URL. The proxy must route /callback to the server.
  3. Call workboard_auth_start_tool, open the URL it returns and approve. WorkBoard redirects to /callback; the server exchanges the code and saves the tokens to the token store. The authorization expires after 10 minutes.
  4. Call workboard_auth_status_tool to confirm (or workboard_auth_result_tool to see why it failed).
podman run -p 8000:8000 \

-e WORKBOARD_CLIENT_ID -e WORKBOARD_CLIENT_SECRET \ -e WORKBOARD_OAUTH_REDIRECT_URI=https://workboard.example.com/callback \ -e WORKBOARD_TOKEN_STORE_PATH=/data/tokens.json -v workboard-tokens:/data:Z \ quay.io/crunchtools/mcp-workboard --transport streamable-http --host 0.0.0.0

VariableDefaultDescription
WORKBOARD_OAUTH_REDIRECT_URIunsetPublic URL of this server's /callback route. Required for workboard_auth_start_tool; the CLI login ignores it and uses http://localhost:8963/callback.
WORKBOARD_TOKEN_STORE_PATH~/.config/mcp-workboard/tokens.jsonWhere OAuth tokens are stored

Usage Examples

Get Current User
User: Who am I in WorkBoard?

Assistant: [calls workboard_get_user with no args]

List All Users
User: List all WorkBoard users

Assistant: [calls workboard_list_users]

Get User Objectives
User: Show me objectives for user 12345

Assistant: [calls workboard_get_objectives with user_id=12345]

Get Objective Details
User: Get details on objective 67890 for user 12345

Assistant: [calls workboard_get_objective_details with user_id=12345, objective_id=67890]

Get My Objectives
User: Show me my objectives (IDs: 2900058, 2900075, 2901770)

Assistant: [calls workboard_get_my_objectives with objective_ids=[2900058, 2900075, 2901770]]

List My Key Results
User: Show me my key results

Assistant: [calls workboard_get_my_key_results]

Update Key Result Progress
User: Update key result 12345 to 75

Assistant: [calls workboard_update_key_result with metric_id=12345, value="75"]

Create an Objective
User: Create an objective called "Increase retention" owned by user@example.com

Assistant: [calls workboard_create_objective with name, owner, dates, and optional key_results]

List Workstreams
User: Show me my workstreams

Assistant: [calls workboard_get_workstreams]

Get Workstream Action Items
User: Show me the agenda for workstream 4130463

Assistant: [calls workboard_get_workstream_activities with ws_id=4130463]

Security

This server was designed with security as a primary concern. See SECURITY.md for:

  • Threat model and attack vectors
  • Defense in depth architecture
  • Token handling best practices
  • Input validation rules
Key Security Features
  1. Token Protection
  • Stored as SecretStr (never accidentally logged)
  • Environment variable only (never in files or args)
  • Sanitized from all error messages
  1. Input Validation
  • Pydantic models for all inputs
  • Positive integer validation for IDs
  • Email validation for user creation
  1. API Hardening
  • Hardcoded API base URL (prevents SSRF)
  • TLS certificate validation
  • Request timeouts
  • Response size limits
  1. Automated CVE Scanning
  • GitHub Actions scan dependencies weekly
  • Automatic issues for security updates
  • Dependabot alerts enabled

Development

Setup
git clone https://github.com/crunchtools/mcp-workboard.git

cd mcp-workboard uv sync

Run Tests
uv run pytest
Lint and Type Check
uv run ruff check src tests

uv run mypy src

Build Container
podman build -t mcp-workboard .

License

AGPL-3.0-or-later

Contributing

Contributions welcome! Please read SECURITY.md before submitting security-related changes.

Links

Ask PopNx