MCP SERVERWrite your standup from what you actually did: local git commits and GitHub activity, turned into an update you can paste.
LABSCO SUMMARY
Instead of remembering what you did, it reads the commits and the pull requests and hands back the update in the format you were going to write by hand anyway.
A reader of your own work history. It walks local git repositories over a time range and, with a token, adds GitHub pull requests, reviews and issue comments — then formats the lot into a standup or a weekly report.
Node.js and git, which is already on the machine. Local commits need no key; the GitHub side needs GITHUB_TOKEN and GITHUB_USERNAME in the environment.
One command — npx -y github:jabbawocky/standupcraft
USE CASES
Commits from the last day become a formatted update, with your blockers and today's plan added as arguments rather than reconstructed.
Seven days of commits and pull requests become a client-facing progress note, in a tone meant for someone who does not read diffs.
It reads more than one repository over the range you name, which is the case where memory fails first.
The source list shows which repositories were detected and whether the GitHub token is in place — worth reading before trusting an update that looks thin.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
generate_standupSynthesize git commit history (and optionally GitHub activity) into a formatted daily standup update. Pass the raw output from get_git_activity (and optionally get_github_activity) and this tool formats it into a clean, ready-to-paste standup.
generate_weekly_summaryGenerate a weekly engineering summary or freelancer client progress report from git and GitHub activity. Pass raw output from get_git_activity (with days=7) to produce a summary suitable for client reports, invoices, or team updates.
get_git_activityRead local git commit history across one or more repos for a time range. Returns structured commits with message, timestamp, files changed, and line stats. No API key required — reads local .git history only.
get_github_activityFetch PRs opened, merged, reviewed, and issues commented on GitHub in the last N days. Requires GITHUB_TOKEN env var with read:repo scope. Gracefully returns empty result if no token is configured.
list_configured_sourcesShow which activity sources are configured and ready to use. Checks for GITHUB_TOKEN, GITHUB_USERNAME, and local git repos. Use this to understand what data get_git_activity and get_github_activity will return.
BEFORE YOU INSTALL
5 tools when we connected. get_github_activity needs GITHUB_TOKEN; the other four work with no configuration. Nothing writes.
npx on PATH
All 3 documented setups run the server on your machine.
CONTEXT COST
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y github:jabbawocky/standupcraft{
"mcpServers": {
"standupcraft": {
"command": "npx",
"args": [
"-y",
"github:jabbawocky/standupcraft"
]
}
}
}claude mcp add standupcraft npx -- -y github:jabbawocky/standupcraft{
"mcpServers": {
"standupcraft": {
"command": "npx",
"args": [
"-y",
"github:jabbawocky/standupcraft"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>",
"GITHUB_USERNAME": "<YOUR_GITHUB_USERNAME>"
}
}
}
}MCP servers
MrOrz
lostintangent
kurdin
nickbaumann98