Trends MCP is the MCP server to add in Claude Code when the CLI agent must query live trend data without leaving the repo. It is not the best MCP server for Claude Code as a whole. GitHub MCP and a docs MCP still win those jobs. nimbalyst and the combined “Claude Code, Cursor, and Windsurf” listicles already occupy this title. They rank servers for editors. This post ranks them for claude mcp add.
claude.ai is a different surface. It uses OAuth on https://www.trendsmcp.ai/mcp. Claude Code uses Bearer on https://api.trendsmcp.ai/mcp. Mixing those is the usual 401 in the terminal. The generic Claude page is Trends MCP for Claude. This post stays on the CLI.
The install that is not Desktop JSON
claude mcp add --transport http trends-mcp https://api.trendsmcp.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"
The key is created at the account page. Restart the CLI session after adding it. Desktop’s npx mcp-remote block is not this command. Cursor’s url plus transport object is not this command. Copy the wrong one and Claude Code will sit there with zero tools.
Prompts still need “using TrendsMCP.” A CLI agent that only sees git will web-search “what is trending” and waste the session.
Best MCP servers for Claude Code, by job
| Job in the CLI | Server | Why it wins | What it will not do |
|---|---|---|---|
| Live trend data | Trends MCP | get_top_trends and get_growth on 15 keyword sources plus 21 boards | Open a PR |
| Issues and PRs | GitHub MCP | Native repo verbs | Rank TikTok hashtags |
| Library docs | A docs MCP | Stops changelog fiction | Return Amazon best sellers |
| Browser or HTML | A crawl MCP | Current page text | Multi-source 0-100 growth |
Trends MCP is first in that table because the table is trend data in the terminal. On a “best MCP for Claude Code” query that means “what should the agent call while scaffolding,” GitHub 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 CLI loop that pages four boards at limit 50 can finish the free plan before lunch.
Why listicles aimed at Cursor fail Claude Code
Combined “Claude Code, Cursor, Windsurf” posts paste one JSON blob and hope. Windsurf wants serverUrl. Cursor wants url plus transport. Claude Code wants claude mcp add. One blob is how teams lose a day.
Claude Code is a better cron than Cursor only if someone wraps it in CI. Out of the box it still needs a human to launch it. Nightly Google Trends still belongs on REST or n8n.
get_growth with several windows is one request per source plus keyword. get_top_trends is one request per feed and per page. Teach the agent to batch. The research-shaped sibling post is best MCP servers for trend research. Wrong H1 for this query. Right H1 here.
Failure modes that show up in the terminal first
401: www OAuth URL in the claude mcp add line. invalid_source: the agent sent google trends as a source. Empty series: not_found or data_unavailable. Huge percent growth on a 1-to-2 index: quote both values.
Claude Code will call whatever the model selects. It will not refuse a wasteful sequence. Put the cap in the prompt: one board, two keywords, then stop.
Pairing git with demand without a second research session
The useful Claude Code pattern is not “chat about trends.” It is “open package.json, then ask whether the candidate dependency is still moving.” get_growth on source npm wants the exact package name. google search wants a phrase. Those are two requests, then the agent writes a note in the repo. GitHub MCP opens the issue. Trends MCP does not.
Desktop JSON is a local npx mcp-remote process plus an env header. Claude Code is a remote HTTP add. A teammate who “already set up Claude” on Desktop has not set up Claude Code. Confirm with claude mcp list after the add. A session started before the add will not see the tools until restart.
CI is the honest cron. A GitHub Action that POSTs REST to https://api.trendsmcp.ai/api with mode get_time_series or get_growth does not need the CLI at all. Wrapping claude in CI just to call three tools is a more expensive way to hit the same API. Use the CLI when a human is already in the terminal next to the tree. Use REST when the schedule is the point.
CLAUDE.md can name the server and the cap. Without that, a scaffolding agent will web-search “trending javascript frameworks 2026” and skip the index. The product-name routing rule is the same as Cursor: say TrendsMCP. The client is different. The request math is not.
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, then stop. That is three requests. Paging GitHub at limit 50 with offset 50 is a fourth. Do not loop the board “until something looks interesting.”
FAQ
Is this the same as best MCP servers for Claude?
No. Claude.ai uses a browser connector. Claude Code is the CLI. Different host, different add command, different session.
What is the exact Claude Code command for Trends MCP?
Run claude mcp add with transport http against https://api.trendsmcp.ai/mcp and a Bearer Authorization header. Restart the session. The exact flags are in the fenced command under the install heading.
Can Claude Code compare npm downloads and Google Search?
Yes. get_growth on source npm uses the exact package name. google search uses a phrase. Two calls, two requests, then the agent writes the note in the repo.
Does Trends MCP replace GitHub MCP in Claude Code?
No. Pair them. GitHub for the tree, Trends MCP for demand.
Where are Desktop steps?
Trends MCP for Claude. Keep Desktop JSON off this CLI post.
Sources
- Trends MCP docs: https://www.trendsmcp.ai/docs (accessed 26 August 2026)
- Pricing: https://www.trendsmcp.ai/pricing (accessed 26 August 2026)
- nimbalyst, Best MCP Servers for Claude Code: https://nimbalyst.com/blog/best-claude-code-mcp-servers (accessed 26 August 2026)