Integrations

Everything here talks to the same keyless API, so none of it needs credentials.

n8n

n8n-nodes-scento-perfume is an n8n community node for the API, published on npm: npmjs.com/package/n8n-nodes-scento-perfume.

Install it in n8n under Settings, Community nodes, Install, with the package name n8n-nodes-scento-perfume, then add the Scento Perfume node to a workflow. No credentials are needed.

Each operation maps to a route on the Endpoints page. The node has a Language option for the scento.com links and a Return All switch for list operations that follows continuation for you. n8n AI agents can use it as a tool.

Stdio bridges

Some MCP clients can only start local servers. Two small packages relay stdio to the remote endpoint at https://www.scento.com/mcp:

A client config for the Node bridge:

{
  "mcpServers": {
    "scento-perfume-api": {
      "command": "npx",
      "args": ["-y", "scento-perfume-api"]
    }
  }
}

Both accept --endpoint <url> if you want to point them somewhere else. Clients that support remote servers do not need a bridge: see MCP server.

Any HTTP tool

The REST API is plain GET with JSON responses and open CORS, so any tool with an HTTP request step can use it: set the method to GET, use a URL from the Endpoints page and parse the response as JSON. Generators that read OpenAPI 3.1 can build a typed client from openapi.json.

Also listed on

The same API appears in these places. They are listings, not separate services.

• Claude connectors directory
• RapidAPI
• Apify
• Hugging Face Space
• GitHub: Scento-com/perfume-api, with curl, JavaScript and Python examples