Standup from your activity MCP server

by sathvic-kollu·io.github.sathvic-kollu/standup-mcp·v0.1.0

No reviews yet

Generate your daily standup from real GitHub, Jira, Linear, and Slack activity.

C69/100grade C

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

C69/100

full report

Adoption

New

0 stars37 downloads/wk

Reviews

Write one

Nobody has reviewed Standup from your activity yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Standup from your activity tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

activity_digest
A chronological digest of everything you did in a window across the configured tools, newest first, grouped by day. Use it to reconstruct what actually happened, separate from the opinionated standup framing.
blocker_scan
Surface what is blocking you across GitHub, Jira, Linear, and Slack, ranked by severity. Detects blockers from signals, not self-report: explicit 'blocked / waiting on / stuck' language, PRs awaiting review, in-progress tickets that have not moved, and requests for help.
list_sources
Show which activity sources (GitHub, Jira, Linear, Slack) are configured, or that the server is running on demo data. Does not hit the network; run the server with --check to verify live connections.
standup_draft
Generate your daily standup, what should I say at standup today, from your real activity across the configured tools (GitHub, Jira, Linear, Slack). Returns Yesterday / Today / Blockers grouped by work item, not by tool, in concrete deltas. Defaults to the last working day (Monday reaches back across the weekend). Only reports observed activity; never invents work.
weekly_summary
Roll up a week (or any N days) of your real activity into accomplishments, grouped by work item as Shipped vs In progress, with reviews and totals. For 1:1s, weekly status, and self-reviews. Only reports observed work.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan26 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 102 days ago8/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 69/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Standup from your activity compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 69/100; higher than 28% of 1,119 Developer tools servers
Tools: 5; the typical Developer tools server has 7
Tools that change things: 0%; typical: 5%. Fewer write tools means less an agent can break
Downloads a week: 37; more than 23% of 436 Developer tools servers with a package

What its tools let an agent do: 5 read

Install Standup from your activity in Claude Code, Cursor or VS Code

Runs npx -y standup-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add standup-mcp -- npx -y standup-mcp

Add to Cursor

What the publisher says

From the Standup from your activity repository's README, as published. We do not edit it. Read it on GitHub

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.

What you can ask

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Standup from your activity: common questions

Is Standup from your activity MCP server safe?: With care: it is graded C, so read the findings first (69/100). Read the Standup from your activity safety report
How do I install Standup from your activity?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Standup from your activity need an API key?: Yes. The registry entry asks for GITHUB_TOKEN, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN.
Is Standup from your activity maintained?: The last commit was 140 days ago (2026-06-17). The latest release is v0.1.0.
What can I use instead of Standup from your activity?: Servers from other publishers that do the same job: GitDiagram MCP server, GitHub MCP server and Gk CLI MCP server.
How does Standup from your activity compare with other Developer tools MCP servers?: safety score 69/100 (higher than 28% of 1,119 Developer tools servers); tools 5 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Standup from your activity

Same job from other publishers: the closest match first, then the best rated.

GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
not reviewed
Established
A
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
not reviewed
Established
A
Gk CLI
The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
not reviewed
Established
B
Agent Harnesses
Agent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.
not reviewed
Established
A
Atlassian Dc Jira
MCP server for Atlassian Jira Data Center - search, view, and create issues
not reviewed
Established
B

Run it through the gateway

Local package. It runs on your machine, not through the gateway.

Rating: —
Safety grade: C · 69/100
Stars: 0
Downloads/wk: 37
Price: Free
Licence: MIT
Transport: Local · npm
Version: 0.1.0
Category: Developer tools
Last release: 2026-06-17

Credentials it needs

GITHUB_TOKENsecretGitHub read-only personal access token. Enables commits, PRs, and reviews. Leave all sources unset to use the built-in demo data.
JIRA_BASE_URLYour Jira Cloud site, e.g. https://your-company.atlassian.net.
JIRA_EMAILAtlassian account email the API token belongs to.
JIRA_API_TOKENsecretJira API token from id.atlassian.com. Read-only use.
LINEAR_API_KEYsecretLinear personal API key (read-only). Enables issue state changes and comments.
SLACK_TOKENsecretSlack token with read scopes. Enables scanning your own messages for blocker language.
SLACK_CHANNELSOptional comma-separated channel ids to scan when message search is unavailable.
STANDUP_NAMEOptional display name for the standup's owner.
STANDUP_DEMO_MODESet to true to force the demo dataset even when credentials are present.

Own this server?

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Claim listing

Badge for your README

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/sathvic-kollu-standup-mcp.svg)](https://mcp.market/server/sathvic-kollu-standup-mcp)

How the badge works