OmniCommerce Developer Docs
MCP Server
Endpoint: https://omnicommerce.sg/api/mcp
Tool Mapping
omni_search_catalog- wrapsGET /api/catalogomni_match_intent- wrapsPOST /api/geo/matchomni_discover_geo- wrapsPOST /api/geo/discoveromni_geo_feed- wrapsGET /api/geo/feed
JSON-RPC Quick Start
1) Initialize
curl -sS -X POST "https://omnicommerce.sg/api/mcp" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"clientInfo":{"name":"agent","version":"1.0.0"}}}'2) List Tools
curl -sS -X POST "https://omnicommerce.sg/api/mcp" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'3) Call Search Tool
curl -sS -X POST "https://omnicommerce.sg/api/mcp" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"omni_search_catalog","arguments":{"q":"fan","platform":"lazada","country":"sg","language":"en","limit":5}}}'Rendering Hints
MCP tool descriptions instruct agents to render results as product cards. Tool responses also include a _renderHint object.
{
"ok": true,
"results": [...],
"_renderHint": {
"type": "product_card_grid",
"layout": "grid",
"columns": 3,
"cardFields": ["image","title","brand","geo.readinessScore","price","marketplaceBuyLinks"]
}
}Logo Metadata Snippet
MCP supports icons on server metadata and tools. Use absolute URLs:
serverInfo: {
name: "omnicommerce-mcp",
version: "1.0.0",
title: "OmniCommerce",
websiteUrl: "https://omnicommerce.sg",
icons: [
{
src: "https://omnicommerce.sg/android-chrome-512x512.png",
mimeType: "image/png",
sizes: ["512x512"]
}
]
}Auth
Connector calls to /api/mcp can run without an auth header. The server forwards your Authorization and Cookie headers when provided, but MCP tools work on the public Catalog/GEO API surface.
- Bearer keys are optional and kept for compatibility with existing connectors.
- Direct
/api/catalog,/api/geo/feed,/api/geo/discover, and/api/geo/matchare public and discoverable by agents.