Standup Mr

standup-mr

Standup notes from merge request state, not commit logs.

Most standup tools read your local git log. That answers "what did I type", which is not what anyone asks in a standup. This one reads GitLab or GitHub: what is ready to merge, what is blocked, what is waiting on you — and when a pipeline is red, it opens the job log and tells you why.

What makes it different

Use

npx standup-mr fetch                            # JSON, provider auto-detected

npx standup-mr fetch --provider github # GitHub npx standup-mr fetch --provider gitlab # GitLab npx standup-mr fetch --markdown # structured digest npx standup-mr fetch --lang tr # Turkish date labels

npx standup-mr fetch --markdown | npx standup-mr post --google-chat "$URL"

Identity

GitHub defaults to github.com when no host is given. GitLab has no default — self-hosted is the norm there, so a host must come from a flag, env var, or glab's own config.

The provider itself is picked in this order:

1. --provider github / --provider gitlab, if passed
2. a recognizable --host (github.com, gitlab.com, or a hostname containing github/gitlab)
3. STANDUP_PROVIDER, or whichever of the GITHUB_* / GITLAB_* env pairs is set
4. whichever of gh / glab is logged in

If none of these resolve — or both do, ambiguously — the command fails with a clear error instead of guessing.

So if you already use gh or glab, there is nothing to configure.

Post it to chat

npx standup-mr fetch --markdown | npx standup-mr post --slack "$SLACK_WEBHOOK_URL"

Hosted connector: any AI assistant

No token, no config file — sign in instead. The hosted server speaks the standard MCP OAuth flow, so any assistant that supports remote MCP servers can use it: add the URL, and a browser page opens where you sign in.

https://standup.ilkerbalcilar.com/mcp

claude.ai and Claude Code are tested end to end; the others use the same standard flow. If one of them doesn't sign in, please open an issue.

On the sign-in page you link the accounts the note should read:

• GitHub — sign in through the standup-mr GitHub App. It only sees the repositories it is installed on, so install it on your org too; if the org won't approve it, add github.com with a fine-grained token instead.
• gitlab.com — sign in with GitLab.
• Your company's GitLab or GitHub Enterprise — type the host. If someone at your company already set up sign-in, you get a "Sign in with …" button. Otherwise set it up once: the page shows the exact redirect URI and scopes for an OAuth application on your host, you paste its ID and secret, and everyone at that host can sign in from then on. A read-only token works too.
• Chat webhook _(optional)_ — Slack, Discord or Google Chat, so your assistant can post the finished note when you ask it to.

Link as many as you like — say, GitHub for side projects and your company's GitLab for work — then ask for "my standup" or "my work standup". With several accounts linked, the assistant asks which one you mean.

Added in an assistant with a mobile app — Claude or ChatGPT — it works from your phone too: ask for your standup on the way to the meeting.

What is stored. Your provider tokens and webhook URL, encrypted with AES-256-GCM, and only to read your merge requests and post your note. The access tokens your assistant holds are stored as hashes. Disconnecting it deletes everything; connections unused for 30 days are deleted. The server is the code in remote/.

When to use the local server instead. A GitLab behind a VPN or on a private network is out of reach of a hosted server. Run the stdio server below on your own machine — the token never leaves it.

The four surfaces

CLI — the core. Emits JSON; zero runtime dependencies.

MCP server (mcp/) — three tools for Claude Desktop, Claude Code, Cursor, or any MCP client that runs a local process. See mcp/README.md.

Remote MCP server (remote/) — the same tools over HTTPS with sign-in, for any assistant that supports remote MCP servers, including the web and mobile apps. See above.

Claude Code plugin — the note-writing playbook, shipped as the standup skill. From inside Claude Code:

/plugin marketplace add Jubstaaa/standup-mr

/plugin install standup@standup-mr

Then type /standup. Updates come with /plugin marketplace update standup-mr.

Using it from Cursor, Codex, or another assistant

If you're not using Claude Code, wire up the MCP server for live data and paste in the note-writing rules separately.

Cursor — add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-local):

{

"mcpServers": { "standup": { "command": "npx", "args": ["-y", "standup-mr", "mcp"], "env": { "GITHUB_TOKEN": "ghp_..." } } } }

Codex — add to ~/.codex/config.toml:

[mcp_servers.standup]

command = "npx" args = ["-y", "standup-mr", "mcp"]

[mcp_servers.standup.env] GITHUB_TOKEN = "ghp_..."

The exact config key and file path are version-dependent for both clients — if a snippet above doesn't work, check Cursor's MCP docs or Codex's own config documentation for the current format rather than trusting this file blindly.

The server exposes three tools:

post_standup_note reads the webhook URL from STANDUP_WEBHOOK_URL and never takes it as an argument — anyone holding that URL can post to the channel, so it belongs with the tokens, not in a transcript. The payload shape is inferred from the URL host; kind is only needed when a proxy hides it.

Three shapes are implemented: slack and google-chat both post {"text"}, discord posts {"content"}.

Slack and Google Chat do not render standard Markdown, so the note is rewritten on the way out: **bold** becomes *bold* and a ## heading becomes a bold line. Inline code, fenced blocks and their contents are left alone. Discord speaks Markdown natively and is sent untouched. Anything else that accepts a Slack-shaped body — Mattermost, Rocket.Chat, an n8n or Zapier endpoint — works today by passing kind: "slack", or --slack URL on the CLI.

Outside MCP, the same rules are available on stdout:

npx standup-mr instructions >> AGENTS.md

--markdown is a digest, not a written note

--markdown organizes the raw material into readable sections. It does not group events into themes or diagnose blockers — that is the model's work, and it lives in the MCP client's prompt or in the Claude Code skill.

• Without AI: a structured digest.
• With AI: a note you can read out.

What the digest looks like

Anonymised output from a real Monday run — note that Friday and Saturday each get their own section, and that a merge request GitLab has not evaluated is not called ready:

# Monday, 31 August — dev

_Structured digest — not a written note._

Previous working day: Friday, 28 August

• acme/ui pushed to — fix(keyboard): scale keys to viewport (4 commits)
• acme/ui accepted — chor