get_perfume — parfum1 Perfume API MCP Tool Read-only
get_perfume
(get perfume) is one of 5 tools on the
parfum1 Perfume API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_perfume from your client
- Claude Code parfum1 Perfume API get_perfume run in your project directory
- Claude Desktop parfum1 Perfume API get_perfume ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor parfum1 Perfume API get_perfume ~/.cursor/mcp.json
- VS Code parfum1 Perfume API get_perfume .vscode/mcp.json
- Zed parfum1 Perfume API get_perfume ~/.config/zed/settings.json
- Windsurf parfum1 Perfume API get_perfume ~/.codeium/windsurf/mcp_config.json
- Cline parfum1 Perfume API get_perfume ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI parfum1 Perfume API get_perfume ~/.gemini/settings.json
- Grok parfum1 Perfume API get_perfume .mcp.json (in your project root)
- ChatGPT parfum1 Perfume API get_perfume Settings → Connectors → Advanced → Developer mode
- Claude.ai parfum1 Perfume API get_perfume Settings → Connectors → Add custom connector
- LangChain parfum1 Perfume API get_perfume pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http perfumes https://parfum1.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.