get_fragrance — Perfume Picks MCP Tool Read-only
get_fragrance
(get fragrance) is one of 8 tools on the
Perfume Picks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_fragrance from your client
- Claude Code Perfume Picks get_fragrance run in your project directory
- Claude Desktop Perfume Picks get_fragrance ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Perfume Picks get_fragrance ~/.cursor/mcp.json
- VS Code Perfume Picks get_fragrance .vscode/mcp.json
- Zed Perfume Picks get_fragrance ~/.config/zed/settings.json
- Windsurf Perfume Picks get_fragrance ~/.codeium/windsurf/mcp_config.json
- Cline Perfume Picks get_fragrance ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Perfume Picks get_fragrance ~/.gemini/settings.json
- Grok Perfume Picks get_fragrance .mcp.json (in your project root)
- ChatGPT Perfume Picks get_fragrance Settings → Connectors → Advanced → Developer mode
- Claude.ai Perfume Picks get_fragrance Settings → Connectors → Add custom connector
- LangChain Perfume Picks get_fragrance pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http perfume-picks https://mcp.perfumepicks.app/?src=registryOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.