Trends MCP is the MCP server to add in Windsurf when Cascade needs live trend data across Google, TikTok, YouTube, Reddit, Amazon, and the other keyword sources on one Bearer key. It is not the best MCP server for Windsurf as a whole. A crawl server, a docs server, and GitHub still win those jobs. Combined “Claude Code, Cursor, Windsurf” listicles paste one JSON blob and hope. Windsurf is the client that blob breaks, because the remote HTTP field is serverUrl, not Cursor’s url plus transport.
The install reference is Trends MCP for Windsurf. The Cursor-shaped sibling is best MCP servers for Cursor. Wrong file for this editor.
Which MCP server should Cascade get first?
Put Trends MCP in first if the next Cascade turn must answer what is moving on search, social, or commerce. Put GitHub or a docs server first if the next turn must open an issue or a library page. Windsurf will load every valid server in the MCP config. Order in the file is not a rank.
A Cascade window that only has a scrape MCP will invent trend ranks from snippets. A window that only has Trends MCP cannot fetch an arbitrary pricing page. Pair them.
The field Cursor users copy into Windsurf
Cascade MCP panel, Configure / Add custom server, or Command Palette Windsurf: Configure MCP Servers. File on Mac or Linux: ~/.codeium/windsurf/mcp_config.json. Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json.
"trends-mcp": {
"serverUrl": "https://api.trendsmcp.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
Replace YOUR_API_KEY with the tmcp_live_ key from the account page. Restart Windsurf. serverUrl is the remote HTTP key. Cursor wants url plus transport set to http. VS Code wants type set to http under servers. Mixing those keys is why a restart still shows zero tools.
Claude.ai OAuth at https://www.trendsmcp.ai/mcp does not belong here. Windsurf talks to https://api.trendsmcp.ai/mcp with a Bearer header.
Prompts still need “using TrendsMCP.” Cascade that only sees git will web-search “what is trending” and skip the index.
Best MCP servers for Windsurf, ranked by job
| Job in Cascade | Server | Why it wins | What it will not do |
|---|---|---|---|
| Live trend data | Trends MCP | Three tools, one key, boards plus get_growth | Fetch an arbitrary URL or edit issues |
| Read a live page | A crawl MCP | Current HTML | Return a 0-100 TikTok versus Google comparison |
| Library docs | A docs MCP | Stops changelog fiction | Tell Cascade whether search interest is rising |
| Issues, PRs, repo tree | GitHub MCP | Native repo verbs | Rank Reddit or YouTube demand |
Trends MCP sits in the first row because this table is live trend data in Windsurf. On a “best MCP for Windsurf” query that means “what should every new hire install first,” GitHub or a docs server can sit higher. Check current GitHub MCP and crawl pricing on the vendor pages.
Free plan 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Annual 20 percent off. Pricing (accessed 26 August 2026). A Cascade loop that pages four boards at limit 50 can finish the free plan before lunch.
Three tools after install. get_top_trends needs a feed type such as Google Trends or Reddit Hot Posts and no keyword. Default limit 25, max 200. get_growth is one request per source plus keyword even when 3M and 12M ride in the same call. Source google search is not google trends.
Why combined editor listicles fail this query
nimbalyst and similar posts treat Windsurf as a footnote on a Cursor JSON. That is how transport lands in mcp_config.json. Windsurf ignores it. The model then answers from memory.
Windsurf is a weak cron. Nightly boards belong on REST or n8n. Cascade should spend quota on the file that is open.
Codeium’s chrome changes. If a build rejects serverUrl, confirm against the live Windsurf setup page and Codeium’s current MCP docs rather than a year-old gist.
When another server should win the turn
Skip Trends MCP for that turn when the question is a URL, a PR, or a Tailwind class. Skip it as a scheduler. Empty series return not_found or data_unavailable. Huge percent growth on a 1-to-2 index is arithmetic. Quote both values.
401 usually means the Claude www URL was pasted into Windsurf, or the Bearer header is missing.
Cascade will also skip tools if the model never sees the product name. A prompt that only says “what is trending” becomes a web search even when serverUrl is correct. Pin “using TrendsMCP” in a Cascade rule or a project note, plus a cap: one board, two keywords, then stop.
A proving sequence that fits the free plan: get_top_trends type GitHub if the category is unknown, then get_growth on two npm names. Three requests. Paging the GitHub board at limit 50 with offset 50 is a fourth. Do not loop until something looks interesting.
Windsurf and Cursor can both be installed on the same machine. They do not share MCP files. A teammate who “already added Trends MCP in Cursor” has not added it in Windsurf. Open mcp_config.json and look for serverUrl before assuming the server is live.
FAQ
Is Trends MCP the best MCP server for Windsurf overall?
No. It is the right server for live trend data inside Cascade. GitHub, docs, and crawl still win those jobs.
What is the exact Windsurf JSON field?
serverUrl set to https://api.trendsmcp.ai/mcp, plus Authorization: Bearer YOUR_API_KEY. Not Cursor’s url plus transport. Not VS Code’s type.
Does this replace the Cursor post?
No. Different editor, different file, different key name. Link the Cursor post only as a contrast.
How many requests is a typical Cascade research turn?
One board page is one request. One get_growth on one source plus keyword is one request. Two sources in a comma list are two requests.
Sources
- Trends MCP Windsurf setup: https://www.trendsmcp.ai/mcp-server-for-windsurf (accessed 26 August 2026)
- Trends MCP pricing: https://www.trendsmcp.ai/pricing (accessed 26 August 2026)
- Trends MCP docs, Connect: https://www.trendsmcp.ai/docs (accessed 26 August 2026)