mark_work_done — Milestone MCP Tool
mark_work_done
(mark work done) is one of 15 tools on the
Milestone
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mark_work_done from your client
- Claude Code Milestone mark_work_done run in your project directory
- Claude Desktop Milestone mark_work_done ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Milestone mark_work_done ~/.cursor/mcp.json
- VS Code Milestone mark_work_done .vscode/mcp.json
- Zed Milestone mark_work_done ~/.config/zed/settings.json
- Windsurf Milestone mark_work_done ~/.codeium/windsurf/mcp_config.json
- Cline Milestone mark_work_done ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Milestone mark_work_done ~/.gemini/settings.json
- Grok Milestone mark_work_done .mcp.json (in your project root)
- ChatGPT Milestone mark_work_done Settings → Connectors → Advanced → Developer mode
- Claude.ai Milestone mark_work_done Settings → Connectors → Add custom connector
- LangChain Milestone mark_work_done pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http milestone https://milestone-continuity2.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.