explain_my_portfolio — Folionomiq MCP Prompt

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

by client

How to invoke explain_my_portfolio from your client

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

Folionomiq 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 25 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.