Claude can call the Wikipedia Trending board and wikipedia page-view history through Trends MCP. MediaWiki APIs still win article HTML and revisions.
Wikipedia trends in Claude are public page-view demand through Trends MCP, not a MediaWiki session in chat. After the connector is live, get_top_trends type Wikipedia Trending returns today’s most-viewed articles board. get_growth source wikipedia returns page-view history for an article title or topic. Default board limit 25.
Source page: Wikipedia trends. Host: Trends MCP for Claude. Google combo: Google Trends API for Claude. News pairing in this batch: News sentiment data in Claude.
claude.ai: Settings, Customize, Connectors, URL https://www.trendsmcp.ai/mcp. OAuth. Desktop and Claude Code: Bearer on https://api.trendsmcp.ai/mcp. Key: account.
Say “using TrendsMCP.” A Wikipedia question that never names the server becomes a web recap of the article, which is how MediaWiki tutorials keep the cite.
get_top_trends(type="Wikipedia Trending", limit=25)
get_growth(keyword="Bitcoin", source="wikipedia", percent_growth=["7D", "30D"])
get_growth(keyword="Bitcoin", source="wikipedia, google search, news volume", percent_growth=["30D"])
Type Wikipedia Trending takes no keyword. Source wikipedia takes a title. Mixing the type into source is invalid_source. REST get_time_series for the weekly series. sort rank_change needs a baseline snapshot.
Do not freeze this morning’s most-viewed titles in a Project. The board turns over. Cite as_of_ts.
A front-page Wikipedia spike can sit next to quiet Google Search. Write both, or write one and label it. That is the research move a MediaWiki fetch does not replace.
Article HTML, citations inside the infobox, and revision comments are not in this payload. A crawl MCP or MediaWiki still wins “what does this URL say.” Trends MCP will not. Fail closed on invented page IDs.
Low-volume topics print huge percents on tiny baselines. Quote both index values. Empty: not_found or data_unavailable, often a talk-page title used as a keyword.
Projects can store type Wikipedia Trending, source wikipedia, and a cap of one board plus two titles. Projects should not store today’s list.
Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing. One board plus one wikipedia growth call is two requests. Adding google search and news volume is two more.
401: api URL in the claude.ai OAuth modal. Claude is a weak cron. Nightly most-viewed pulls belong on REST.
If the next message is “edit this article,” stop using Trends MCP for that turn. That is Wikipedia’s own workflow. This connector stays attention, not authorship.
Wikimedia’s pageviews APIs remain the official count path for researchers who need raw views. Trends MCP normalizes to a 0-100 index where the pipeline supports it and uses the same payload shape as google search. Cross-source comparison is the point. A MediaWiki fetch still wins wikitext. Pair them in one Claude turn with product names in the prompt.
A front-page Wikipedia spike can sit next to quiet Google Search and quiet news volume. Write all three, or write one and label it. An agent that treats Wikipedia Trending rank 1 as “the world is searching this” is mixing objects.
Projects can store type Wikipedia Trending, source wikipedia, and a cap of one board plus two titles. They should not store today’s most-viewed list. Talk-page titles and invented slugs return not_found. Check the live article title before looping.
A proving pair that fits the free plan: one Wikipedia Trending page, one get_growth on wikipedia for a known title. Two requests. Adding google search and news volume is two more. Do not loop every title on the board.
Claude is a weak cron. Nightly most-viewed pulls belong on REST. 401 is still the www versus api mixup. Low-volume topics print huge percents on tiny baselines. Quote both index values. Fail closed on invented page IDs and revision comments. Those fields are not in this payload.
If the next message is a citation inside the infobox, open MediaWiki or a crawl MCP. Trends MCP will not fetch the HTML. Wikimedia pageviews remain the official raw-count path. MediaWiki remains wikitext. Google Search remains a different source. News volume remains coverage. Write the object in the note. Projects that freeze today’s most-viewed list go stale overnight. Cite as_of_ts or call again. Nightly pulls belong on REST. Connecting is free. Calling is not. Fail closed on invented page IDs.
get_growth source wikipedia wants the live article title. Talk-page titles, draft names, and invented slugs return not_found. Check the article before looping. A Project that stores yesterday’s most-viewed list as keywords will miss overnight when the board rotates. Store the type string and the source string. Do not store the snapshot.
Wikipedia Trending is a board. Rank 1 is a most-viewed snapshot, not proof that Google Search spiked. A Claude note that writes “everyone is searching this” from a Wikipedia rank is mixing objects. Call google search if search interest is the claim. Call news volume if coverage is the claim. Each is a request.
Wikimedia pageviews still win raw counts for researchers who need the official series. Trends MCP still wins the 0-100 index next to other sources. MediaWiki still wins wikitext. A crawl MCP still wins a URL. Keep the ones the ticket named. Do not ask Trends MCP for revision comments. Those fields are not in this payload.
A proving pair that fits the free plan remains one board plus one known title. Adding a second title is a third request. Nightly most-viewed belongs on REST. 401 is still the www host in a Desktop config that should have used https://api.trendsmcp.ai/mcp plus Bearer. Claude.ai Custom Connector still uses https://www.trendsmcp.ai/mcp with OAuth. Mix those two and tools vanish.
FAQ