standcast

mcp
Guvenlik Denetimi
Uyari
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Open source daily standup tool for software teams: write your standup in your AI agent (Claude Code, Cursor, any MCP client) from your GitHub and Linear activity, confirm it, and post one team digest to Slack or Google Chat.

README.md

Standcast: the daily standup, written in your AI agent

Your team's daily standup, written with your AI agent and delivered to Slack or Google Chat.

Docs · Quick start · GitHub App

CI Latest release npm Status: public beta License: MIT

Standcast was previously called Standwise.


[!WARNING]
Public beta. Standcast is being tested with its first teams. Expect rough edges and changes to behaviour, configuration and the API before 1.0. Report problems in GitHub issues or at [email protected].

Each person runs /daily in their AI agent (Claude Code, Cursor, Codex, Claude Desktop, VS Code). Standcast drafts the daily from what they did on GitHub; the person edits it, adds today's plan and blockers, and confirms before anything is sent. At the time set in standcast.yml, Standcast posts one digest per team to Slack or Google Chat.

It is built for teams, not for watching people: no productivity metrics, no rankings, nothing sent on anyone's behalf.

Table of contents

Quick start

New here? The landing page has the overview and the beta request form. Agents can read llms.txt.

For admins

You need to own the GitHub organization (or personal account).

  1. Install the Standcast GitHub App on your organization.
  2. GitHub sends you to https://app.standcast.app/setup. Sign in. If your teams post to Slack, click Connect Slack. If they post to Google Chat, add the Standcast app to a space and paste the code it posts in the Google Chat step (guide).
  3. Create standcast.yml at the root of your private .github-private repository (or of .github), from the template on the setup page.

Step by step: Install.

For members

Install the CLI and sign in. On macOS and Linux:

curl -fsSL https://standcast.app/install.sh | sh
standcast login

The script downloads the latest release for your system, checks it against SHA256SUMS and installs it to ~/.local/bin/standcast.

On macOS, Linux and Windows with Node.js 18 or later, install it from npm instead. npm installs the same binary, only the one for your system:

npm install -g standcast
standcast login

The binaries are also on the releases page.

Then pick how you write your daily:

Client Setup
Claude Code /plugin marketplace add ImFelipeOliveira/standcast, then /plugin install standcast@standcast, then run /daily
Cursor, Codex, Claude Desktop, VS Code Add the MCP server (standcast mcp, or npx -y standcast mcp without installing the CLI): MCP guide
Terminal standcast draft and standcast submit: CLI reference

Why Standcast

Once a team writes dailies with AI, three problems show up:

  • Loose dailies. Every message comes in a different format, in a different place.
  • No consolidated view. The manager reads scattered messages and has no single picture of the team.
  • Nobody orchestrates. No one tracks who sent the daily, and blockers sit until someone notices.

Standcast keeps the writing where people already work, inside their agent, and takes care of collecting, consolidating and delivering.

Features

  • Draft from GitHub activity. Pull requests opened, merged and reviewed, plus commits grouped by repository, since your last daily. Monday covers the weekend.
  • Works in any MCP client. A Claude Code plugin with the /daily skill, an MCP server for Cursor, Codex, Claude Desktop and VS Code, and a plain CLI for the terminal.
  • One digest per team. Posted to Slack or Google Chat at digest_at, in the team's time zone and only on workdays, with blockers first and the people who did not send listed at the end.
  • Late dailies. Sent after the digest, they are posted as a reply in the digest thread.
  • Reminders. At remind_at, people who have not sent their daily get one direct message, at most once a day, and never after the digest.
  • Blocker routing. A new blocker goes by direct message to whoever can help: the pull request's reviewers, then its CODEOWNERS, then the team managers.
  • Slack or Google Chat. Each team picks its chat in standcast.yml. On Google Chat, add the Standcast app to a space and link it with the code it posts; people link themselves by sending the app a direct message.
  • Linear cards. Connect one Linear workspace (read-only) and your own cards that started or finished appear in your draft. A blocker that links a card goes to the people who own the blocking card.
  • Suggested blockers, only for you. A pull request waiting too long for review, CI failing for a day or a card in progress for days shows up in your own draft. You confirm or ignore it; nobody else ever sees it.
  • Several teams, one daily. People in two teams write once and appear in both digests.
  • Configuration as code. A single standcast.yml in your private .github-private repository (or in .github). Every push and pull request that changes standcast.yml is validated by a Standcast config check run with the error on the right line, and an invalid push never breaks anything: the last valid version stays in effect.
  • Manager tools. Managers read their team's dailies, digests and blockers from their own AI agent.
  • Read-only API and webhooks. API keys (sck_…), an OpenAPI reference, and signed outgoing webhooks such as daily.submitted and blocker.opened.
  • Bilingual. English and Brazilian Portuguese across the CLI, chat messages, web pages and documentation.

How it works

flowchart LR
    subgraph Member["Each member"]
        A["AI agent<br/>/daily · MCP · CLI"]
    end
    subgraph SW["Standcast"]
        API["API"]
        W["Worker"]
        DB[("Postgres")]
    end
    GH["GitHub<br/>activity · standcast.yml"]
    SL["Slack or Google Chat<br/>team channel or space"]

    A -- "1. draft" --> API
    API -- "reads activity" --> GH
    A -- "2. confirmed daily" --> API
    API --> DB
    W -- "3. digest at digest_at" --> SL
    DB --> W

A day with remind_at: "09:30" and digest_at: "10:00":

