get_try_on_result — WORN Fit MCP Tool Read-only
get_try_on_result
(get try on result) is one of 4 tools on the
WORN Fit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_try_on_result from your client
- Claude Code WORN Fit get_try_on_result run in your project directory
- Claude Desktop WORN Fit get_try_on_result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WORN Fit get_try_on_result ~/.cursor/mcp.json
- VS Code WORN Fit get_try_on_result .vscode/mcp.json
- Zed WORN Fit get_try_on_result ~/.config/zed/settings.json
- Windsurf WORN Fit get_try_on_result ~/.codeium/windsurf/mcp_config.json
- Cline WORN Fit get_try_on_result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WORN Fit get_try_on_result ~/.gemini/settings.json
- Grok WORN Fit get_try_on_result .mcp.json (in your project root)
- ChatGPT WORN Fit get_try_on_result Settings → Connectors → Advanced → Developer mode
- Claude.ai WORN Fit get_try_on_result Settings → Connectors → Add custom connector
- LangChain WORN Fit get_try_on_result pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http worn-fit https://worn.club/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.