Listed from the MCP registry; nobody on Odel publishes it.
Write your standup in your AI agent, confirm it, and post a team digest to Slack or Google Chat
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y standcast
MCP client config
{
"mcpServers": {
"standcast": {
"command": "npx",
"args": [
"-y",
"standcast"
]
}
}
}Your team's daily standup, written with your AI agent and delivered to Slack or Google Chat.
Docs · Quick start · GitHub App
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 support@standcast.app.
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.
New here? The landing page has the overview and the beta request form. Agents can read llms.txt.
You need to own the GitHub organization (or personal account).
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.
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 |
Once a team writes dailies with AI, three problems show up:
Standcast keeps the writing where people already work, inside their agent, and takes care of collecting, consolidating and delivering.
/daily skill, an MCP server for Cursor, Codex, Claude Desktop and VS Code, and a plain CLI for the terminal.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.remind_at, people who have not sent their daily get one direct message, at most once a day, and never after the digest.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.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.sck_…), an OpenAPI reference, and signed outgoing webhooks such as daily.submitted and blocker.opened.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.
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.
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.Details: Privacy.
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.
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 .
.env.example.LINEAR_CLIENT_ID and LINEAR_CLIENT_SECRET are required on the api and the worker.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.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:
SUPPORT_EMAIL=you@example.com bun run docs:dev
SUPPORT_EMAIL=you@example.com bun run docs:build
bun run check-docs
dev and main.dev; dev merges into main when a release is ready.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.Contributions are welcome. Read CONTRIBUTING.md for commit conventions, releases, local setup and code style before opening a pull request.
standcast.yml validation as a GitHub check runOrange Labs supports Standcast. Financial support for the project goes through GitHub Sponsors.
Questions and problems: support@standcast.app.
MIT © 2026 Felipe Oliveira