plan_departure — ViaFrei MCP Prompt
plan_departure
is one of 9 prompts on the
ViaFrei
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke plan_departure from your client
- Claude Code ViaFrei Prompt/plan_departure run in your project directory
- Claude Desktop ViaFrei Prompt/plan_departure ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ViaFrei Prompt/plan_departure ~/.cursor/mcp.json
- VS Code ViaFrei Prompt/plan_departure .vscode/mcp.json
- Zed ViaFrei Prompt/plan_departure ~/.config/zed/settings.json
- Windsurf ViaFrei Prompt/plan_departure ~/.codeium/windsurf/mcp_config.json
- Cline ViaFrei Prompt/plan_departure ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ViaFrei Prompt/plan_departure ~/.gemini/settings.json
- Grok ViaFrei Prompt/plan_departure .mcp.json (in your project root)
- ChatGPT ViaFrei Prompt/plan_departure Settings → Connectors → Advanced → Developer mode
- Claude.ai ViaFrei Prompt/plan_departure Settings → Connectors → Add custom connector
- LangChain ViaFrei Prompt/plan_departure pip install langchain-mcp-adapters
Other prompts on this server
ViaFrei 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 8 October 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.