bootstrap_plan_context — Symvanta MCP Prompt

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

by client

How to invoke bootstrap_plan_context from your client

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

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