set_checklist_status — Afterglow Checklists MCP Tool Mutating
set_checklist_status
(set checklist status) is one of 3 tools on the
Afterglow Checklists
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_checklist_status from your client
- Claude Code Afterglow Checklists set_checklist_status run in your project directory
- Claude Desktop Afterglow Checklists set_checklist_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Afterglow Checklists set_checklist_status ~/.cursor/mcp.json
- VS Code Afterglow Checklists set_checklist_status .vscode/mcp.json
- Zed Afterglow Checklists set_checklist_status ~/.config/zed/settings.json
- Windsurf Afterglow Checklists set_checklist_status ~/.codeium/windsurf/mcp_config.json
- Cline Afterglow Checklists set_checklist_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Afterglow Checklists set_checklist_status ~/.gemini/settings.json
- Grok Afterglow Checklists set_checklist_status .mcp.json (in your project root)
- ChatGPT Afterglow Checklists set_checklist_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Afterglow Checklists set_checklist_status Settings → Connectors → Add custom connector
- LangChain Afterglow Checklists set_checklist_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http afterglow-checklists https://afterglow-lime.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 1 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.