Perfume MCP explained
What is a perfume MCP?
A perfume MCP is a Model Context Protocol server that lets AI agents query structured perfume data — longevity, sillage, notes, and community scores — instead of guessing from training data.
MCP stands for Model Context Protocol, an open way for AI clients such as Cursor and Claude Desktop to call tools. A perfume MCP is simply an MCP server whose tools are about fragrance: search a catalog, read a wear profile, compare two scents, or blend note pyramids.
Without a perfume MCP, an agent invents notes, mixes up flankers, and cannot tell whether a scent is actually long-lasting. With one, the model asks a live catalog. scentrev-mcp is that catalog: 14 tools over 126,000+ perfumes, with 0–1 scores and an n_records count so the agent can see how much community evidence sits behind a number.
Perfume MCP vs scraping a fragrance website
Browsing Fragrantica or a shop is fine for a human. It is a poor API: HTML changes, rate limits bite, and you still have to parse marketing copy. A fragrance MCP returns JSON the agent can plan against — season fit, sillage category, accord list — without impersonating a browser.
Who searches for perfume MCP
Developers wiring Cursor or Claude to product data. Perfume retailers who want an assistant that does not hallucinate stock. Enthusiasts who want “beast mode winter oud” answered with filters, not vibes. If that is you, install the perfume MCP server or call the same data as a perfume API.