SerpApi vs DataForSEO for Google Trends and SERP data

SerpApi is the better pick for live, structured SERP JSON. DataForSEO is the better pick for pay-as-you-go Google Trends Explore and the rest of an SEO data platform. Trends MCP is the better pick when a Cursor or Claude agent needs ranked live boards and keyword growth across Google, TikTok, Amazon, and other sources without scraping search HTML. On 29 August 2026, SerpApi Starter is $25 for 1,000 successful searches, DataForSEO still prints a $50 minimum payment, and Trends MCP Starter is $19 for 1,000 requests. The head-to-head is a job match, not a single winner. Teams that only compare per-query SERP rates will miss the Google Trends daily cap on DataForSEO and the default google_light engine on SerpApi's MCP search tool.

Which product wins which job?

SerpApi wins live parsed search pages. DataForSEO wins cheap queued Google Trends Explore plus backlinks, keyword databases, and on-page APIs in one prepaid balance. Trends MCP wins multi-source trend boards and growth math for AI agents.

That table is the capsule in grid form. The rest of the post is the durable limits behind each cell, with sources dated 29 August 2026.

What Google Trends costs once the SERP sticker is ignored

DataForSEO is cheaper per Explore task than any SerpApi monthly bucket, if the caller can wait on a queue. The Keywords Data Google Trends pricing page (accessed 29 August 2026) still lists Standard Queue at $0.0027 per task and Live Mode at $0.011 per task. Each task accepts up to 5 keywords. The page also prints $540 per 1 million keywords on Standard as 200,000 tasks with 5 keywords each, and $2,200 per 1 million keywords on Live for the same packing.

The Explore task_post docs add limits SerpApi's marketing comparison does not lead with. Historical web data starts at 2004-01-01; other types start at 2008-01-01. Callers may send up to 2,000 API calls per minute, with at most 100 tasks per POST (error 40006 above that). Keyword strings cap at 100 characters. Topics and related-queries lists require a single keyword. Types are web, news, youtube, images, and froogle.

The same docs page states a shared capacity rule: 500,000 daily requests across all Google Trends API endpoints and all users. That is a platform-wide ceiling, not a per-account courtesy. High-volume overnight jobs need to spread across days or they collide with everyone else on the same Google Trends pipe.

SerpApi bills Explore as an ordinary search. The Google Trends Results API (accessed 29 August 2026) uses engine=google_trends and q. TIMESERIES and compared breakdown by region accept up to 5 queries; related topics and related queries accept 1. Maximum length per query is 100 characters. gprop maps to images, news, froogle (Shopping), and youtube. Date presets include now 1-H through today 5-y and all (2004-present). no_cache=true forces a fresh pull; cache lasts 1 hour and cached searches do not count.

On SerpApi's 29 August 2026 pricing grid, a Google Trends call costs the same as a Google organic call: Starter $25 / 1,000 searches (200/hour), Developer $75 / 5,000 (1,000/hour), Production $150 / 15,000 (3,000/hour) with Legal Shield. The $0 row is 250 searches and 50/hour. Only successful searches count. Throughput is a guaranteed successful-searches-per-hour figure. Best Effort is 1× plan price. Ludicrous Speed is 2× and claims 2.2× faster average response times. Ludicrous Speed Max is 4×.

Trends MCP does not sell a Google-HTML Explore clone. get_trends on source google search (or google news, google images, google shopping, youtube) returns a weekly series. get_growth can pass several presets in one call (12M, 3M, YTD, and the rest of the documented list) and still counts as one request for that source + keyword. get_top_trends with type Google Trends or Google Trends by Category is the live board, not a five-keyword overlay chart. Default limit is 25; the cap is 200. Pagination is offset. Those numbers come from the 29 August 2026 docs.md API reference, which also names sort=rank_change and windows 1d, 3d, 7d, 14d, 30d.

For a full SKU grid on the SERP side, see the SerpApi pricing and DataForSEO pricing posts. This comparison only restates the rows needed to choose a Trends path.

How the three Cursor MCP configs actually differ

Cursor loads three different objects, and the tool list behind each object is the real product.

SerpApi's hosted MCP page (accessed 29 August 2026) gives this shape:

{
  "mcpServers": {
    "serpapi": {
      "type": "http",
      "url": "https://mcp.serpapi.com/YOUR_SERPAPI_API_KEY/mcp"
    }
  }
}

Header auth is documented as a second path: Bearer on https://mcp.serpapi.com/mcp. The main tool is search. Sample parameters include params.q (required), params.engine (default google_light), params.location, params.output (md for markdown), and mode (compact or complete JSON). A Trends question that never sets engine to google_trends is a Google Light SERP, not Explore. That default is the foot-gun in this matchup.

DataForSEO's v3 MCP README (accessed 29 August 2026) publishes a remote URL with OAuth out of the box:

{
  "mcpServers": {
    "dataforseo": {
      "url": "https://mcp.dataforseo.com/v3/mcp"
    }
  }
}

