Developer relations teams publish weekly snapshots, launch readouts, and ecosystem commentary. Trends MCP gives them npm download curves, GitHub trending lists, and search interest series so those posts stay grounded in fresh quantitative inputs instead of hand copied charts.
Queries often combine npm download trends, GitHub trending API, and Model Context Protocol in one tab stack. The goal is simple: reduce bespoke scrapers, reduce HTML surprises, and keep JSON stable enough for a newsletter template. Trends MCP aims at that intersection by exposing get_trends, get_growth, and get_top_trends with shared authentication.
Open with three npm packages that mattered to the community this week using exact registry names. Add a short GitHub trending section drawn from the daily feed type documented on the site. Insert one Google Search series for a phrase tied to the company narrative, such as AI agents or observability, so the post speaks to readers outside GitHub. Close with a single growth table comparing 3M and 12M windows for the headline package.
GitHub Actions workflows that post trend reports from REST shows how scheduled jobs can fetch payloads and publish summaries. The human step remains editing claims and adding context about releases, breaking changes, and security advisories. Trends MCP supplies the quantitative spine.
npm statistics describe registry downloads, which can diverge from unique humans. GitHub trending surfaces discovery, which is not the same as production usage. Google Search curves describe interest, which can spike on controversy. Good DevRel copy names those distinctions instead of smoothing them away.
Ecosystem wide surveys belong with Developer ecosystem trends for AI agents. LangChain based agents that call MCP tools are documented on LangChain agents that call live trend tools through MCP. For a broader tool catalog reference, see Trend tools for assistants, copilots, and backend services.
FAQ