identifyDevice — FitsThis MCP Tool
identifyDevice
(identify device) is one of 23 tools on the
FitsThis
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call identifyDevice from your client
- Claude Code FitsThis identifyDevice run in your project directory
- Claude Desktop FitsThis identifyDevice ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FitsThis identifyDevice ~/.cursor/mcp.json
- VS Code FitsThis identifyDevice .vscode/mcp.json
- Zed FitsThis identifyDevice ~/.config/zed/settings.json
- Windsurf FitsThis identifyDevice ~/.codeium/windsurf/mcp_config.json
- Cline FitsThis identifyDevice ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FitsThis identifyDevice ~/.gemini/settings.json
- Grok FitsThis identifyDevice .mcp.json (in your project root)
- ChatGPT FitsThis identifyDevice Settings → Connectors → Advanced → Developer mode
- Claude.ai FitsThis identifyDevice Settings → Connectors → Add custom connector
- LangChain FitsThis identifyDevice pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http shop https://fitsthis.com/mcpOther tools on this server
- findCompatibleParts
- searchProducts
- getProduct
- getReviews
- quickCheckout
- createCheckout
- getOrderStatus
- submitReview
- createSupportTicket
- adminListOrders
- adminGetOrder
- adminListTickets
- adminGetTicket
- adminReplyTicket
- adminSetTicketStatus
- adminGetStats
- adminListDemand
- adminGetSupplierContext
- adminRefreshAeOrder
- adminRefreshTracking
- adminRetryFulfill
- adminRetryAfterpay
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.