work_done — MCPFax Agent Continuity MCP Tool
work_done
(work done) is one of 33 tools on the
MCPFax Agent Continuity
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call work_done from your client
- Claude Code MCPFax Agent Continuity work_done run in your project directory
- Claude Desktop MCPFax Agent Continuity work_done ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCPFax Agent Continuity work_done ~/.cursor/mcp.json
- VS Code MCPFax Agent Continuity work_done .vscode/mcp.json
- Zed MCPFax Agent Continuity work_done ~/.config/zed/settings.json
- Windsurf MCPFax Agent Continuity work_done ~/.codeium/windsurf/mcp_config.json
- Cline MCPFax Agent Continuity work_done ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCPFax Agent Continuity work_done ~/.gemini/settings.json
- Grok MCPFax Agent Continuity work_done .mcp.json (in your project root)
- ChatGPT MCPFax Agent Continuity work_done Settings → Connectors → Advanced → Developer mode
- Claude.ai MCPFax Agent Continuity work_done Settings → Connectors → Add custom connector
- LangChain MCPFax Agent Continuity work_done pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-continuity https://mcpfax-continuity.bowling-anthony.workers.dev/mcpOther tools on this server
- register
- whoami
- claim
- complete
- lease
- lease_renew
- lease_release
- resume_packet
- checkpoint_put
- checkpoint_get
- watermark_set
- watermark_get
- seen_add
- seen_check
- retry_state
- send
- inbox_schedule
- inbox_poll
- inbox_ack
- inbox_nack
- heartbeat
- budget_record
- budget_check
- barrier_create
- barrier_signal
- barrier_status
- work_push
- work_take
- work_fail
- work_status
- job_cancel
- should_continue
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.