Claude can call the X (Twitter) Trending board through Trends MCP. There is no twitter keyword source on this index. Pair google search or news volume for history.
X / Twitter trends in Claude are a live board through Trends MCP, not an X developer account in chat. After the connector is live, get_top_trends with type X (Twitter) Trending returns the ranked topics snapshot. The parentheses are part of the type string on data sources. There is no twitter row in the keyword-source table. History for a named phrase uses google search, news volume, or tiktok. Default board limit 25.
Product pages: Twitter trends, X Twitter trending API. Host: Trends MCP for Claude. News pairing: News sentiment data in Claude.
claude.ai: custom connector https://www.trendsmcp.ai/mcp. Desktop and Claude Code: Bearer on https://api.trendsmcp.ai/mcp. Key: account.
Say “using TrendsMCP.” A prompt that only says “Twitter trends” often becomes a web recap of trends24 or official X, which is how those UIs keep the cite.
get_top_trends(type="X (Twitter) Trending", limit=25)
get_growth(keyword="standing desk", source="google search, news volume", percent_growth=["7D", "30D"])
Do not send type X (Twitter) Trending into get_growth. Do not invent source twitter or x. invalid_source is the usual result. REST may omit type to pull more feeds in one HTTP call. MCP cannot. One board page is one request.
sort rank_change needs a baseline snapshot. Count 0 with a note is not always an outage. Ask for sort rank when the job is the current page.
Do not freeze this morning’s topic list in a Project. The board turns over. Cite as_of_ts.
It will not return tweet bodies, impressions, or Community Notes. Official X API still wins objects. A crawl MCP still wins a status URL. Brandwatch-class suites still win always-on firehoses. Trends MCP is a snapshot.
A Project can store the exact type string and a cap: one X board, then two google search growth calls on shortlisted phrases, then stop. That is three or four requests if news volume is added.
Low-volume follow-up phrases print huge percents on tiny baselines. Quote both index values. Empty history: not_found or data_unavailable. That miss is not an X outage. It is a keyword-plus-source pair with no points.
Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing. Paging limit 200 is extra.
401: api host in the claude.ai OAuth modal. Claude is a weak cron. Nightly X boards belong on REST POST https://api.trendsmcp.ai/api with mode get_top_trends.
If the next message is “post this tweet,” stop using Trends MCP for that turn. If the next message is “what did this account say,” open the official API or a crawl. This connector stays the public trending topics page as this pipeline models it.
The keyword-source table on data sources lists google search, tiktok, reddit, news volume, and the rest. It does not list twitter or x. That is a product fact, not a missing FAQ. Directories that promise “Twitter trends API” often mean a scrape of the public topics page or the official X API. This MCP exposes the topics page as type X (Twitter) Trending. History for a named phrase is a different source on purpose.
A Project can store the exact type string, including parentheses, and a routing rule: board on X, then google search or news volume on the shortlisted phrase. It should not store this morning’s topics. Geo slices and “trending in a city” are not extra query params on this type unless the hosted contract documents them. Do not invent a country code field on get_top_trends.
A proving pair that fits the free plan: one X board, one get_growth on google search for a single phrase from that board. Two requests. Adding news volume is a third. Adding Reddit Hot Posts is a fourth object if the ticket named community heat. Cap it.
Official X API rate limits and access tiers are irrelevant to this board until someone needs tweet bodies. Then leave Trends MCP idle. Brandwatch-class firehoses still win always-on mentions. Check current X API pricing on developer.x.com if that path is in play. This page does not quote an X floor.
401 remains host mixup. Empty history on google search is not an X outage. Fail closed. Invented tweet IDs in a Claude note are worse than an empty tool list. Brandwatch-class suites still win always-on mentions. Official X APIs still win tweet bodies. A crawl MCP still wins a status URL. This connector stays the public topics snapshot. Nightly boards belong on REST. Connecting is free. Calling is not. Do not invent source twitter. Do not drop the parentheses in the type string. Recheck data sources if a close label fails. Type X (Twitter) Trending includes parentheses and a space. Twitter Trending can miss. X Trending can miss. Pin the string in the Project. Geo city boards are not extra params on this type. Official X API still wins tweet bodies. Brandwatch still wins firehoses. This connector still wins the public topics snapshot. Nightly boards belong on REST. One board proves the connect. Growth on google search is optional follow-up, billed separately.
Source twitter and source x are not legal growth sources. A Claude Project that stores them will burn retries. After the X board, the follow-up series is google search or news volume on the shortlisted phrase. That is a second request. It is not an X keyword history. Recheck X / Twitter trending API if a close type label fails.
FAQ