Stdio skips OAuth and needs env credentials:

{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": ["dataforseo-mcp-server"],
      "env": {
        "DATAFORSEO_LOGIN": "your_api_login",
        "DATAFORSEO_PASSWORD": "your_api_password"
      }
    }
  }
}

api_request posts to DataForSEO .ai paths unless noAiMode is true. Docs tools cache for 24 hours. There is no get_top_trends equivalent. An agent that wants Explore must know /v3/keywords_data/google_trends/explore/task_post or the live Explore path and must handle task IDs on the Standard method.

Trends MCP's Cursor block from docs.md (same day) is:

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude.ai Connectors use a separate OAuth host on www, not the api Bearer URL. Mixing those two hosts is a common misconfig. Setup steps for Cursor live on the Google Trends MCP for Cursor page and the generic MCP server for Cursor page.

SerpApi is the widest live-search MCP if the agent needs shopping, scholar, or maps in the same search call. DataForSEO is the widest SEO MCP if the agent must also hit backlinks or on-page. Trends MCP is the only one of the three whose default tools are trend series, growth, and live boards.

When the honest pick is not a SERP API

A rank tracker that stores overnight Google HTML should price DataForSEO Standard Queue first: $0.0006 per 10-result organic SERP on the Google Organic pricing page (accessed 29 August 2026), $50 minimum payment on the main pricing page. Live Mode at $0.002 per SERP is the fair SerpApi comparison, not the queued sticker. SerpApi's own 30 July 2026 comparison post argues that gap from the vendor side; the organic dollars above are from DataForSEO's page, not from that post.

A product that shows a user the current SERP, including ads and People Also Ask, should start on SerpApi. Speed modes and Legal Shield begin at Production ($150 / 15,000). ZeroTrace is a Cloud 1M+ column. Those are compliance features, not trend features.

An AI agent in Cursor that asks "what is trending on TikTok and Amazon this week, and how has Google Search interest in this SKU moved over 12 months" is a Trends MCP job. HTML pricing on 29 August 2026 lists monthly Starter $19 / 1,000, Pro $49 / 5,000, Business $199 / 25,000, annual billed as $192 / $468 / $1,910 ("2 months free" on the yearly toggle). Keyword alerts: Pro 50, Business 250. The same HTML markets 35+ data sources. Same-day docs.md lists 15 keyword sources and 24 named live feeds, including TikTok Trending Hashtags by Category. Same-day llms.txt says "plus 21 live feeds." The MCP get_top_trends schema lists 23 feeds and omits TikTok Trending Hashtags by Category. Those four counts disagree; treat them as a split. The HTML counter on this run read 9,457,604 API calls served. The Trending Now engine on SerpApi is documented at google-trends-trending-now (engine=google_trends_trending_now).

DataForSEO still covers Keyword Data, Backlinks, Domain Analytics, On-Page, Labs, Business Data, Merchant, App Data, Content Analysis, and AI Optimization as separate API groups on its pricing hub. SerpApi does not replace that stack. Trends MCP does not replace it either.

FAQ

Is DataForSEO cheaper than SerpApi for Google Trends?

On a single Explore task, yes: $0.0027 Standard or $0.011 Live versus SerpApi's $25 per 1,000 successful searches on Starter ($0.025 each if the bucket is used evenly). The DataForSEO figure assumes the 500,000/day shared Google Trends cap has room, and Standard may take up to 45 minutes. SerpApi's call is synchronous and shares the plan's hourly throughput cap (200/hour on Starter).

Can SerpApi replace DataForSEO's backlinks and keyword database APIs?

No. SerpApi's MCP and REST catalog is search-result parsing. DataForSEO's pricing hub lists Backlinks, Keyword Data, Domain Analytics, and On-Page as separate products. A shop that needs those datasets keeps a DataForSEO balance even if SERP HTML moves to SerpApi.

Does Trends MCP return the same overlay chart as Google Trends Explore?

No. Explore compares up to 5 keywords in one Google Trends task. Trends MCP get_trends is one source + one keyword per request. Comparison across Google, TikTok, and Amazon is a get_growth call with a comma-separated source list, which is a different chart than Google's five-term overlay.

What Cursor MCP should a trend-research agent load first?

Load Trends MCP when the questions are live boards and multi-source growth. Add SerpApi when the agent must read a live SERP. Add DataForSEO when the agent must call Explore in bulk or pull backlinks. The three JSON blocks above can sit in the same mcp.json. They are not interchangeable tool names.

Do unused credits roll across vendors the same way?

SerpApi's pricing FAQ (29 August 2026) does not promise monthly search rollover; downgrades move leftover searches into Extra Credits. DataForSEO is a prepaid balance drawn per task, with a $50 minimum payment. Trends MCP unused monthly requests do not convert to a cash balance; 429 until reset or upgrade, with no overage charges, per the HTML FAQ the same day.