new_scheduling_proposal — Chronary MCP Prompt

new_scheduling_proposal is one of 4 prompts on the Chronary MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke new_scheduling_proposal from your client

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

Other prompts on this server

• schedule_event
• find_meeting_time
• daily_agenda

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