trace_story — masnavi MCP Prompt

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

by client

How to invoke trace_story from your client

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

Other prompts on this server

• explicate
• find_parallels

masnavi also offers 2 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.