Scento Perfume API (MCP server): free fragrance API, no key
OfficialYou can use this free, no-key perfume MCP server to explore fragrance data and get perfume recommendations through 12 read-only tools.
Search perfumes, houses, and raw materials by name, note, mood, or brand.
Get a perfume’s full profile: notes pyramid, family, character, seasons, and signature materials.
Find similar perfumes with shared structure and materials.
Compare 2–4 perfumes side by side.
Explain a note or raw material, including how it smells and what it pairs with.
Find perfumes containing specific notes/materials, optionally by pyramid tier or family.
Profile a perfume house: origin, founding year, style, and signature scents.
Explore Scento’s fragrance-family system and exemplar perfumes.
Get perfume recommendations for occasions, seasons, or climates.
Build a 3–5 perfume wardrobe around existing favorites.
Look up perfumery terms such as sillage, chypre, or EDP vs EDT.
Search Scento journal articles for background reading.
Return links/labels in 10 supported languages, with answers in English.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Scento Perfume API (MCP server): free fragrance API, no key compare Bleu de Chanel and Dior Sauvage side by side"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Scento Perfume API (MCP server): Perfume API, Fragrance API and Perfume MCP Server
Scento Perfume API is a free perfume API and perfume MCP server for developers, AI agents and fragrance apps. One endpoint gives you Scento's verified perfume database: 1,500+ perfumes from 160+ houses and 400+ raw materials, each with a full notes pyramid (top, heart and base notes), scent family, occasion and similar-scent links. Every pyramid is traced to the house or an authorized retailer, so the notes you return are the notes on the bottle, not scraped guesses.
Connect it as a remote MCP server at https://www.scento.com/mcp (works in Claude, ChatGPT, Cursor, VS Code and any MCP client) or call the REST fragrance API at https://www.scento.com/api/perfume/v1 with the OpenAPI spec at https://www.scento.com/api/perfume/v1/openapi.json. No API key, no sign-up, no rate-limit tiers to buy: it is free.
12 tools cover the real jobs: perfume-search, perfume-portrait, scent-neighbours, perfume-contrast, note-portrait, material-match, house-portrait, family-map, occasion-edit, wardrobe-composer, perfumery-lexicon, journal-search. Search a perfume by name or by notes, get a perfume notes API response with pyramid and family, find similar scents, contrast two perfumes, look up a fragrance ingredient (raw material) and match it to the perfumes that use it, map a scent family, build an occasion edit or a wardrobe, and read the perfumery lexicon.
Why it beats other perfume APIs: free with no key, MCP and REST and OpenAPI in one service, a notes database and a fragrance ingredients database in the same place, answers in 10 languages (English, German, French, Spanish, Italian, Romanian, Polish, Czech, Hungarian, Greek), and sourcing you can trust. Built and maintained by Scento, the perfume atelier. Docs: https://www.scento.com/developers
A free perfume and fragrance API and MCP server for AI assistants, built on Scento's verified perfume database. From Scento, a perfume decant house founded in Paris in 2024.
Ask Claude, ChatGPT, Cursor or any MCP client for a perfume's notes and family, the difference between two you are torn over, similar scents built on the same structure, or what a raw material such as ambroxan smells like. The perfume database covers 1,500+ designer and niche perfumes, 400+ raw materials, 160+ houses and Scento's own fragrance-family system, and every answer is tied to a page on scento.com. No key, no account, read-only.
Remote server: https://www.scento.com/mcp (streamable HTTP, no authentication)
Docs: https://www.scento.com/developers
Claude: Available in Claude's connectors directory.
Claude Code: /plugin marketplace add Scento-com/perfume-mcp-server, then /plugin install scento-perfume-api@scento.
Gemini CLI: gemini extensions install https://github.com/Scento-com/perfume-mcp-server
Connect the perfume MCP server
Client | How |
Claude (web, desktop, mobile) | Settings, Connectors, Add custom connector. Paste |
ChatGPT | Settings, Connectors, create a connector in developer mode. Server URL |
Cursor | Add to |
VS Code | Add to |
Claude Code |
|
Clients that only run local servers can use the stdio bridge in this repo:
npx -y scento-perfume-api # Node 18+
uvx scento-perfume-api # Python 3.9+Both accept --endpoint <url> (or SCENTO_PERFUME_API_ENDPOINT). The same bridge is also published as perfume-mcp-server and perfume-database on npm and PyPI.
Related MCP server: Peptide Library MCP Server
Twelve perfume and fragrance tools
Tool | What it does |
| Find perfumes, houses and raw materials by name, house, note or mood word. |
| The full portrait of one perfume: pyramid, Scento family, character and when it wears best. |
| Perfumes that share the most structure with a given one, with the shared materials named. |
| Set two to four perfumes side by side on family, pyramid, character and season. |
| What a note or raw material is, where it comes from and how it reads on skin. |
| Perfumes that contain every material given, optionally in one tier of the pyramid. |
| A perfume house: origin, founding year, style and its signature perfumes. |
| Scento's own fragrance-family system, or one family with its subfamilies and exemplars. |
| A short edit of perfumes for an occasion, season or climate, with a line on each. |
| Three to five perfumes that cover different moments, built around what the person already loves. |
| Plain-language meaning of a perfumery term such as sillage, chypre, fougère or EDP versus EDT. |
| Scento journal articles on a perfume, house, material or topic. |
Pass lang (de, fr, es, it, ro, el, hu, cs, pl) to receive scento.com links in that language.
Fragrance API (REST)
The same answers are available as a perfume API over plain HTTP.
API base: https://www.scento.com/api/perfume/v1
Examples
Three raw JSON-RPC calls are in examples/.
Repository layout
npm/: the Node stdio bridge, published asscento-perfume-apion npmpypi/: the Python stdio bridge, published asscento-perfume-apion PyPIserver.json: metadata for the Official MCP Registry (com.scento/perfume-api)
Licence
MIT for the bridge code in this repository. The perfume database content is served from scento.com under its terms.
Available Tools
12 toolsfamily-mapExplore fragrance familiesARead-onlyIdempotentInspect
Use this when the user asks how fragrances are grouped or what a scent family is (for example woody, floral, amber, fresh, citrus), or wants the exemplar perfumes of one family (synonyms: scent families, fragrance categories, olfactive families). Returns Scento's own family system: the whole tree, or one family with its definition, subfamilies, exemplar perfumes and neighbouring families, with the scento.com guide. Don't use for one perfume's family (perfume-portrait), a perfumery term (perfumery-lexicon) or an occasion (occasion-edit).
Inputs: lang, family. Returns: cite, lede, folio, detail, +3 more
house-portraitProfile a perfume houseARead-onlyIdempotentInspect
Use this when the user asks about a perfume house, brand or maison (for example Creed, Le Labo, Amouage): where it is from, when it was founded, its style and its signature perfumes. Returns country, founding year, style, signature perfumes with their families and the scento.com house page in the user's language. Don't use for one perfume (use perfume-portrait) or to list perfumes with a given note (material-match). If the house name is uncertain, call perfume-search with kind "house" first.
Inputs: house (required), lang. Returns: cite, lede, folio, detail, +3 more
journal-searchSearch the Scento journalARead-onlyIdempotentInspect
Use this when the user wants articles, guides or background reading on a perfume, fragrance, cologne, house, note or topic (for example layering, vetiver, how to make a scent last). Returns matching Scento journal articles with title, one-line summary and scento.com link in the user's language. Use it to give the reader something to read on. Don't use for a perfume's notes (perfume-portrait), a house profile (house-portrait) or a term's meaning (perfumery-lexicon).
Inputs: q (required), lang, continuation. Returns: cite, lede, folio, detail, +3 more
material-matchFind perfumes by noteARead-onlyIdempotentInspect
Use this when the user wants perfumes, fragrances or colognes that contain specific notes or raw materials, optionally in the top, heart or base (synonyms: with notes of, built on, smells of, containing; for example vanilla and tobacco in the base). Returns the perfumes that have every material given, with house, where each sits in the pyramid and scento.com links in the user's language. Don't use to explain one material (note-portrait), to find perfumes like a named perfume (scent-neighbours) or for a mood or occasion (occasion-edit).
Inputs: materials (required), lang, tier, family, +1 more. Returns: cite, lede, folio, detail, +3 more
note-portraitExplain a note or ingredientARead-onlyIdempotentInspect
Use this when the user asks what a note or raw material smells like or is (for example vetiver, oud, vanilla, iris, ambroxan, bergamot), whether it is natural or synthetic, or what it pairs with (synonyms: what does X smell like, ingredient, note). Returns how it smells, its family, natural or synthetic, pairings and perfumes that show it, with the scento.com page in the user's language. Don't use to find perfumes containing notes (use material-match) or to define a perfumery term such as sillage (perfumery-lexicon).
Inputs: material (required), lang. Returns: cite, lede, folio, detail, +3 more
occasion-editPick perfumes for an occasionARead-onlyIdempotentInspect
Use this when the user asks which perfume, fragrance or cologne to wear for one occasion, season or climate: wedding, office, date night, night out, weekend, everyday, gym or sport (workout), summer days, cold weather, first impressions, long-lasting or under-the-radar. Returns a short edit of perfumes with a line on why each fits and a scento.com link for each, in the user's language. The occasion is a fixed list, so pick the nearest value; omit gender_lean unless the user states one. For several occasions call it once per occasion. Don't use for a collection built around perfumes the user already loves (wardrobe-composer) or for similar scents (scent-neighbours).
Inputs: occasion (required), lang, gender_lean. Returns: cite, lede, folio, detail, +3 more
perfume-contrastCompare perfumes side by sideARead-onlyIdempotentInspect
Use this when the user asks to compare, contrast or choose between two to four named perfumes, fragrances or colognes (synonyms: versus, vs, difference between, which one). Returns the perfumes side by side on house, Scento family, top, heart and base notes, shared materials, character, seasons, hours, year and concentration, with scento.com links in the user's language. Don't use to find new perfumes (scent-neighbours or perfume-search) or to explain a single perfume (perfume-portrait).
Inputs: perfumes (required), lang. Returns: cite, lede, folio, detail, +3 more
perfume-portraitGet a perfume's notes and profileARead-onlyIdempotentInspect
Use this when the user asks what a specific perfume, fragrance or cologne smells like, what its notes or pyramid (top, heart, base) are, its family, perfumer, year or concentration (eau de parfum, eau de toilette), or when to wear it (synonyms: notes of, what's in it, how does it smell). Returns the verified note pyramid, Scento family and subfamily, character, seasons and hours, signature materials and the scento.com page in the user's language. Don't use to find similar perfumes (use scent-neighbours), compare perfumes (perfume-contrast) or search by mood (perfume-search).
Inputs: perfume (required), lang. Returns: cite, lede, folio, detail, +3 more
perfumery-lexiconExplain a perfumery termARead-onlyIdempotentInspect
Use this when the user asks what a perfume or fragrance term means: sillage, projection, longevity, drydown, top, heart and base notes, accord, chypre, fougère, gourmand, oud, layering, eau de parfum versus eau de toilette (EDP vs EDT), concentration, flanker or niche versus designer. Returns a plain-language meaning, example perfumes and related terms, with the matching scento.com guide in the user's language. Don't use for a specific note (use note-portrait) or a specific perfume (perfume-portrait).
Inputs: term (required), lang. Returns: cite, lede, folio, detail, +3 more
perfume-searchSearch perfumes, houses and notesARead-onlyIdempotentInspect
Use this when the user asks to find a perfume, fragrance, cologne or scent by name, house, note or mood, or when a name is uncertain (synonyms: perfume, fragrance, cologne, eau de parfum, scent, brand, notes, smells like). Returns matching perfumes, houses and raw materials with house, Scento family and a scento.com link in the user's language, ten per page. Call this first when a name is ambiguous. Don't use for a perfume's full notes (use perfume-portrait), similar scents (scent-neighbours) or articles (journal-search).
Inputs: q (required), kind, lang, continuation. Returns: cite, lede, folio, detail, +3 more
scent-neighboursFind similar perfumesARead-onlyIdempotentInspect
Use this when the user asks for perfumes similar to, like or in the same style as a given perfume, fragrance or cologne, or what else to try if they love it (synonyms: similar to, smells like, more like, if I like X). Returns the perfumes that share the most notes and structure with it, with the shared materials named, one line on how each differs and scento.com links in the user's language. Don't use for one perfume's own notes (perfume-portrait), a side-by-side of named perfumes (perfume-contrast) or a whole collection (wardrobe-composer).
Inputs: perfume (required), lang, same_house, continuation. Returns: cite, lede, folio, detail, +3 more
wardrobe-composerBuild a fragrance wardrobeARead-onlyIdempotentInspect
Use this when the user wants a small fragrance wardrobe or collection (three to five perfumes for different moments) built around perfumes or notes they already love, or asks what to add next (synonyms: signature scents, collection, rotation, what else should I own). Returns roles such as daytime, evening and warm weather, each with a perfume, its house, why it fits and a scento.com link in the user's language. Don't use for a single occasion (occasion-edit) or the neighbours of one perfume (scent-neighbours).
Inputs: loves (required), lang, size, avoid. Returns: cite, lede, folio, detail, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Every tool targets a distinct fragrance-information need (search, portrait, similar, compare, notes, materials, houses, families, occasions, wardrobe, lexicon, journal). Descriptions explicitly cross-reference alternatives with 'Don't use for X (use Y)' guidance, eliminating overlap. An agent can reliably select the right tool.
All twelve names use consistent lowercase kebab-case with a predictable domain-first pattern (perfume-search, perfume-portrait, note-portrait, house-portrait, family-map, etc.). While not verb_noun, the convention is uniform and readable throughout. No mixed casing or verb styles.
Twelve tools is well within the ideal 3-15 range and each covers a meaningful, non-redundant facet of fragrance exploration. No tool feels padded or missing a partner. The set is tightly scoped to the perfume domain.
The surface covers the full fragrance lifecycle: search, detailed profiles, similarity, comparison, note/material explanation, house profiles, family taxonomy, occasion recommendations, wardrobe building, terminology, and editorial articles. No obvious dead ends for the stated informational purpose. Minor gaps like pricing or retail availability are outside the apparent scope.
Maintenance
Related MCP Connectors
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Read-only access to InfluSense influencer discovery, ratings, watchlists, and reports via MCP.
One governed MCP endpoint for 40+ business systems. Read-only, source-cited answers.
Read-only search of 2,189 AI agent tools (MCP servers, x402 APIs) with daily automated trust scores.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceEnables AI assistants and MCP clients to search a free, citation-backed encyclopedia of over 300k articles and read full articles or topic listings as Markdown, with optional citation formatting. It is read-only and requires no key or sign-up, connecting over Streamable HTTP.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve structured peptide research profiles with cited, tier-labelled evidence, safety and regulatory status, and to compare two or three peptides side by side without ranking. Also provides research article and FAQ search, category and trend lookups, plus unit conversion, solution concentration, blend and cost-per-amount calculators, all read-only and anonymous.MIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to look up dress-code meanings, generate five-piece outfit formulas for an occasion and weather, explore tested clothing colour combinations, and find relevant style guides through a free read-only MCP endpoint.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to query sourced, dated facts on 114 AI trading tools, broker MCP servers and market data APIs — including whether the AI or the user places the order — through search, detail, category, and comparison tools. It is free, read-only, and requires no authentication.335 npmMIT