What it does
Generate your daily standup from real GitHub, Jira, Linear, and Slack activity.
- Connects 在你的电脑上运行
- Account or key Needs GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 3/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Standup from your activity。按照 https://mcp.popnx.com/i/sathvic-kollu-standup-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
让 AI 帮你安装
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Standup from your activity,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "standup": { "command": "npx", "args": [ "-y", "standup-mcp" ], "env": { "GITHUB_TOKEN": "your-value", "JIRA_API_TOKEN": "your-value", "LINEAR_API_KEY": "your-value", "SLACK_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Standup from your activity 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
注册并创建 Standup from your activity 的密钥
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "standup": { "command": "npx", "args": [ "-y", "standup-mcp" ], "env": { "GITHUB_TOKEN": "your-value", "JIRA_API_TOKEN": "your-value", "LINEAR_API_KEY": "your-value", "SLACK_TOKEN": "your-value" } } } }只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
退出 Claude 再重新打开
试一试
用 Standup from your activity 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Standup from your activity,或回答中出现 Standup from your activity 的工具名称,就表示连接成功
5 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
JIRA_BASE_URL您的 Jira Cloud 站点,例如 https://your-company.atlassian.net查看英文原文
Your Jira Cloud site, e.g. https://your-company.atlassian.net.JIRA_EMAILAPI 令牌所属的 Atlassian 账户邮箱。查看英文原文
Atlassian account email the API token belongs to.SLACK_CHANNELS可选的、以逗号分隔的频道 ID 列表,在消息搜索不可用时进行扫描。查看英文原文
Optional comma-separated channel ids to scan when message search is unavailable.STANDUP_NAME可选的 standup 负责人显示名称。查看英文原文
Optional display name for the standup's owner.STANDUP_DEMO_MODE设置为 true 可强制使用演示数据集,即使存在凭据也是如此。查看英文原文
Set to true to force the demo dataset even when credentials are present.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Standup from your activity
Standup from your activity 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Standup from your activity 的应用
- 需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
- 需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
- 需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
可连接 Claude Code,但需要先准备
需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Standup from your activity,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user standup --env GITHUB_TOKEN=your-value --env JIRA_API_TOKEN=your-value --env LINEAR_API_KEY=your-value --env SLACK_TOKEN=your-value -- npx -y standup-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Standup from your activity 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
注册并创建 Standup from your activity 的密钥
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --scope user standup --env GITHUB_TOKEN=your-value --env JIRA_API_TOKEN=your-value --env LINEAR_API_KEY=your-value --env SLACK_TOKEN=your-value -- npx -y standup-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude Code 中输入 /mcp
应能看到 Standup from your activity 在列表中并显示已连接
试一试
用 Standup from your activity 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Standup from your activity,或回答中出现 Standup from your activity 的工具名称,就表示连接成功
5 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
JIRA_BASE_URL您的 Jira Cloud 站点,例如 https://your-company.atlassian.net查看英文原文
Your Jira Cloud site, e.g. https://your-company.atlassian.net.JIRA_EMAILAPI 令牌所属的 Atlassian 账户邮箱。查看英文原文
Atlassian account email the API token belongs to.SLACK_CHANNELS可选的、以逗号分隔的频道 ID 列表,在消息搜索不可用时进行扫描。查看英文原文
Optional comma-separated channel ids to scan when message search is unavailable.STANDUP_NAME可选的 standup 负责人显示名称。查看英文原文
Optional display name for the standup's owner.STANDUP_DEMO_MODE设置为 true 可强制使用演示数据集,即使存在凭据也是如此。查看英文原文
Set to true to force the demo dataset even when credentials are present.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Standup from your activity,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "standup": { "command": "npx", "args": [ "-y", "standup-mcp" ], "env": { "GITHUB_TOKEN": "your-value", "JIRA_API_TOKEN": "your-value", "LINEAR_API_KEY": "your-value", "SLACK_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Standup from your activity 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
注册并创建 Standup from your activity 的密钥
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
填写你的密钥
在 Standup from your activity 的设置中,GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Standup from your activity 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Standup from your activity,或回答中出现 Standup from your activity 的工具名称,就表示连接成功
5 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
JIRA_BASE_URL您的 Jira Cloud 站点,例如 https://your-company.atlassian.net查看英文原文
Your Jira Cloud site, e.g. https://your-company.atlassian.net.JIRA_EMAILAPI 令牌所属的 Atlassian 账户邮箱。查看英文原文
Atlassian account email the API token belongs to.SLACK_CHANNELS可选的、以逗号分隔的频道 ID 列表,在消息搜索不可用时进行扫描。查看英文原文
Optional comma-separated channel ids to scan when message search is unavailable.STANDUP_NAME可选的 standup 负责人显示名称。查看英文原文
Optional display name for the standup's owner.STANDUP_DEMO_MODE设置为 true 可强制使用演示数据集,即使存在凭据也是如此。查看英文原文
Set to true to force the demo dataset even when credentials are present.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Standup from your activity 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Standup from your activity,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "standup": { "type": "stdio", "command": "npx", "args": [ "-y", "standup-mcp" ], "env": { "GITHUB_TOKEN": "your-value", "JIRA_API_TOKEN": "your-value", "LINEAR_API_KEY": "your-value", "SLACK_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Standup from your activity 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
注册并创建 Standup from your activity 的密钥
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
填写你的密钥
在 Standup from your activity 的设置中,GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Standup from your activity 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Standup from your activity,或回答中出现 Standup from your activity 的工具名称,就表示连接成功
5 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
JIRA_BASE_URL您的 Jira Cloud 站点,例如 https://your-company.atlassian.net查看英文原文
Your Jira Cloud site, e.g. https://your-company.atlassian.net.JIRA_EMAILAPI 令牌所属的 Atlassian 账户邮箱。查看英文原文
Atlassian account email the API token belongs to.SLACK_CHANNELS可选的、以逗号分隔的频道 ID 列表,在消息搜索不可用时进行扫描。查看英文原文
Optional comma-separated channel ids to scan when message search is unavailable.STANDUP_NAME可选的 standup 负责人显示名称。查看英文原文
Optional display name for the standup's owner.STANDUP_DEMO_MODE设置为 true 可强制使用演示数据集,即使存在凭据也是如此。查看英文原文
Set to true to force the demo dataset even when credentials are present.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add --scope user standup --env GITHUB_TOKEN=your-value --env JIRA_API_TOKEN=your-value --env LINEAR_API_KEY=your-value --env SLACK_TOKEN=your-value -- npx -y standup-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"standup": {
"command": "npx",
"args": [
"-y",
"standup-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"JIRA_API_TOKEN": "your-value",
"LINEAR_API_KEY": "your-value",
"SLACK_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"standup": {
"command": "npx",
"args": [
"-y",
"standup-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"JIRA_API_TOKEN": "your-value",
"LINEAR_API_KEY": "your-value",
"SLACK_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"standup": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"standup-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"JIRA_API_TOKEN": "your-value",
"LINEAR_API_KEY": "your-value",
"SLACK_TOKEN": "your-value"
}
}
}
}需要你填写的值
GITHUB_TOKEN机密 必填 envGitHub 只读个人访问令牌。可启用提交、PR 和评审。若不设置任何来源,则使用内置演示数据。查看英文原文
GitHub read-only personal access token. Enables commits, PRs, and reviews. Leave all sources unset to use the built-in demo data.JIRA_BASE_URLenv您的 Jira Cloud 站点,例如 https://your-company.atlassian.net查看英文原文
Your Jira Cloud site, e.g. https://your-company.atlassian.net.JIRA_EMAILenvAPI 令牌所属的 Atlassian 账户邮箱。查看英文原文
Atlassian account email the API token belongs to.JIRA_API_TOKEN机密 必填 env来自 id.atlassian.com 的 Jira API 令牌。仅用于只读。查看英文原文
Jira API token from id.atlassian.com. Read-only use.LINEAR_API_KEY机密 必填 envLinear 个人 API 密钥(只读)。可用于更改问题状态和发表评论。查看英文原文
Linear personal API key (read-only). Enables issue state changes and comments.SLACK_TOKEN机密 必填 env具有读取权限的 Slack 令牌。启用后可扫描您自己的消息,查找阻塞性用语。查看英文原文
Slack token with read scopes. Enables scanning your own messages for blocker language.SLACK_CHANNELSenv可选的、以逗号分隔的频道 ID 列表,在消息搜索不可用时进行扫描。查看英文原文
Optional comma-separated channel ids to scan when message search is unavailable.STANDUP_NAMEenv可选的 standup 负责人显示名称。查看英文原文
Optional display name for the standup's owner.STANDUP_DEMO_MODEenv设置为 true 可强制使用演示数据集,即使存在凭据也是如此。查看英文原文
Set to true to force the demo dataset even when credentials are present.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 sathvic-kollu 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于5个月前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
已公开的漏洞(OSV.dev)
OSV.dev 中没有 standup-mcp@0.1.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/sathvic-kollu-standup-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6182 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6182 个服务器的 16% 更新
- 基础检查结果等于或优于此分类中其他 6182 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Standup from your activity 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于5个月前,最新版本(0.1.0)于5个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Standup from your activity | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
standup-mcp
Generate your daily standup from what you actually did, across GitHub, Jira, Linear, and Slack.
Every standup, you stop and reconstruct yesterday from memory: which commits, which PR, which ticket you moved, that Slack thread where you said you were stuck. The work is already recorded across your tools. Re-typing it is the chore everyone hates, so updates come out vague ("worked on the thing") and real blockers go unsaid.
standup-mcp reads that activity back and writes the draft for you. You ask your AI assistant "what should I say at standup today?" and it answers from your real GitHub, Jira, Linear, and Slack activity: grouped by work item, in concrete deltas, with blockers it noticed on its own.
It is a standard Model Context Protocol server, so it works in any MCP client (Claude, Cursor, Cline, and more) on any model. It is local and read-only: nothing about your activity leaves your machine except the calls to those tools' own APIs, and it needs no AI API key of its own. The host client supplies the model.
See it in 30 seconds (no accounts needed)
The server ships with a realistic demo dataset and runs against it automatically when no credentials are set, so you see the output before connecting anything:
npx -y standup-mcp --demo
That prints a full standup from a synthetic day across all four tools. Here is the headline tool:
# Standup: Jordan Lee
_since Tue Jun 16. Demo data, no credentials configured._
Yesterday
- PROJ-412 Biometric re-auth · opened PR #128, 3 commits, latest "handle expired challenge edge case", moved to In Progress, posted an update
- ENG-88 Rate-limit the export endpoint · 2 commits, latest "tests for limiter window", moved to In Progress, posted an update
- PROJ-407 Card dispute webhook · merged PR #125, moved to In Review
- Reviewed PR #129: Tidy currency formatting helpers
Today
- Continue PROJ-412 Biometric re-auth
- Continue ENG-88 Rate-limit the export endpoint
- Land PR #128: Add biometric re-auth (review pending)
- Review PR #130: Refactor request logging
Blockers
- 🔴 PROJ-412 Biometric re-auth · flagged blocked: "Blocked on the vendor sandbox creds for PROJ-412. Waiting on infra to provision them before I can test the re-auth flow…"; awaiting review
Notice the GitHub commits, the GitHub PR, and the Jira move all collapsed under PROJ-412, and the blocker was lifted from a Slack message on its own. Nobody typed any of that.
(Running npx -y standup-mcp with no flag starts the MCP server on stdio, which is what an MCP client launches. Use --demo to see output in a plain terminal.)
What it does
Five tools. Every one defaults to the last working day, and Monday automatically reaches back across the weekend, so you rarely pass arguments.
| Tool | What you get |
|---|---|
standup_draft | Your standup: Yesterday / Today / Blockers, grouped by work item, in concrete deltas. The answer to "what should I say at standup?" |
blocker_scan | Everything blocking you, ranked by severity, fused from explicit "blocked / waiting on" language, PRs awaiting review, stalled in-progress tickets, and help requests. |
weekly_summary | A week of activity rolled into Shipped vs In progress, with reviews and totals. For 1:1s, weekly status, and self-reviews. |
activity_digest | A chronological "what actually happened" across all tools, newest first, grouped by day. |
list_sources | Which sources are wired, or that you are on demo data. |
What you can ask
You talk to it in plain language through your AI client:
- "What should I say at standup today?"
- "Give me Monday's standup covering the weekend."
- "What is blocking me right now?"
- "Summarize what I shipped this week for my 1:1."
- "What did I actually do yesterday?"
Principles it follows
- Only observed activity. It reports commits, PRs, ticket moves, and messages that exist. It never invents progress to fill a quiet day; a quiet day is reported as one.
- Grouped by work item, not by tool. Reviewers think in tickets, so the commit, the PR, the Jira move, and the Slack thread for PROJ-412 become one line, not four.
- Blockers from signals, not self-report. People forget to say they are stuck, so it infers it.
- A draft, not an auto-post. You get editable markdown to paste wherever your team already does standup (Slack, Geekbot, a doc, a ticket). It does not post on your behalf.
Example: blocker_scan
# Blockers
_since Tue Jun 16. Demo data._
1 blocker: 1 high, 0 medium, 0 low.
- 🔴 PROJ-412 Biometric re-auth (slack) · flagged blocked: "Blocked on the vendor sandbox creds for PROJ-412. Waiting on infra to provision them before I can test the re-auth flow…"; awaiting review
</details>
Example: weekly_summary
# Weekly summary: Jordan Lee
_the last 7 days. Demo data._
Shipped
- PROJ-407 Card dispute webhook
In progress
- PROJ-412 Biometric re-auth
- ENG-88 Rate-limit the export endpoint
Reviews and support
- Reviewed 1 PR for teammates
_3 work items touched, 1 PR merged, 5 commits._
</details>
Privacy
This is the part most tools gloss over. standup-mcp is built so that using it does not feel like installing surveillance on yourself:
- Local. It runs on your machine, inside your AI client. There is no standup-mcp server or account.
- Read-only. Every token it asks for is used only to read your activity. It never writes, posts, or moves anything.
- No AI key, no third party. It makes no LLM calls of its own. Your activity is sent only to the APIs of the tools you connect, and to your existing AI client's model. It is not sent to me or anyone else.
- It is yours, not your manager's. It generates your own update for you to review and edit, not a feed of your activity for someone else.
Connect your tools
Set any subset. Whatever you configure, it uses; with nothing set, it stays in demo mode. Restart the server after changing these.
| Variable | Source | Notes |
|---|---|---|
GITHUB_TOKEN | GitHub | Read-only PAT. Reads your commits, PRs, and reviews. |
JIRA_BASE_URL JIRA_EMAIL JIRA_API_TOKEN | Jira | Cloud site, account email, and an API token. Reads your ticket moves. |
LINEAR_API_KEY | Linear | A personal API key. Reads your issue state changes and comments. |
SLACK_TOKEN | Slack | A user token (xoxp) with search:read scans your own messages for blocker language. With a bot token instead, also set SLACK_CHANNELS (comma-separated channel ids) since bots cannot search. |
STANDUP_NAME | optional | Display name for the standup's owner. Without it, the GitHub handle is used. |
Verify your connections before wiring it into a client:
GITHUB_TOKEN=ghp_xxx LINEAR_API_KEY=lin_xxx npx -y standup-mcp --check
It prints, per source, the authenticated identity or a clear error.
Connect your AI client
standup-mcp speaks the Model Context Protocol, so any MCP-capable client can use it, whichever model is behind it: Claude Desktop, Claude Code, Cursor, Cline, Continue, Zed, Windsurf, and more. The server uses no AI API key of its own.
Claude Desktop
Add this to claude_desktop_config.json (Settings, Developer, Edit Config), then restart Claude Desktop:
{
"mcpServers": { "standup": { "command": "npx", "args": ["-y", "standup-mcp"], "env": { "GITHUB_TOKEN": "ghp_your_token", "JIRA_BASE_URL": "https://your-company.atlassian.net", "JIRA_EMAIL": "you@company.com", "JIRA_API_TOKEN": "your-jira-token", "LINEAR_API_KEY": "lin_api_your_key", "SLACK_TOKEN": "[PopNx MCP ตัดค่าที่หน้าตาเหมือนกุญแจออก]" } } } }
Leave the env block out entirely to run in demo mode first. Include only the sources you use.
Claude Code
claude mcp add standup \
-e GITHUB_TOKEN=ghp_your_token \ -e LINEAR_API_KEY=lin_api_your_key \ -- npx -y standup-mcp
Cursor, Cline, Continue, Zed, Windsurf, and others
These read the same mcpServers JSON as Claude Desktop, in the client's own MCP config. Use the block above. The server is identical; only the model driving the client differs.
How it works
The design goal is a clean seam between each tool and the standup logic.
- One activity model. GitHub commits, Jira moves, Linear state changes, and Slack messages all normalize to a single
ActivityEvent. Nothing downstream knows which tool a fact came from, which is exactly what lets it group by work item across tools. - One provider, many sources. Each source is an independent read-only client behind a common interface. The aggregator fans out to whichever are configured and tolerates any one failing, so a misconfigured Slack token never sinks your standup.
- Pure-function engine. Grouping, blocker detection, and the draft are pure functions over normalized events. They run identically on demo data and live data, and the tests run them directly.
- No model in the server. The server assembles a factual draft; your AI client phrases it. That is why it needs no AI key and why it can promise it never invents work.
src/
index.ts MCP server, stdio transport, --demo/--check/--help config.ts per-source env resolution, demo-mode detection window.ts the weekend-aware "since last standup" window provider.ts aggregator that fans out to configured sources types.ts ActivityEvent and the source/provider interfaces normalize.ts work-item key extraction, signal and noise detection sources/ github, jira, linear, slack clients, plus the demo provider analytics/ grouping, blockers, draft, weekly, digest (pure functions) tools/ one MCP tool per file, thin wrappers over analytics
What has been verified
- All five tools run end to end over real MCP stdio (
npm test). - The parse heuristics (work-item keys, blocker language, noise filters) are unit tested (
test/normalize.test.ts). - The engine is unit tested, including the Monday-covers-the-weekend window, work-item grouping, blocker severity, and the assembled draft (
test/draft.test.ts). - The whole engine is exercised against the demo dataset and reconciles across tools (
npm run smoke).
The demo dataset proves the engine. It does not prove each live client against every real account shape, which is why the parse layer is unit tested separately and each source is kept small and tolerant. Run --check to confirm your own connections, and if a response shape does not parse cleanly on your account, open an issue.
Roadmap
- A
team_standupview that rolls up several people for the PM running the meeting - Calendar sources (meetings as activity, so a meeting-heavy day reads honestly)
- GitLab and Bitbucket
- Cycle-time and "what changed since I last looked" digests
- OAuth flows in addition to tokens
Built by Sathvic Kollu
I run delivery for SaaS and fintech teams, and I build tools like this with Claude Code. If this saves you the daily standup chore, I would like to hear how you use it.
- Website: sathvickollu.com
- LinkedIn: linkedin.com/in/sathvic-kollu
Issues and pull requests are welcome.
License
MIT. See [LICENSE](LICEN