/mcpso/clients/search

POST /api/mcpso/clients/search

Price: 1 credit

Walk mcp.so's catalogue of applications that speak MCP — IDEs, coding agents, desktop and web chat apps and agent frameworks — with name, tagline, author, star count and category

How to use it

Answers 'which apps can consume an MCP server'. `category` separates full editors from CLI coding agents, chat apps and SDKs, which is usually the distinction a caller means. These aliases belong to the client catalogue and are not accepted by /mcpso/servers. There is no keyword here: a query string is silently ignored by this route.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of client applications to return (examples: 60; min: 1)
• category string nullable — Restrict to one kind of MCP client application (one of: "ide", "coding-agent", "desktop-chat", "web-chat", "agent-framework", "other"; examples: "ide")
• tag string nullable — Restrict to editorially featured or verified clients (one of: "featured", "verified"; examples: "verified")
• sort string nullable — Order by newest addition or by name; omit for the site's own default order (one of: "latest", "name"; examples: "latest")

Response

• @type string (default: "McpsoClient")
• id string required
• alias string required
• url string required
• name string nullable
• tagline string nullable
• image string nullable
• author_name string nullable
• category string nullable
• star_count integer nullable
• status string nullable
• is_verified boolean nullable
• is_featured boolean nullable
• is_editor_pick boolean nullable
• created_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.