scentrev-mcp logoscentrev-mcp

Choose an interface

Fragrance API vs perfume MCP

Use a perfume MCP when your AI client speaks Model Context Protocol (Cursor, Claude Desktop). Use the fragrance API / perfume API when you want plain HTTPS from Node, Python, or a backend.

scentrev-mcp is one catalog with two doors. The perfume MCP door is for agents that already load MCP servers. The fragrance API door is REST for everything else. Same Bearer key, same scores, same 10-row list caps.

Pick perfume MCP when

  • You live in Cursor, Claude Desktop, Cline, or Windsurf.
  • You want the model to choose tools without writing HTTP glue.
  • You are demoing fragrance intelligence inside an IDE, not a custom app.

Pick the fragrance API / perfume API when

  • You already have a backend, RAG pipeline, or mobile app.
  • Your runtime is Python, Go, or a serverless function.
  • ChatGPT, a custom GPT, or an internal bot only speaks HTTPS today.

If you are unsure, start with MCP in Cursor using the Cursor perfume MCP setup, then call REST from production using the perfume API examples. You will not migrate data — only the transport.