start_from_example — Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP Prompt

start_from_example is one of 3 prompts on the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke start_from_example from your client

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

Other prompts on this server

• migrate_framework_code
• diagnose_stack_trace

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) 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.