daily_standup — time tracking billing hours MCP Prompt
daily_standup
is one of 2 prompts on the
time tracking billing hours
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 time tracking billing hours Prompt/daily_standup run in your project directory
- Claude Desktop time tracking billing hours Prompt/daily_standup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor time tracking billing hours Prompt/daily_standup ~/.cursor/mcp.json
- VS Code time tracking billing hours Prompt/daily_standup .vscode/mcp.json
- Zed time tracking billing hours Prompt/daily_standup ~/.config/zed/settings.json
- Windsurf time tracking billing hours Prompt/daily_standup ~/.codeium/windsurf/mcp_config.json
- Cline time tracking billing hours Prompt/daily_standup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI time tracking billing hours Prompt/daily_standup ~/.gemini/settings.json
- Grok time tracking billing hours Prompt/daily_standup .mcp.json (in your project root)
- ChatGPT time tracking billing hours Prompt/daily_standup Settings → Connectors → Advanced → Developer mode
- Claude.ai time tracking billing hours Prompt/daily_standup Settings → Connectors → Add custom connector
- LangChain time tracking billing hours Prompt/daily_standup pip install langchain-mcp-adapters
Other prompts on this server
time tracking billing hours 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 26 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.