Commerce CensusContactRequest access

API / Interoperability

MCP server

Six tools, not thirty endpoints. A chatty server makes an agent burn context stitching fragments and gives it room to hallucinate the join.

MCP @commercecensus/mcp

Request

NameTypeNotes
find_productWhich product is the user talking about?
search_commerceIntent in, ranked products out.
best_priceWhere is it cheapest right now, landed?
price_contextIs this actually a good price?
recallWhat do we already know about this shopper?
watch_price1× + rentTell me when it drops below X.
Request & response
// claude_desktop_config.json
{ "mcpServers": { "census": {
    "command": "npx", "args": ["-y", "@commercecensus/mcp"],
    "env": { "CENSUS_KEY": "cc_live_…" } } } }

> is the XM5 a good buy right now?

price_context("sony wh-1000xm5")
  → "excellent" — $198.00 at bestbuy, percentile 4 of 89 days,
    low $198.00 / median $319.99 / high $398.00

Notes

Each tool declares its meter, because no human approves individual agent calls and a metadata lookup should not cost what a live cross-seller compare costs.