Time What happens
08:50 Alice runs /daily. Her agent fetches a draft of yesterday's GitHub work; she edits it, writes today and one blocker, and confirms. Her blocker links a pull request, so its reviewer gets a direct message.
09:30 Bob has not sent yet, so he gets a reminder.
10:00 Standcast posts the team digest to #daily-backend: blockers first, then each person's yesterday and today, then who did not send.
10:40 Bob sends a late daily. It is posted as a reply in the digest thread.

The full walkthrough is in How it works.

Configuration

All configuration lives in standcast.yml at the root of the .github-private repository or, when that one has no file, of the .github repository, on the default branch. Keep it in a private repository: it names the people of your teams. A minimal file:

teams:
  - name: backend
    timezone: America/Sao_Paulo
    remind_at: "09:30"
    digest_at: "10:00"
    managers: [alice]
    members: [alice, bob]
    chat:
      provider: slack
      channel: "#daily-backend"

Every key is documented in the configuration reference.

Privacy principles

  • Your code is never read. Standcast reads standcast.yml, team and organization membership, and the titles, links and dates of your own pull requests, reviews and commits. If you connect Linear, it also reads card titles, links, states and dates, never descriptions or comments.
  • Nothing is sent without your confirmation.
  • No rankings, scores or productivity metrics, in any plan, ever.
  • No AI model processes your data on the Standcast servers. The writing happens in your own agent.
  • Secrets are encrypted at rest with AES-256-GCM.

Details: Privacy.

Architecture

A Bun + TypeScript monorepo. Business rules live in use cases; HTTP routes, jobs, the CLI and the MCP server are thin layers on top of them.

apps/
├── api/            Hono HTTP API, OAuth, GitHub, Slack and Google Chat webhooks, /reference
├── worker/         pg-boss jobs: tick, digests, late dailies, webhook delivery
└── cli/            standcast CLI and MCP server (compiled to a single binary)
packages/
├── core/           pure domain: config, calendar, digest builders, i18n
├── orchestrator/   use cases: drafts, submissions, digests, org reads
├── db/             Drizzle schema, migrations and repositories (Postgres)
├── queue/          job queue port and pg-boss implementation
├── plugin/         Claude Code plugin with the /daily skill
└── adapters/
    ├── github/     GitHub App: activity, config, teams, OAuth
    ├── slack/      Slack: OAuth, digests, threads, direct messages
    └── google-chat/ Google Chat: app events, digests, threads, direct messages
docs/
├── site/           VitePress documentation (en and pt-BR), hosted on Cloudflare Pages
└── api/            OpenAPI guides and changelog

Dependency direction: apps → orchestrator → core, with db, queue and the adapters behind ports so use cases are tested without HTTP, Slack or GitHub.

Self-hosting

Standcast ships as one Docker image containing the api and the worker. APP (api or worker) selects the default command. The documentation site is not part of the image: it is a static site on Cloudflare Pages, see docs/cloudflare-pages.md.

docker build --build-arg APP=api -t standcast-api .
docker build --build-arg APP=worker -t standcast-worker .
  • The api runs the migrations on startup, so run a single api replica. Both services need Postgres.
  • Every variable is listed in .env.example.
  • Register the apps with docs/github-app.md (or the manifest), docs/slack-app-manifest.yml and docs/linear-app.md. LINEAR_CLIENT_ID and LINEAR_CLIENT_SECRET are required on the api and the worker.
  • Google Chat is optional: create the Chat app with docs/google-chat-app.md, then set GOOGLE_CHAT_SERVICE_ACCOUNT (the base64 of the service account JSON key) on the api and the worker, and GOOGLE_CHAT_PROJECT_NUMBER (the Google Cloud project number, api only, required with the key). The Chat app authentication audience must be Project number. Without the key, Google Chat is off.

Development

bun install
bun test                    # starts one disposable Postgres for the full suite
bun run lint                # Biome, CI-enforced
bun run typecheck           # tsc, CI-enforced

Tests require Docker, but no database setup: Testcontainers starts PostgreSQL 17 once, shares it across the whole run and removes it after the last test. Set TEST_DATABASE_URL to reuse an existing database instead. To run the api or worker locally, copy .env.example to .env and run docker compose up -d.

Documentation site, served at the root of its own domain (https://docs.standcast.app). STANDCAST_PUBLIC_URL sets the api address shown in the examples and the API reference link:

[email protected] bun run docs:dev
[email protected] bun run docs:build
bun run check-docs

Release automation

  • CI (lint, typecheck, tests against Postgres, docs build) runs on every pull request and on pushes to dev and main.
  • Feature branches merge into dev; dev merges into main when a release is ready.
  • release-please keeps a release PR open on main from Conventional Commits. Merging it tags the release, uploads the CLI binaries and SHA256SUMS, publishes the CLI to npm as standcast and updates its MCP Registry entry, io.github.ImFelipeOliveira/standcast.

Contributing

Contributions are welcome. Read CONTRIBUTING.md for commit conventions, releases, local setup and code style before opening a pull request.

Roadmap

  • Drafts from GitHub activity, through the skill, the MCP server and the CLI
  • Team digest and late dailies in Slack
  • Manager tools, read-only API and outgoing webhooks
  • Reminder for people who have not sent their daily
  • Blocker routing to reviewers, CODEOWNERS or managers
  • Suggested blockers (pull request without review, failing CI), visible only to you
  • standcast.yml validation as a GitHub check run
  • Linear integration: cards in the draft, card blocker routing and stale card suggestions
  • Google Chat: digests, threads and direct messages through the Standcast app
  • Jira, then ClickUp, Asana and GitHub Projects
  • Microsoft Teams and Discord

Sponsors

Orange Labs supports Standcast. Financial support for the project goes through GitHub Sponsors.

Support

Questions and problems: [email protected].

License

MIT © 2026 Felipe Oliveira

Yorumlar (0)

Sonuc bulunamadi