The vendor's own sequencing is the part worth following: `categories` returns the type map and the `search` description tells you to call it first, because the category names are what make a query land. `detail` is the only route to a single product in full, and it wants the `id` a search hit gives you. `ping` earns its slot by telling an unreachable API apart from a query that matched nothing, which a caller would otherwise read as the same failure.
A catalogue lookup over Bitrefill's product range: `categories` returns the product type map, `search` finds products inside it, `detail` returns a single product by `id`, and `ping` reports whether the Bitrefill API is reachable.
- The full product type map from `categories`, which the search tool's own description points to as the step to run first so a query is aimed at a category that exists.
- Product search across gift cards, esims and mobile topups through `search`, narrowed by `category`, `country`, `language` and `query`, and paged with `limit` and `skip`.
- The detailed record for a single product from `detail`, addressed by the `id` a search result carries.
- A reachability check on the Bitrefill API from `ping`, which takes no arguments.
A Bitrefill API key, supplied as BITREFILL_API_KEY.
One command plus a key — npx -y bitrefill-mcp-server, then supply credentials