PrismCrawl

Model Context Protocol

Give your AI tools live search data.

Connect an MCP client to PrismCrawl with OAuth sign-in or your existing API key. Search tools use the same provider parameters, credit balance, and request history as the REST API.

Connect with OAuth

  1. Add a remote MCP server using the URL below and the Streamable HTTP transport.
  2. Choose your client's OAuth or sign-in option.
  3. Sign in to PrismCrawl, review the application and return address, and select Allow access. Your account needs an active API key from the dashboard.
  4. Return to the client and refresh its tool list.
MCP server URL
https://api.prismcrawl.com/mcp

The authorization server also provides a consent form that accepts your API key. Enter the key only on your PrismCrawl API server's authorization page. The client receives an access token; your API key stays with PrismCrawl.

Connect with an API key

If your client supports custom request headers, copy your key from the dashboard and configure the x-api-key header. A Bearer API key in the Authorization header is also accepted.

Connection values
{
  "url": "https://api.prismcrawl.com/mcp",
  "transport": "streamable-http",
  "headers": {
    "x-api-key": "<PRISMCRAWL_API_KEY>"
  }
}

Use your client's equivalent URL and header settings; configuration-file formats vary. Use OAuth when your client does not support custom API-key headers.

Registered tools

Each tool publishes its input schema. Product and review tools use provider IDs; search tools use queries. Google Play Games supports category browsing and source-verified game search. Check the service catalog for operation-specific limits.

Yelp Business Lookup supports native business results within a 200-result window, and Yelp Reviews supports complete review pages. Category filters and alternative sorting are unsupported for business lookup. Google Maps Reviews supports native continuation tokens. If Google restricts review access and supplies a verified place preview, the response identifies that subset and its pagination limits. Restrictions without a verified preview return an upstream error.

google_searchgoogle_maps_searchbing_searchamazon_searchduckduckgo_searchduckduckgo_mapsbing_mapsapple_mapsapple_maps_reviewsyelp_searchtripadvisor_searchtripadvisor_placeyelp_reviewstripadvisor_reviewsgoogle_play_appsgoogle_play_gamesgoogle_play_booksgoogle_play_moviesgoogle_play_productgoogle_play_reviewsapple_app_storeapple_app_store_productapple_app_store_reviewsgoogle_shopping_productgoogle_maps_reviewsgoogle_contributor_reviews

Results and credits

Tools return structured provider data and a request ID. Native AI summaries include their source links when the provider returns them. A successful search, product lookup, or review request uses one credit. Discovering tools does not consume search credits; each successful pagination call does.

The server reports invalid parameters, unavailable upstream data, exhausted credits, and rate limits as tool errors. Review the returned result before making another paid request.