A
licenseA
qualityD
maintenanceGenerates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.
5
42 npm
MIT
standup-mr
Server Details
Writes your daily standup from GitLab or GitHub merge request state: what's ready, blocked or waiting on your review, and why a pipeline is red, read from the failing job log. OAuth sign-in, no API keys; can post the note to Slack, Discord or Google Chat on a schedule.
Ownership verified
- Status
- Healthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Jubstaaa/standup-mr
- GitHub Stars
- 0
- Server Listing
- standup-mr
TDQS
Score is being calculated.
Available Tools
3 toolsget_note_instructionsGet note instructionsRead-onlyIdempotentInspect
Returns the note-writing rules — the playbook for turning get_standup_data output into a standup note a person would actually say out loud: how to group the previous day by theme, how to derive today from open merge requests, and how to report a blocker from its job log. Read-only, no arguments, no network. Call it once before writing the first note; the rules do not change between calls.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_standup_dataGet standup dataRead-onlyIdempotentInspect
Collect merge-request-based standup data from the GitLab or GitHub account the user linked to this connector. Returns one JSON object: today, previousDays[] with the events of each, todayEvents[], myMrs[] bucketed ready / blocked / draft / stale, reviews[] waiting on the user, and blockers[] carrying the error lines read out of each failed pipeline job log.
Call it once at the start of a working day, to write a standup note. It is a snapshot, not a search API: it cannot fetch one named merge request, reach further back than the previous working day, or filter by project.
Read-only. Credentials come from the accounts linked on the connect page, never from an argument. With one linked account no argument is needed; with several, pass provider or host — an ambiguous call fails and lists the linked accounts, so ask the user which one they mean. An expired login fails with a request to reconnect the connector.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Which linked account to read, by host, e.g. github.com or gitlab.example.com. Only needed when several accounts of the same provider are linked. | |
| lang | No | Language for the date labels inside the returned JSON: en (default) or tr. It relabels dates and nothing else — no field is translated, and the standup note itself is written by the caller, in whatever language they are speaking. | |
| provider | No | Which linked account to read, by provider. Only needed when both a GitHub and a GitLab account are linked. |
post_standup_notePost standup noteInspect
Posts a finished standup note to the chat webhook the user saved on the connect page (Slack, Discord or Google Chat). This one has a side effect: it sends a message other people will see, so only call it on a note the user has agreed to send. The webhook URL is never an argument. If none is saved, the call fails and says how to add one.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The note to post, as the chat should render it. Slack and Discord both take Markdown, so send the written note rather than the raw JSON from get_standup_data. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- First observed
get_note_instructions - First observed
get_standup_data - First observed
post_standup_note
Publisher details
- Operator
- İlker Balcılar · Publisher source
- Operator website
- https://github.com/Jubstaaa
- Vendor relationship
- Independent
- Trust center
- Not available
- Restrictions
- Free. GitHub org repositories need the standup-mr GitHub App installed on the org (or a fine-grained token). Self-hosted GitLab / GitHub Enterprise must be reachable from the public internet. · Publisher source
Related MCP Connectors
Task management for people and autonomous AI developers: tasks, stories, work logs, pull requests.
- mcpOAuthcom.attendmeet
Bring meeting decisions, tasks and user stories into your AI editor (Claude, Cursor, Copilot).
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
- DoneThatOAuthai.donethat
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
Related MCP Servers
- AlicenseAqualityCmaintenanceGenerates daily standup notes from your git commits across multiple repositories using AI.443 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables building a daily standup from real GitHub activity and spoken notes, exposing tools to fetch a voice-ready summary, capture tasks, bugs and blockers, list and complete items, and file deduplicated GitHub issues. Output is voice-first, returning a short spoken version alongside markdown for the screen.MIT
- FlicenseNot gradedqualityDmaintenanceSummarizes Slack activity and GitLab merge requests with OpenAI to help generate daily standups, weekly reports, or quarterly check-ins.-
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.