search_products — FrankoX MCP Tool Read-only
search_products
(search products) is one of 22 tools on the
FrankoX
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_products from your client
- Claude Code FrankoX search_products run in your project directory
- Claude Desktop FrankoX search_products ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FrankoX search_products ~/.cursor/mcp.json
- VS Code FrankoX search_products .vscode/mcp.json
- Zed FrankoX search_products ~/.config/zed/settings.json
- Windsurf FrankoX search_products ~/.codeium/windsurf/mcp_config.json
- Cline FrankoX search_products ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FrankoX search_products ~/.gemini/settings.json
- Grok FrankoX search_products .mcp.json (in your project root)
- ChatGPT FrankoX search_products Settings → Connectors → Advanced → Developer mode
- Claude.ai FrankoX search_products Settings → Connectors → Add custom connector
- LangChain FrankoX search_products pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trade-intelligence https://frankox.com/mcp
Other tools on this server
- search_manufacturers
- search_suppliers
- search_opportunities
- get_public_company_profile
- get_public_product_profile
- register_manufacturer_interest
- create_manufacturer_draft
- update_manufacturer_draft
- request_opportunity_match
- create_agent_conversation
- get_agent_conversation
- list_agent_conversations
- reply_to_agent_conversation
- list_network_intents
- discover_network_intents
- initiate_network_request
- list_network_requests
- get_network_request
- respond_to_network_request
- external_business_handshake
- get_external_agent_entrypoint
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.