/glama/servers/search

POST /api/glama/servers/search

Price: 1 credit

Search Glama's directory of open-source MCP servers. Returns each server's namespace/slug id, name, description, attribute tags, tool count, recent usage, Glama's licence, security, maintenance and quality grades, and the source repository with its language, star count, licence, npm package and declared environment variables. Results can be narrowed by free text and by attribute tags.

How to use it

Omitting `query` browses the catalog, which is what you want when the filter is an attribute rather than a phrase; `attributes` values are the `lookup_key` strings /glama/attributes returns and several of them combine as AND. Whatever the filter, the source stops serving rows past 1000 for one query, so a broad search is a sample and not the full catalog — slice it with attributes to reach further, and `sort` reaches a different slice too since each ordering exposes a different part of the 1000-row window. `scores` mixes types on purpose: licence and security are 0-100 numbers, maintenance and quality are letter grades, and any of them can be null on a server Glama has not graded. Pass a returned `id` to /glama/servers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free text matched against server names and descriptions. Leave it out to browse the whole catalog (examples: "slack", "postgres", "browser automation"; minLength: 1)
• count integer required — Max number of results (examples: 20; min: 1; max: 1000)
• attributes array nullable — Keep only servers carrying every one of these Glama attribute keys. Values come from /glama/attributes (examples: ["category:developer-tools"], ["language:python","hosting:remote-capable"])
• sort string nullable — Ordering. Leave out for search relevance. Known values: search-relevance:desc, added-at:desc, updated-at:desc, github-stargazers:desc, recent-github-stargazers:desc, recent-usage:desc, npm-downloads:desc (examples: "github-stargazers:desc", "updated-at:desc")

Response

• @type string (default: "GlamaServer")
• id string required
• url string required
• namespace string nullable
• alias string nullable
• uid string nullable
• numeric_id integer nullable
• name string nullable
• description string nullable
• description_markdown string nullable
• attributes array (default: [])
• tool_count integer nullable
• app_count integer nullable
• has_apps boolean nullable
• recent_usage integer nullable
• discoverability_score number nullable
• quality_score number nullable
• scores object nullable
  • @type string (default: "GlamaScores")
  • license integer nullable
  • security integer nullable
  • maintenance string nullable
  • quality string nullable
• repository object nullable
  • @type string (default: "GlamaRepository")
  • github object nullable
    • @type string (default: "GlamaGithubRepository")
    • full_name string nullable
    • name string nullable
    • id integer nullable
    • tree_id integer nullable
    • url string nullable
    • default_branch string nullable
    • language string nullable
    • stargazers integer nullable
    • recent_stargazers integer nullable
    • pushed_at string nullable
    • owner object nullable
      • @type string (default: "GlamaGithubOwner")
      • login string nullable
      • id integer nullable
      • uid string nullable
    • license object nullable
      • @type string (default: "GlamaLicense")
      • name string nullable
      • url string nullable
  • npm_package object nullable
    • @type string (default: "GlamaNpmPackage")
    • name string nullable
    • weekly_downloads integer nullable
  • supported_platforms array (default: [])
  • environment_variables_schema object nullable
  • arguments_schema object nullable
  • latest_release_version string nullable
  • inspectable boolean nullable
  • has_readme boolean nullable
  • project_url string nullable
  • maintainers array (default: [])
• repository_private boolean nullable
• icon_slug string nullable
• added_at string nullable
• updated_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.