integrations

Connect Cline to the Trends API MCP server

Cline keeps MCP servers in its own settings file inside VS Code. One entry with a url and headers gives the agent keyword history, growth, and live boards.

Cline connects to the Trends API MCP server through its own settings file. Open the MCP Servers panel in the Cline extension, edit the settings, and add one mcpServers entry pointing at https://api.trendsapi.ai/mcp with a Bearer header. The editor's workspace MCP file does not reach Cline, which is the usual reason a working VS Code setup still shows no tools here. After saving, get_time_series, get_growth, and get_top_trends appear in the panel. Server detail sits on MCP server setup.

The entry

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

A red dot in the MCP panel means the connect failed; the error text there names the cause, usually the header. Registration for the editor itself sits on VS Code Trends MCP.

Approval and agent behaviour

Cline asks before each tool call unless auto-approve is on for the server. A request such as "check whether searches for this feature are growing" becomes a get_growth call with source google search, and the plan Cline writes can quote the percent. Keyword calls take a source string, board calls take a type label; both lists sit on the sources reference.

Scope of the tool

Cline sessions answer questions inside a coding task. Stored, scheduled pulls belong on POST https://api.trendsapi.ai/api. Only successful 200 responses count against quota; caps sit on pricing. The editor-native version of this setup sits on Cursor Trends MCP.

Cline Trends MCP setup

What you get

Entry in the Cline MCP settings file

Remote server at https://api.trendsapi.ai/mcp

Same Bearer key as REST

Per-call approval for trend tools

FAQ

Common questions

Why does Cline not read the workspace MCP file?

Cline keeps its own MCP settings, opened from the MCP Servers panel in the extension. A workspace .vscode/mcp.json serves Copilot and the editor; Cline ignores it. The same server must be registered once in each place that should call it.

What does the Cline entry look like?

Under mcpServers, a trends-api object with the url https://api.trendsapi.ai/mcp and a headers object holding Authorization Bearer plus the product key. Save the file and the server connects; the three tools appear in the MCP panel.

Can Cline call the tools without asking each time?

Cline asks for approval per tool call by default, and each server has an auto-approve setting. Trend reads are safe to auto-approve for most projects: the tools return data and change nothing outside the session.

Which key does Cline send?

The product key, as a Bearer header, identical to REST. A wrong value fails at connect time in the MCP panel, which is easier to spot than a failed call mid task.

Keep exploring

Connect the Trends API MCP server The product MCP URL is https://api.trendsapi.ai/mcp. Same Bearer key as REST. The server exposes get_time_series, get_growth, and get_top_trends. Connect VS Code to the Trends API MCP server VS Code reads MCP servers from .vscode/mcp.json under a servers key. One entry adds keyword history, growth, and live boards to Copilot chat. Connect Cursor to the Trends API MCP server One mcp.json block in Cursor settings gives the editor three trend tools next to the codebase. Same Bearer key as REST, no local server to run.

Start pulling trend data in 60 seconds.

100 requests a month free. No credit card, no sales call. One key works for every source.

Get a free API key