MCP Server (directory-mcp)
A Model Context Protocol server exposing the directory as tools for AI runtimes (Claude, ChatGPT, Cursor, n8n AI agents). It speaks MCP Streamable HTTP and is a separate function from the REST API.
Endpointtext
https://rjpxllsycikfabazvkdh.supabase.co/functions/v1/directory-mcpMCP Streamable HTTP requires Accept: application/json, text/event-stream on every POST. Without it a compliant server answers 406 Not Acceptable.
Tools
| Tool | Does | Key inputs |
|---|---|---|
search_suppliers | Semantic (AI vector) or keyword supplier search. | query (required), category_id, region_id, limit (1–50, default 10), use_semantic (default true) |
get_business_detail | Full business record plus supplier performance summary. | business id / slug |
get_product_catalog | Products for a business, same shape as the REST catalog. | business id, paging |
get_rfq_status | RFQ state and supplier quote progress. | RFQ id |
get_category_tree | Category taxonomy for grounding queries. | optional parent |
Product results use the same product_pricing_tiers field name as the REST API, so a model or mapper written against one surface works on the other.
REST, Agent Gateway, or MCP?
| Use | When |
|---|---|
REST /v1/* | Deterministic application code: syncs, RFQ pushes, dashboards. Full endpoint coverage. |
| Agent Gateway | One-shot natural-language questions from your own backend, over HTTP. |
| MCP server | An AI runtime that should discover and call directory tools itself during a conversation. |
MCP exposes a curated subset of the data — there is no write path, no RFQ creation and no webhook management. Anything transactional goes through the REST API.
Current as of API 1.1.0 — released 7 September 2026