plan_a_night — Dim Hour MCP Prompt

plan_a_night is one of 3 prompts on the Dim Hour MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_a_night from your client

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

Other prompts on this server

• find_dinner
• whats_new

Dim Hour also offers 1 resource — 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.