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