run_the_checklist — checklist MCP Prompt

run_the_checklist is one of 2 prompts on the checklist MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke run_the_checklist from your client

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

Other prompts on this server

• upgrade_to_pro

checklist 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.