Myntra Fashion Catalog Finder by Category & Brand: MCP config, n8n workflow and API

Myntra products with prices, discounts, coupons, ratings, sellers, per-size stock, specifications, policies, media, and optional written-review rows.

Fastest route, in Claude Code:

claude mcp add --transport http myntra-fashion-catalog-finder-by-category "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category" --name myntra-fashion-catalog-finder-by-category

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (The schema has no required fields; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.40$0.010$0.41
100$0.40$0.10$0.50
1,000$0.40$0.99$1.39

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http myntra-fashion-catalog-finder-by-category "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going
  • dataspryva--myntra-fashion-catalog-finder-by-categoryruns the Actor and returns its results

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowmyntra-fashion-catalog-finder-by-category.n8n.json

Actor on Apify
{
  "name": "Myntra Fashion Catalog Finder by Category & Brand to n8n only",
  "nodes": [
    {
      "id": "0a8be09a-337c-41ea-acf6-ff67ffe0a7bb",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "5de6aa1a-cc31-4118-aecd-e865a44b611b",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "9e2719e6-efcb-44a5-a52c-0e5cb3a1dee3",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/dataspryva~myntra-fashion-catalog-finder-by-category/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"mode\": \"search\",\n  \"searchQueries\": [\n    \"tshirts\"\n  ],\n  \"minPrice\": 0,\n  \"maxPrice\": 0,\n  \"minDiscount\": 0,\n  \"minRating\": 0,\n  \"includeDetails\": true,\n  \"includeReviews\": false,\n  \"maxReviewsPerProduct\": 1,\n  \"maxItems\": 2,\n  \"splitLargeSearches\": false\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: dataspryva/myntra-fashion-catalog-finder-by-category. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "9c1a8a02-cb64-4568-a1fe-b5596a32e8c7",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Myntra Fashion Catalog Finder by Category & Brand\n\nSource: [dataspryva/myntra-fashion-catalog-finder-by-category](https://apify.com/dataspryva/myntra-fashion-catalog-finder-by-category) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/dataspryva~myntra-fashion-catalog-finder-by-category/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","searchQueries":["tshirts"],"minPrice":0,"maxPrice":0,"minDiscount":0,"minRating":0,"includeDetails":true,"includeReviews":false,"maxReviewsPerProduct":1,"maxItems":2,"splitLargeSearches":false}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "mode": "search",
  "searchQueries": [
    "tshirts"
  ],
  "minPrice": 0,
  "maxPrice": 0,
  "minDiscount": 0,
  "minRating": 0,
  "includeDetails": true,
  "includeReviews": false,
  "maxReviewsPerProduct": 1,
  "maxItems": 2,
  "splitLargeSearches": false
}

FieldTypeWhat it does
mode string (5 options) What to fetch. Each mode has its own input list below.
searchQueries array One or more keyword searches (mode=search), e.g. tshirts, printed kurtas, nike running shoes. Each query is fetched separately and duplicates are removed.
categories array One or more category listings (mode=browseByCategory).
brands array One or more brands to browse (mode=browseByBrand), e.g. nike, levis, tommy hilfiger. Spaces and punctuation are normalized automatically.
startUrls array Myntra listing, search, category, brand, or product URLs (mode=byUrl). Product URLs are fetched as products; everything else is fetched as a listing.
productIds array Numeric Myntra product IDs or product URLs (mode=byProductIds), e.g. 36674095.
gender string (5 options) Restrict listing results to one gender segment. Applied on Myntra's side.
sortBy string (7 options) How Myntra orders listing results.
minPrice integer Only products whose selling price is at least this amount. 0 means no minimum.
maxPrice integer Only products whose selling price is at most this amount. 0 means no maximum.
minDiscount integer Only products discounted by at least this percentage. 0 means no minimum.
minRating number Only products rated at least this value (0-5). Products without a rating are excluded when this is above 0.
containsKeyword string Only products whose name contains this keyword (case-insensitive). Leave empty for all products.
includeDetails boolean Open each product page to add sellers, addresses, per-size stock and measurements, specifications, rating breakdown, policies, videos, and tags. Slower but much richer. URL and product-ID modes always fetch details.
includeReviews boolean Emit one row per written review with recordType review, in addition to product rows.
maxReviewsPerProduct integer Review rows to fetch for each product when written reviews are enabled (1-2000).
maxItems integer Total product rows to save across all queries, categories, brands, and URLs (1-10000). Review rows are additional.
splitLargeSearches boolean Go past the per-filter result cap by fetching gender, price-band, and sort slices, then removing duplicates. Recommended for deep exports.
proxyConfiguration object Optional override. Leave untouched and the actor selects a working connection automatically.

What your agent receives

Each run returns a list of records. The Actor publishes 12 fields, starting with productName, brand, price, mrp.

Field
recordType
productName
brand
price
mrp
discountPercent
couponCode
rating
sellerName
inStock
2 more fields
Field
category
productUrl

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdmyntra-fashion-catalog-finder-by-category/SKILL.md

---
name: myntra-fashion-catalog-finder-by-category
description: "Myntra products with prices, discounts, coupons, ratings, sellers, per-size stock, specifications, policies, media, and optional written-review rows. Runs the Apify Actor dataspryva/myntra-fashion-catalog-finder-by-category. Use when the user needs Myntra data with fields such as recordType, productName, brand, price, mrp, discountPercent and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/myntra-fashion-catalog-finder-by-category"
  store-url: "https://apify.com/dataspryva/myntra-fashion-catalog-finder-by-category"
---

# Myntra Fashion Catalog Finder by Category & Brand

Use this skill to fetch Myntra data with the Apify Actor `dataspryva/myntra-fashion-catalog-finder-by-category` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `browseByCategory`, `browseByBrand`, `byUrl`, `byProductIds` | What to fetch. Each mode has its own input list below. |
| `searchQueries` | array | One or more keyword searches (mode=search), e.g. `tshirts`, `printed kurtas`, `nike running shoes`. Each query is fetched separately and duplicates are removed. |
| `categories` | array | One or more category listings (mode=browseByCategory). |
| `brands` | array | One or more brands to browse (mode=browseByBrand), e.g. `nike`, `levis`, `tommy hilfiger`. Spaces and punctuation are normalized automatically. |
| `startUrls` | array | Myntra listing, search, category, brand, or product URLs (mode=byUrl). Product URLs are fetched as products; everything else is fetched as a listing. |
| `productIds` | array | Numeric Myntra product IDs or product URLs (mode=byProductIds), e.g. `36674095`. |
| `gender` | one of `men`, `women`, `boys`, `girls` | Restrict listing results to one gender segment. Applied on Myntra's side. |
| `sortBy` | one of `new`, `popularity`, `price_asc`, `price_desc`, `discount`, `customer_rating` | How Myntra orders listing results. |
| `minPrice` | integer | Only products whose selling price is at least this amount. 0 means no minimum. |
| `maxPrice` | integer | Only products whose selling price is at most this amount. 0 means no maximum. |
| `minDiscount` | integer | Only products discounted by at least this percentage. 0 means no minimum. |
| `minRating` | number | Only products rated at least this value (0-5). Products without a rating are excluded when this is above 0. |
| `containsKeyword` | string | Only products whose name contains this keyword (case-insensitive). Leave empty for all products. |
| `includeDetails` | boolean | Open each product page to add sellers, addresses, per-size stock and measurements, specifications, rating breakdown, policies, videos, and tags. Slower but much richer. URL and product-ID modes always fetch details. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQueries": [
    "tshirts"
  ],
  "minPrice": 0,
  "maxPrice": 0,
  "minDiscount": 0,
  "minRating": 0,
  "includeDetails": true,
  "includeReviews": false,
  "maxReviewsPerProduct": 1,
  "maxItems": 2,
  "splitLargeSearches": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~myntra-fashion-catalog-finder-by-category/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~myntra-fashion-catalog-finder-by-category/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `recordType`, `productName`, `brand`, `price`, `mrp`, `discountPercent`, `couponCode`, `rating`, `sellerName`, `inStock`, `category`, `productUrl`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.

  • Claude Code: save it as ~/.claude/skills/myntra-fashion-catalog-finder-by-category/SKILL.md, or .claude/skills/myntra-fashion-catalog-finder-by-category/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/myntra-fashion-catalog-finder-by-category/SKILL.md, or .agents/skills/myntra-fashion-catalog-finder-by-category/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill myntra-fashion-catalog-finder-by-category
  • Set APIFY_TOKEN in the agent's environment.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

How do I connect Myntra Fashion Catalog Finder by Category & Brand to Claude?

In Claude Code run: claude mcp add --transport http myntra-fashion-catalog-finder-by-category "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/myntra-fashion-catalog-finder-by-category and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Myntra Fashion Catalog Finder by Category & Brand need?

No field is required by the published input schema. The example on this page uses the Actor's own Store prefill, so it is a sensible first run.

What does Myntra Fashion Catalog Finder by Category & Brand cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, dataspryva--myntra-fashion-catalog-finder-by-category. Apify's MCP server listed them for this exact URL on 2026-11-11.