integrations

Connect Windsurf to the Trends API MCP server

Windsurf reads mcp_config.json and wants serverUrl for remote servers, not url. One entry gives Cascade keyword history, growth, and live boards.

Windsurf connects to the Trends API MCP server through mcp_config.json, and its remote field is serverUrl, not the url that Cursor and Cline use. One entry registers https://api.trendsapi.ai/mcp with the same Bearer key as REST. After a refresh in the MCP panel, Cascade lists three tools: get_time_series, get_growth, and get_top_trends. Server detail sits on MCP server setup.

The config entry

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

Open the file from Windsurf's MCP settings, paste the entry, and refresh. If the server is missing from the panel, the field name is the first thing to check. The file sits in the user profile and holds a live key, so keep it out of shared folders.

Ask in Cascade

"Is interest in local models still growing" maps to get_growth with source google search and the phrase as keyword. "What games top the Steam board" maps to get_top_trends with type Steam Most Played. Keyword calls take a source string; board calls take a type label. Both lists sit on the sources reference.

The panel context does the work: Cascade can check a demand claim, then write the landing page copy in the same session, with the growth percent quoted from the call rather than invented.

Session versus schedule

Cascade answers questions during a build session. Pipelines that store rows belong on POST https://api.trendsapi.ai/api. Only successful 200 responses count against quota; caps sit on pricing. The closest sibling setup sits on Cursor Trends MCP.

Windsurf Trends MCP setup

What you get

mcp_config.json with the serverUrl field

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

Same Bearer key as REST

Three tools inside Cascade sessions

FAQ

Common questions

Why does Windsurf use serverUrl instead of url?

Windsurf's mcp_config.json marks remote HTTP servers with serverUrl, while local stdio servers take command and args. A Cursor-style url entry is ignored, so the server never appears in Cascade. The field name is the whole fix.

Where does mcp_config.json live?

In the Windsurf configuration folder in the user profile, opened from the MCP settings panel. One file serves every workspace, so the key in it is available in all projects; treat the file as a secret.

What can Cascade answer once the server is connected?

get_time_series returns weekly keyword history, get_growth returns percent change over windows such as 3M and 12M, and get_top_trends returns ranked live boards such as Google Trends or Steam Most Played. The answers land in the Cascade panel next to the diff.

Which credential goes in the headers?

The product key as Authorization Bearer, the same key as POST /api. A mistyped value shows up as a failed server in the MCP panel before any question is asked.

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 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. 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.

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