guest-result — Velox TriFit: Virtual Try-On API MCP Resource
guest-result
is one of 2 resources on the
Velox TriFit: Virtual Try-On API
MCP server. Connect the server and your client can attach it as context.
by client
How to attach guest-result from your client
- Claude Code Velox TriFit: Virtual Try-On API Resource/guest-result run in your project directory
- Claude Desktop Velox TriFit: Virtual Try-On API Resource/guest-result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Velox TriFit: Virtual Try-On API Resource/guest-result ~/.cursor/mcp.json
- VS Code Velox TriFit: Virtual Try-On API Resource/guest-result .vscode/mcp.json
- Zed Velox TriFit: Virtual Try-On API Resource/guest-result ~/.config/zed/settings.json
- Windsurf Velox TriFit: Virtual Try-On API Resource/guest-result ~/.codeium/windsurf/mcp_config.json
- Cline Velox TriFit: Virtual Try-On API Resource/guest-result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Velox TriFit: Virtual Try-On API Resource/guest-result ~/.gemini/settings.json
- Grok Velox TriFit: Virtual Try-On API Resource/guest-result .mcp.json (in your project root)
- ChatGPT Velox TriFit: Virtual Try-On API Resource/guest-result Settings → Connectors → Advanced → Developer mode
- Claude.ai Velox TriFit: Virtual Try-On API Resource/guest-result Settings → Connectors → Add custom connector
- LangChain Velox TriFit: Virtual Try-On API Resource/guest-result pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, 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 resource's type and contents.