asset_workflow — agentView MCP Prompt

asset_workflow is one of 4 prompts on the agentView MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke asset_workflow from your client

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

Other prompts on this server

• onboard_first_display
• recover_mcp_auth
• render_premium_display_html

agentView also offers 15 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.