Give Perplexity access to live trend data - real search volumes, social momentum, and demand signals from 15+ platforms. Research with current numbers, not stale training data.
Updated 2026-08-19
Trends MCP is the structured trend server. Perplexity is a research host that may be able to attach it as a custom remote MCP server, depending on the product build. When that panel exists, the URL is https://api.trendsmcp.ai/mcp with Authorization: Bearer YOUR_API_KEY. The tools are get_trends, get_growth, and get_top_trends. Free Trends MCP usage is 100 requests per month. Starter is $19 per month. Perplexity is the right client when the job is an evidence pack: web pages for narrative, MCP JSON for measurement. It is the wrong client if the current Perplexity workspace has no MCP Servers setting; in that case ChatGPT, Claude, Cursor, or REST should host the same server instead.
If Perplexity Settings includes MCP Servers, add a remote server named Trends MCP. URL: https://api.trendsmcp.ai/mcp. Header: Authorization: Bearer YOUR_API_KEY. The key comes from email signup. Do not install a local npx @trendsmcp/server command as if Perplexity were Claude Desktop. Do not paste https://www.trendsmcp.ai/mcp. That www URL is OAuth for Claude.ai Connectors only.
If Settings has no MCP Servers entry, stop. The public agent guide flags this page as applicable only when the Perplexity build supports custom remote MCP. Forcing a JSON file from Cursor (url plus transport) into a Perplexity chat will not create a connector. Use ChatGPT setup or an IDE host until Perplexity exposes the panel.
After a successful add, require the prompt phrase “using TrendsMCP.” Perplexity’s default move is web search. Search is still useful. It is not a substitute for get_growth fields.
Perplexity’s advantage is mixed evidence. A thread can retrieve analyst writeups and call Trends MCP for the percent change those writeups omitted. Cursor’s advantage is the file tree. ChatGPT’s advantage is a long project memory without a search-first UI. The data layer stays Trends MCP in all three.
Use Perplexity for investment memos, category overviews written as prose, and “what did the press say versus what did search volume do.” Use n8n when the same comparison must rerun every Monday. Use Raycast when the question is one percent window on a Mac. Ranking those clients as “best AI” misses the point. They share one server and split on UI.
Lane 1 is Perplexity web search: who is writing about the topic, which numbers they cite, how old those numbers are. Lane 2 is Trends MCP. get_top_trends names what a live feed shows today (Google Trends, Reddit Hot Posts, TikTok Trending Hashtags). get_growth scores a shortlist across google search, reddit, and news volume with windows such as 1M and 3M in a single call per source plus keyword. get_trends pulls the weekly curve for the one entity that will appear as a chart in the memo. REST twins of that history call use mode: "get_time_series".
Keep the lanes from collapsing. If Perplexity quotes a blog’s “up 400 percent” claim, the next message should ask TrendsMCP for get_growth on the same keyword and source, then compare dates. Mismatched windows are the usual false fight: a blog used week-over-week, the API used 12M.
Source hygiene matters more in Perplexity because the model juggles search snippets. news volume is a keyword source. Google News Top News is a live feed type. Reddit wants a subreddit name without r/. The data sources catalog should be open in a second tab during the first week.
Pricing is 100 requests per month on Free. Perplexity users ask broad questions. Broad questions plus MCP can mean twenty tool calls before the essay starts. Budget in the prompt: two feeds, five growth checks, one series. Everything else stays in web search, which does not spend Trends MCP quota.
Starter at $19 per month is the usual step when a research team lives in Perplexity all day. Pro at $49 and Business at $199 exist for heavier volumes. Annual billing saves 20 percent. Perplexity Pro is a separate subscription.
MCP support in Perplexity can appear, move, or vanish with product builds. This page cannot freeze OpenAI-style connector guarantees. If tool calls never fire, fall back to REST POST https://api.trendsmcp.ai/api from a notebook and paste JSON into Perplexity as a file.
History is about five years of weekly points. That is weaker than a tick database and stronger than a screenshot of Google Trends. not_found means the keyword/source pair has no series, not that the topic is “dead.” Huge percents on tiny baselines still need the raw recent and baseline values in the memo.
Spaces and collections that reuse the same thread for a week will keep calling tools unless the user pins a finished JSON blob. Paste the last get_growth object into the thread and tell Perplexity to reason over that object before spending a new request. That habit matters more here than in Cursor, because Perplexity users ask follow-ups that sound new but repeat the same keyword.
Perplexity is a research UI on top of the shared Trends MCP server when custom MCP is actually present. It is not a second data vendor, and it is not a daily-limit API.
Tools for this workflow
get_trendsIn Perplexity, pull weekly history for a keyword so the research thread can cite a series instead of a training cutoff or a blog chart.
get_trends(keyword='AI wearables', source='google search', data_mode='weekly')get_growthAsk Perplexity to compare momentum across Reddit, news volume, and Google Search in one get_growth pass with several percent_growth windows.
get_growth(keyword='GLP-1', source='reddit, news volume, google search', percent_growth=['1M', '3M'])get_ranked_trendsDraft a ranked competitive brief from live feeds, then confirm each name with get_growth before quoting it as a mover.
get_ranked_trends(source='google search', sort='wow_pct_change', limit=20)get_top_trendsPulse-check YouTube or TikTok with get_top_trends, then use web search in the same Perplexity thread for the articles that explain the spike.
get_top_trends(type='TikTok Trending Hashtags', limit=25)FAQ