MCP server
Instead of logging into TradeIndia, downloading a CSV, and manually reviewing leads, you ask Claude: "Get my TradeIndia leads from the last 2 days." Claude calls this MCP server and returns every inquiry — buyer name, company, mobile number, message, product interest, city, and state — parsed and readable in seconds.
get_tradeindia_inquiries
Fetches TradeIndia buyer inquiries for a date range and returns parsed, cleaned leads — buyer name, company, mobile, message, product interest, city, and state — aggregated into a single structured response.
Claude calls the MCP tool over HTTPS the moment you ask about your TradeIndia leads in a conversation.
Nginx checks the caller against an allowlist of Anthropic's published IP range and rejects everything else with a 403.
An n8n MCP Server Trigger receives the tool call and hands it to a dedicated sub-workflow.
The sub-workflow queries the TradeIndia Inquiry API, then parses, cleans, and aggregates every lead into one structured JSON payload.
Claude receives the payload and presents the leads readably — no login, no export, no copy-pasting.
Bill of materials
Field test
“Get my TradeIndia leads from the last 2 days”
“Which of this week's inquiries mention packaging machines?”
“Summarise today's buyer inquiries and flag the ones asking for quotes”
Connected drawings
Commission a unit
The same pattern works for any system with an API — CRM leads, orders, support tickets, inventory. I design, build, and secure the MCP server; you just ask questions in a conversation.