JavaScript ecosystem decisions hinge on weekly download counts. Source npm requires the precise package string so assistants compare frameworks fairly and avoid fuzzy matches across similarly named libraries.
Two packages can differ by one character yet serve opposite stacks. Trends MCP enforces the exact-name rule documented beside source: "npm" in Data Sources.
Ask the user to confirm the string from npmjs.com before running get_trends. When comparing React meta-frameworks, run sequential calls per package so each response stays tied to one keyword.
npm trends, GitHub and developer trends. Hub: MCP trend tools for assistants.
Tools for this workflow
get_trendsShow multi-year adoption for a library before a major version upgrade.
get_trends(keyword='react', source='npm', data_mode='weekly')
get_growthCompare 3M and 12M download momentum between two candidate packages.
get_growth(keyword='vue', source='npm', percent_growth=['3M', '12M', 'YTD'])
get_ranked_trendsList npm packages with the fastest week-over-week download growth for radar reports.
get_ranked_trends(source='npm', sort='wow_pct_change', limit=30)
get_top_trendsAdd a live macro feed when the brief mixes library adoption with breaking search topics; npm has no dedicated top list in this API.
get_top_trends(type='Google Trends', limit=15)
FAQ