daily_standup — timer tracking MCP Prompt

daily_standup is one of 2 prompts on the timer tracking MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke daily_standup from your client

• Claude Code timer tracking Prompt/daily_standup run in your project directory
• Claude Desktop timer tracking Prompt/daily_standup ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor timer tracking Prompt/daily_standup ~/.cursor/mcp.json
• VS Code timer tracking Prompt/daily_standup .vscode/mcp.json
• Zed timer tracking Prompt/daily_standup ~/.config/zed/settings.json
• Windsurf timer tracking Prompt/daily_standup ~/.codeium/windsurf/mcp_config.json
• Cline timer tracking Prompt/daily_standup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI timer tracking Prompt/daily_standup ~/.gemini/settings.json
• Grok timer tracking Prompt/daily_standup .mcp.json (in your project root)
• ChatGPT timer tracking Prompt/daily_standup Settings → Connectors → Advanced → Developer mode
• Claude.ai timer tracking Prompt/daily_standup Settings → Connectors → Add custom connector
• LangChain timer tracking Prompt/daily_standup pip install langchain-mcp-adapters

Other prompts on this server

• upgrade_to_pro

timer tracking also offers 2 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.