Log inSubmit server
Standup from your activity logo

Standup from your activity

Drafts standups from read-only GitHub, Jira, Linear, and Slack activity through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Standup from your activity

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "standup-from-your-activity": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE",
        "JIRA_BASE_URL": "YOUR_VALUE_HERE",
        "JIRA_EMAIL": "YOUR_VALUE_HERE",
        "JIRA_API_TOKEN": "YOUR_VALUE_HERE",
        "LINEAR_API_KEY": "YOUR_VALUE_HERE",
        "SLACK_TOKEN": "YOUR_VALUE_HERE",
        "SLACK_CHANNELS": "YOUR_VALUE_HERE",
        "STANDUP_NAME": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Standup from your activity MCP server turns recorded work from GitHub, Jira, Linear, and Slack into an editable daily standup draft. It runs locally over MCP, reads activity from configured APIs, groups related changes by work item, and identifies possible blockers. Reach for it when reconstructing yesterday's work, preparing a weekly update, or checking what may be blocking progress without posting anything automatically.

Use cases

  • Generate a daily standup from yesterday's activity
  • Find blockers across work and communication tools
  • Prepare a weekly update for a 1:1
  • Review a chronological activity digest

Key features

  • Groups activity by work item
  • Drafts Yesterday, Today, and Blockers sections
  • Scans for inferred blocker signals
  • Summarizes shipped and in-progress work
  • Runs locally in demo or connected mode
  • Provides read-only MCP tools

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · standup-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads148Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.

How Standup from your activity works

What Standup from your activity MCP server does

Standup from your activity MCP server creates status updates from activity already recorded in GitHub, Jira, Linear, and Slack. It combines related events around a work item instead of presenting separate lists for each service. For example, commits, a pull request, a ticket transition, and a related Slack message can appear together in one update.

The main output is an editable Markdown draft with Yesterday, Today, and Blockers sections. It is intended for review and copying into an existing team process; the server does not publish the result to Slack or update tickets.

How it works

The server runs locally as a standard Model Context Protocol process. An MCP client launches it over stdio, and the client’s model turns the returned activity into answers to questions such as what to say at standup or what happened yesterday. No separate AI API key is used by the server.

Five tools are available:

  • standup_draft prepares a grouped daily update.
  • blocker_scan ranks blocking signals, including explicit blocked or waiting language, pending reviews, stalled in-progress tickets, and requests for help.
  • weekly_summary separates shipped work from in-progress work and includes review and activity totals.
  • activity_digest presents activity chronologically by day.
  • list_sources reports configured sources or indicates that demo data is active.

Each tool defaults to the most recent working day. A Monday request includes the preceding weekend. The server uses observed commits, pull requests, reviews, ticket changes, comments, and messages rather than filling gaps with invented progress.

Setup and configuration

Install and launch it with npx -y standup-mcp. Running without credentials starts the MCP server in demo mode; adding --demo prints sample output in a terminal. Use --check to test configured connections and display either the authenticated identity or an error for each source. Restart the process after changing environment variables.

Configure only the services you need. GitHub uses GITHUB_TOKEN; Jira requires JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN; Linear uses LINEAR_API_KEY; and Slack uses SLACK_TOKEN. A Slack user token with search:read searches the user’s own messages for blocker language. A bot token also requires SLACK_CHANNELS, containing comma-separated channel IDs. STANDUP_NAME optionally sets the displayed owner name; otherwise the GitHub handle is used.

Limitations and notes

Standup from your activity is read-only. Tokens are used to read connected services, and the server does not write, post, or move records. Activity is sent to the APIs of the services you configure and to the model used by your existing MCP client; there is no hosted account or standup-mcp service described in the material.

The generated text is a draft, so review it before sharing. With no credentials, results come from the included synthetic dataset rather than personal activity. Slack coverage depends on the token type and its available search or channel access.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Standup from your activity

Standup from your activity is an MCP server that connects to GitHub, Jira, Linear, and Slack to read recorded work activity. Its main tools generate a standup draft, scan for blockers, summarize weekly work, provide a chronological activity digest, and list configured sources. It runs locally and is read-only.

Install it with `npx -y standup-mcp` and add that command to your MCP client configuration. Run it without credentials for demo mode, use `--demo` for terminal output, or configure source environment variables before starting the client.

Yes, it works with Cursor through the client’s MCP configuration. Add the same `mcpServers` JSON structure used for Claude Desktop, set the credentials for the sources you want to use, and launch `npx -y standup-mcp`.

It needs only the credentials for the sources you configure: a GitHub token, Jira site and account credentials, a Linear API key, or a Slack token. No credentials are needed for demo mode, and the server does not require its own AI API key.

No, it does not post or modify connected services. The tools return a standup draft or summaries for you to review and copy into Slack, a document, a ticket, or another team workflow.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewStandup from your activity AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/standup-from-your-activity?style=directory)](https://allmcps.com/mcp/standup-from-your-activity)
HTML Embed
<a href="https://allmcps.com/mcp/standup-from-your-activity"><img src="https://allmcps.com/api/badge/standup-from-your-activity?style=directory" alt="Standup from your activity on AllMCPs" /></a>