plan_week — task board todo kanban MCP Prompt

plan_week is one of 2 prompts on the task board todo kanban MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_week from your client

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

Other prompts on this server

• upgrade_to_pro

task board todo kanban 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 26 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.