MCP Server

Connect your AI coding tools to DailyStandup and let them log activity in real time. Every commit, blocker, and question is captured automatically — no copy-pasting into standup forms.

Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.

Get connected

Choose your AI coding tool and follow the steps to connect to DailyStandup.

The fastest way to get started. Your token is stored locally and never touches the repo.

Run this in your terminal (not inside Claude Code):

claude mcp add --transport http dailystandup https://mcp.dailystandup.io/mcp \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --scope local

Replace YOUR_API_KEY with the token from Settings → Integrations → AI Activity Log.

Restart Claude Code, then verify with /mcp. You should see dailystandup: connected.

Tip: This stores the config in ~/.claude.json — your token never enters version control.

Set up automatic logging

After connecting, Claude Code has access to DailyStandup tools — but it won't call them automatically unless instructed. Choose a method below.

Add this to your project's CLAUDE.md:

## DailyStandup
After completing any task (feature, bugfix, refactor, review), call the
DailyStandup `log_progress` tool with a one-line summary of what was done.
Include the scope (e.g. file or component name) and the outcome.

If you encounter a blocker that prevents progress, call `report_blocker`
with a description of what is blocked and why.

If you need input from the team (design review, architecture decision,
clarification), call `ask_question`.

When linking to a PR, issue, or commit, use `link_item` with the URL.

When resolving a previously reported blocker, call `resolve_blocker`.

Do this automatically — do not ask for permission to log. Keep summaries
concise (under 20 words).

This is the “set and forget” approach — every task, every branch, every session produces activity events automatically.

Method	Frequency	Best for
CLAUDE.md rule	Every task, automatic	Teams wanting comprehensive passive logging
`/log` command	End of session, manual	Developers wanting control over what gets logged
Existing commands	Every commit/PR	Teams already using `/done` or `/ship`

All three methods can be combined.

Available tools

Tool	Description	Required params
`log_progress`	Log a progress update to activity feed	`title`
`report_blocker`	Report a blocker preventing progress	`title`
`ask_question`	Log a question for the team	`title`
`link_item`	Link an external item (PR, issue, commit)	`title`, `external_url`
`resolve_blocker`	Mark a blocker as resolved	`title`
`get_today_log`	Get all activity events for a date	none (date optional)
`get_standup_draft`	Get or generate standup draft from events	none (date optional)

See it in action

Once connected, your AI coding tool calls DailyStandup tools naturally:

> Refactored the auth middleware to support both transports

✓ Logged progress: "Refactored auth middleware for dual transport support"

> I'm blocked — DevOps hasn't provisioned the staging environment and it's been 3 days

✓ Reported blocker: "Staging env not provisioned by DevOps — 3 days outstanding"

> Just opened a PR for the activity log UI, link it

✓ Linked PR: "Activity Log UI" → github.com/org/repo/pull/68

Events appear in your Activity Log and automatically feed into your next standup draft.