The product MCP server is https://api.trendsapi.ai/mcp. Official docs and https://trendsapi.ai/llms.txt show that URL in an mcp.json block. The header is the same Bearer key as POST https://api.trendsapi.ai/api. The server exposes get_time_series, get_growth, and get_top_trends. It is not a fourth mode. Cron and Airflow still use REST. Caps sit on pricing.

mcp.json

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

That block matches the documented config. Cursor, VS Code, and other hosts that read mcp.json paste it as-is. Do not wrap the token in extra quotes inside the header value. Auth detail is on authentication.

The homepage connector for Claude and ChatGPT uses https://trendsapi.ai/mcp as the connector URL and the same key. One-click setup is on the homepage.

The three tools

Tool REST mode Notes
get_time_series get_time_series One source, one keyword
get_growth get_growth percent_growth presets. Comma-separated sources allowed
get_top_trends get_top_trends type required on MCP. No keyword

source strings are MCP values such as google search. Live type strings are labels such as Google Trends. Do not swap them. Mode pages: get_time_series, get_growth, get_top_trends.

get_trends is a REST alias only. Send get_time_series from an agent.

REST remains the batch path

A LangChain host can load this server instead of a StructuredTool. n8n can use its MCP Client node or HTTP Request. A crontab line should still POST /api. MCP adds a model in front of a call the script already knows.

Failed 4xx calls do not count as a successful lookup. 401 is the header. 429 is the cap, on errors.