Capterra Reviews MCP server

How an agent would call it

Two steps: search returns refs, then data_fetch opens one of them. The arguments below are the arguments that were sent.

{
  "tool": "search",
  "arguments": {
    "query": "https://www.capterra.com/p/186596/Notion/reviews/",
    "sources": [
      "capterra"
    ],
    "limit": 2,
    "runId": "<from run_begin>"
  }
}

{
  "tool": "data_fetch",
  "arguments": {
    "sourceId": "capterra",
    "ref": "<the ref object the search returned, verbatim — the review travels inside it>",
    "runId": "<from run_begin>"
  }
}

This runs against an account — send Authorization: Bearer <token> with the call. Get one at app.bedrocktap.com/dashboard/tokens; the free tier needs no card, and it reaches capterra like every other source.

What it costs. 3 credits per review row returned; a fetch costs nothing, because the row already carries the review. A search that returns no rows costs nothing.

What a row contains

One row is one review: the review id, its URL, and the review’s own title. meta carries the overall rating, the reviewer, the industry they work in, the review date, and the pros and cons as separate fields. The query is a product URL — the listing page for one product — so a product name has to be resolved to its URL first. This platform skews toward small and mid-sized buyers, and where it disagrees with the enterprise view of the same product, the disagreement is itself the finding. There is no per-review endpoint here, so `data_fetch` takes the whole ref object the search returned — the review lives in its `meta`. An id on its own carries no review and is refused.

A question it answers. Do small-business buyers rate this product the way enterprise buyers do?

Routing guidance

What an agent reads to decide whether capterra is the right source, and what to reach for when it is not.

Answers

When working: small-business software reviews, with pros and cons separated and the reviewer’s title attached.

Query shape

A product URL on the platform.

Price

Priced in credits, per row, per query or per call depending on the source. Every call is quoted before it runs — `cost_estimate` returns the exact figure and spends nothing. See /pricing.

Latency

Moderate.

Prefer instead

Go straight to your fallback: `g2` for B2B software reviews, or `software-reviews` if you specifically need Capterra rows as part of a cross-platform pull.

Cannot answer

Anything, at present. Do not spend a retry loop on it.

Caveat

Currently broken upstream and returning nothing. Treat it as unavailable.

Related sources