Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Secure MCP server for WorkBoard OKR and strategy execution platform
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"workboard": {
"command": "uvx",
"args": [
"mcp-workboard-crunchtools"
]
}
}
}在终端中运行这条命令
claude mcp add workboard -- uvx mcp-workboard-crunchtools粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"workboard": {
"command": "uvx",
"args": [
"mcp-workboard-crunchtools"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"workboard": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-workboard-crunchtools"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 crunchtools 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.6.1)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SSTracker free youth training
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Free youth sports drills, practice plans and age-group answers for parents and coaches.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A secure MCP (Model Context Protocol) server for WorkBoard OKR and strategy execution platform.
This MCP server is designed to be:
quay.io/crunchtools/mcp-workboard built on Hummingbird Python base image| Component | Name |
|---|---|
| GitHub repo | crunchtools/mcp-workboard |
| Container | quay.io/crunchtools/mcp-workboard |
| Python package (PyPI) | mcp-workboard-crunchtools |
| CLI command | mcp-workboard-crunchtools |
| Module import | mcp_workboard_crunchtools |
The container image is built on the Hummingbird Python base image from Project Hummingbird, which provides:
workboard_get_user_tool - Get a user by ID or the current authenticated userworkboard_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 userworkboard_get_objectives_tool - Get all objectives a user ownsworkboard_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 resultsworkboard_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)workboard_get_my_key_results_tool - List current user's key results with metric IDs and progressworkboard_update_key_result_tool - Update key result progress for weekly OKR check-insworkboard_get_workstreams_tool - Get team workstreams accessible to the authenticated userworkboard_get_workstream_activities_tool - Get workstream details with all action itemsworkboard_get_workstream_columns_tool - List the Kanban columns in use on a workstreamworkboard_get_team_workstreams_tool - Get all workstreams belonging to a specific teamworkboard_create_workstream_tool - Create a new workstream for a teamworkboard_update_workstream_tool - Update workstream properties (name, dates, pace, health, priority)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 redirectuvx mcp-workboard-crunchtools
pip install mcp-workboard-crunchtools
podman run -e WORKBOARD_API_TOKEN=your_token \
quay.io/crunchtools/mcp-workboard
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
In OAuth mode (WORKBOARD_CLIENT_ID + WORKBOARD_CLIENT_SECRET), a server reachable over HTTPS can be re-authorized without a shell:
https://workboard.example.com/callback, as the redirect URI of the WorkBoard app.WORKBOARD_OAUTH_REDIRECT_URI to that same URL. The proxy must route /callback to the server.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.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
| Variable | Default | Description |
|---|---|---|
WORKBOARD_OAUTH_REDIRECT_URI | unset | Public 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.json | Where OAuth tokens are stored |
User: Who am I in WorkBoard?
Assistant: [calls workboard_get_user with no args]
User: List all WorkBoard users
Assistant: [calls workboard_list_users]
User: Show me objectives for user 12345
Assistant: [calls workboard_get_objectives with user_id=12345]
User: Get details on objective 67890 for user 12345
Assistant: [calls workboard_get_objective_details with user_id=12345, objective_id=67890]
User: Show me my objectives (IDs: 2900058, 2900075, 2901770)
Assistant: [calls workboard_get_my_objectives with objective_ids=[2900058, 2900075, 2901770]]
User: Show me my key results
Assistant: [calls workboard_get_my_key_results]
User: Update key result 12345 to 75
Assistant: [calls workboard_update_key_result with metric_id=12345, value="75"]
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]
User: Show me my workstreams
Assistant: [calls workboard_get_workstreams]
User: Show me the agenda for workstream 4130463
Assistant: [calls workboard_get_workstream_activities with ws_id=4130463]
This server was designed with security as a primary concern. See SECURITY.md for:
git clone https://github.com/crunchtools/mcp-workboard.git
cd mcp-workboard uv sync
uv run pytest
uv run ruff check src tests
uv run mypy src
podman build -t mcp-workboard .
AGPL-3.0-or-later
Contributions welcome! Please read SECURITY.md before submitting security-related changes.