Chrome extensions · MCP TOOL

search_extensions

Search the separate Chrome Web Store catalog.

Set up your assistant · Authentication and errors

When to use it

Find extensions by publisher words, category or observed metrics. Trending and rising accept category filtering only and can report not_ready or stale until usable scores exist.

Parameters

Name	Type	Required	Default	Allowed values	Description
`limit`	integer	No	`20`	—	Maximum number of results requested. Minimum: 1. Maximum: 50.
`count`	boolean	No	`—`	—	Request an exact total when supported; broad or deep searches can still omit it.
`cursor`	integer	No	`0`	—	Zero-based offset; use the returned nextCursor to continue. Minimum: 0.
`after`	string	No	`—`	—	Opaque keyset token from nextAfter; replaces the offset when provided. Minimum length: 1. Maximum length: 1024.
`q`	string	No	`—`	—	Words in an extension’s name or publisher. Minimum length: 1. Maximum length: 200.
`category`	string	No	`—`	—	Store category ID; all means the overall chart where supported. Pattern: ^[a-z_]+(\/[a-z_]+)?$.
`type`	string	No	`"extension"`	extension, theme, app	Chrome Web Store listing type.
`minUsers`	integer	No	`—`	—	Minimum observed Chrome store users. Minimum: 0.
`maxUsers`	integer	No	`—`	—	Maximum observed Chrome store users. Minimum: 0.
`minRating`	number	No	`—`	—	Minimum star rating. Minimum: 0. Maximum: 5.
`minRatingCount`	integer	No	`—`	—	Minimum observed rating count. Minimum: 0.
`updatedWithinDays`	integer	No	`—`	—	Require a store update within this many days. Minimum: 1. Maximum: 3650.
`publishedWithinDays`	integer	No	`—`	—	Require publication within this many days. Minimum: 1. Maximum: 3650.
`manifestVersion`	integer	No	`—`	—	Chrome manifest version. Minimum: 1. Maximum: 3.
`featured`	boolean	No	`—`	—	Filter by featured status.
`sortBy`	string	No	`"users"`	users, ratingCount, rating, updated, published, trending, rising	Result ordering.
`order`	string	No	`"desc"`	asc, desc	Extension sort direction.

Defaults and constraints come from the published Zod input schema. “—” means no schema default or no enum restriction. Use JSON values of the listed type; additional handler rules are described above.

Example prompts

Find grammar extensions ordered by users.

Example call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_extensions",
    "arguments": {
      "q": "grammar",
      "sortBy": "users",
      "limit": 5
    }
  }
}

Example result

Illustrative, abridged JSON-RPC result. Only selected fields are shown; empty arrays illustrate a response with no rows. These are not current catalog observations. Parse the JSON inside content[].text.

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"data\":[],\"pagination\":{\"nextCursor\":null,\"nextAfter\":null,\"totalCount\":0,\"limit\":5}}"
      }
    ]
  }
}

Free vs paid results

Free keeps extension identities at absolute positions 1–10 and locks identities at 11+. User counts and ratings remain visible. Paid plans unlock identities.

Paid access does not fill coverage gaps or unknown values. Returned plan metadata and lock notes explain redaction where applicable. Read the full Free data policy.

Rate limits and usage credit

Plan	Calls per tool / day	All tools / week
Free	5	50
Basic	100	700
Pro	300	2,500

Days reset at 00:00 UTC. The combined ISO week resets Monday at 00:00 UTC. Every served tool call counts, including cached reads. Failed or refused calls are released along with any charge. Compare plans.

After either allowance, Basic and Pro can opt in to pay $0.02 in usage credit per call to search_extensions. A call exceeding both windows is charged once. Free is refused past its allowances; paid plans without opt-in or enough credit are also refused with HTTP 402 / JSON-RPC -32004.

Credential request throttles and, for live keyword work, store-work throttles also apply. Follow retry instructions in the error reference.