Fragrance MCP explained
What is a fragrance MCP?
A fragrance MCP is a Model Context Protocol server for structured scent data. Agents call tools for longevity, sillage, accords, and notes instead of guessing from training data.
Fragrance MCP means a Model Context Protocol server whose tools are about fragrance. The client (Cursor, Claude Desktop, Cline, Windsurf) loads the server. The model then calls search, profile, compare, or blend tools and gets JSON — not a web page.
scentrev-mcp is a fragrance MCP with 14 tools over 126,000+ scents. Scores are 0–1 with an n_records count. That is the difference between “this smells woody” and “sillage category enormous, 4,200 votes.”
Fragrance MCP vs perfume MCP
Same server. Fragrance is the word the industry, Europe, and the Gulf use. Perfume is the word most US searches use. If you typed fragrance MCP, use the fragrance MCP page. If you typed perfume MCP, use the perfume MCP page. The API key and endpoint do not change.
Fragrance MCP vs a fragrance website
A site like Fragrantica is for humans scrolling reviews. A fragrance MCP is for agents that must filter (“summer, moderate sillage, beloved”) and then explain the scores. No HTML, no scraping, 10-row caps.