@roketfy/data-engine-mcp

MCP server for the Roketfy Data Engine — every endpoint (Trendyol, Hepsiburada, Amazon, n11, Akakçe, Google, and more) as an agent tool, generated from the same registry the public API and docs use. No endpoint is hand-wired here; adding one to the API adds it here too.

Calls go out over the same public HTTP API your own code would call, under your own API token — the same plan limits, the same live concurrency ceiling, the same credit cost, and every call lands in your dashboard's request log exactly like any other call.

Setup

Add this to your MCP client's config (Claude Desktop, Claude Code, Cursor — they all read the same shape):

{
  "mcpServers": {
    "roketfy-data-engine": {
      "command": "npx",
      "args": ["-y", "@roketfy/data-engine-mcp"],
      "env": {
        "DATA_ENGINE_API_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

Your token is in your dashboard sidebar.

DATA_ENGINE_API_URL is optional — defaults to https://data-api.roketfy.com. Set it only if you're pointing this at a different environment (e.g. a local api/ while developing against this repo).

What you get

• One MCP tool per endpoint, named {platform}_{slug} (e.g. trendyol_product_detail), with the exact same input schema the HTTP API validates against.
• The documentation itself, served as MCP resources — an agent can read docs://catalog and docs://{platform}/{slug} without a human pointing it at a web page first.

Full docs: https://data.roketfy.com/docs/mcp