plan_schedule — Rhylthyme MCP Prompt

plan_schedule is one of 1 prompt on the Rhylthyme MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_schedule from your client

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

Rhylthyme also offers 10 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.