TrendsAGI Now Works With WebMCP: Trend Intelligence for Your Browser's AI Agent
Signed in to TrendsAGI, the AI agent in Chrome or ChatGPT desktop can now read your trends, insights and recommendations through WebMCP. No connector or API key.
TrendsAGI now registers its tools with WebMCP, the proposed web standard that lets a page hand tools to the AI agent built into the browser. Open the TrendsAGI app while you are signed in, ask your browser's agent what is accelerating in your market, and it answers from TrendsAGI's measurements: no connector to install, no OAuth screen and no API key to paste.
It is the same set of read-only tools that already powers the TrendsAGI MCP server for Claude, ChatGPT, Grok and Cursor. The difference is where they run: inside your browser tab, with the session you are already using.
What your browser's agent can do now
| Ask | What the agent uses |
|---|---|
| "Which Technology topics are rising fastest today?" | list_trends sorted by velocity, with measured volume and growth |
| "Is this trend still rising, or should we pull spend?" | get_trend_analytics over 24 hours, 7 days or 30 days |
| "Who is talking about it and what angle fits our brand?" | get_trend_ai_insights: summary, sentiment, audience, marketing angles |
| "What should we act on this week?" | list_recommendations with each decision brief and its evidence |
| "Which of my watched keywords are trending, by category?" | read_data_schema then execute_sql, a read-only SELECT over your data |
| "Show me that trend." | open_app_page, which moves the tab to the trend's insight page |
The full list: list_trends, list_trend_categories, search_trend_insights, get_trend,
get_trend_ai_insights, get_trend_analytics, list_recommendations, list_crisis_events,
list_watchlist, get_api_usage, read_data_schema, execute_sql and
find_capability, plus open_app_page in the app. Plan limits still apply: insight search needs Advantage or
higher and crisis events need Scale or higher, exactly as in the app.
Public tools on trendsagi.com, no account needed
Every visitor's agent also gets a smaller set of public tools on trendsagi.com: search_trendsagi_docs (docs, API
reference, pricing and FAQs), list_trend_reports (our public reports on topics rising now, with measured velocity),
get_trendsagi_plans, get_ai_assistant_setup, and the free calculators as tools:
estimate_search_volume_from_google_trends, calculate_break_even_roas and score_ad_fatigue.
If you are signed in, the account tools are offered on trendsagi.com as well.
How to try it
- Use a browser with WebMCP: Chrome 149 or later (TrendsAGI is registered in Chrome's WebMCP origin trial, so there is nothing to turn on), ChatGPT desktop, or Brave's Leo (experimental).
- Sign in at app.trendsagi.com. The tools are registered for as long as you stay signed in.
- Open the browser's agent and ask a question about your market. To see what the page registered, Chrome's Model Context Tool Inspector extension lists every tool and lets you call it by hand.
How it works
When you sign in, the app reads the tool list from GET https://api.trendsagi.com/api/agent/tools and registers each tool
with document.modelContext.registerTool(). When the agent calls one, the page sends the arguments to
POST /api/agent/tools/{name} with your session. The API then replays the call as the ordinary API request it stands for,
through the same authentication, plan checks and rate limits as the app's own screens. That has two useful consequences:
- The agent can never see more than you can. It acts with your session, so it gets your plan's data and nothing else.
- WebMCP calls do not use your API quota. They count as app use, like opening the same view yourself. Calls through the MCP server or with an API key still count toward the daily API limit.
Because the MCP server and WebMCP share one tool definition on the server, a tool added or improved for one is immediately available in the other.
Safety by design
- Read-only. Every TrendsAGI tool reads and is marked
readOnlyHint.open_app_pageonly changes which TrendsAGI page is on screen. Watchlists, alerts and integrations stay in the app's own screens. - Untrusted text is labelled. Results that quote social posts or AI-generated insights carry
untrustedContentHint, which tells the agent to treat that text as data rather than instructions. - Gone when you sign out. Signing out removes the tools from the page.
- We see tool calls, not your conversation. TrendsAGI receives only the calls the agent makes.
For developers
The same tools are open to your own code. GET /api/agent/tools returns every tool in WebMCP's shape and needs no
sign-in; POST /api/agent/tools/{name} runs one with an API key. To offer TrendsAGI tools on your own website, register
them from your page and forward each call to your server, which keeps the API key. Version 0.16.0 of the Python SDK adds
TrendsAGITools.webmcp() for exactly that. See the WebMCP integration guide
and the example on GitHub.
WebMCP or the MCP server?
Use WebMCP when you work in TrendsAGI in a browser that has an agent. Use the MCP server for assistants outside the browser, such as Claude, ChatGPT, Cursor, Grok or Claude Code, and for scheduled or headless work. We compare the two in depth in WebMCP vs MCP: which should you ship?, and explain the standard itself in WebMCP explained.
WebMCP setup and FAQ · Create a free account · Connect the MCP server