notify_when_done — kweenkl mcp MCP Prompt

notify_when_done is one of 3 prompts on the kweenkl mcp MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke notify_when_done from your client

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

Other prompts on this server

• send_notification
• alert_on_error

kweenkl mcp 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.