Perfume Picks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | No | Override the database URL | |
| SUPABASE_SERVICE_ROLE_KEY | No | Internal use only — unlocks live 30-day wardrobe-add trending. Never distribute this key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fragrancesA | Full-text search across 13,000+ fragrances in the Perfume Picks database. Filter by brand, fragrance family, gender, and MSRP (USD). Returns note pyramids, accords, and community wear scores with source attribution. |
| get_fragranceA | Detailed record for one fragrance: full note pyramid (top/heart/base), accords, concentration, community longevity/sillage/compliment scores, and MSRP. Accepts a Perfume Picks slug or a name like 'Bleu de Chanel'. |
| find_dupesA | Curated dupes for a fragrance — cheaper scents documented to smell like the original, with match percentage and price comparison. The answer to 'what smells like X without the price tag'. |
| find_similarA | Fragrances most similar to a given one, from Perfume Picks' precomputed similarity ranking over notes and accords. |
| get_recommendationsA | Personalized fragrance picks from note/accord preferences (e.g. 'vanilla', 'oud', 'citrus'), a budget in USD, an occasion ('office', 'date night', 'gift', 'signature scent'), and gender presentation. |
| compare_fragrancesA | Side-by-side comparison: note pyramids, shared and distinct accords, longevity/sillage/compliment scores, concentration, and price difference. |
| trending_fragrancesA | Fragrances Perfume Picks users are adding to their wardrobes most over the last 30 days (falls back to catalog popularity when live activity data is unavailable). The method used is labeled in the response. |
| what_to_wear_tonightA | A fragrance suggestion for right now, based on mood, occasion (e.g. 'date', 'office tomorrow', 'night out', 'cozy evening in'), and season — scored with Perfume Picks' community compliment, office-safety, and versatility data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct read-only fragrance discovery step: lookup, search, dupes, similar scents, recommendations, comparison, trends, and a now-oriented suggestion. There is minor overlap between get_recommendations and what_to_wear_tonight, and between find_similar and find_dupes, but the descriptions clarify their different inputs and intents.
Most tool names follow a readable snake_case action_noun pattern such as get_fragrance, search_fragrances, and compare_fragrances. The main deviations are trending_fragrances and what_to_wear_tonight, which are still understandable but break the consistent verb-first pattern.
Eight tools is a well-balanced size for a fragrance discovery server. Each tool covers a meaningful step in the experience—exploring, understanding, comparing, recommending, and discovering—without unnecessary duplication.
The tool set covers the core discovery loop thoroughly: search the catalog, fetch details, compare fragrances, find alternatives, get personalized recommendations, check trends, and get a contextual suggestion. Any omitted write-oriented operations are outside the server's apparent read-only scope.