TrendsAGI registers its tools with WebMCP, the new web standard for browser AI agents. Open TrendsAGI while signed in and your browser's agent can ask what is accelerating in your market, read the insight behind a trend and pull your recommendations, using your session instead of a connector.
Where the tools are
A page calls document.modelContext.registerTool() with a tool's name, description, JSON input schema and a function. The browser offers the tool to its built-in agent, which calls the function directly instead of reading pixels and clicking buttons. It is a W3C Community Group draft, edited by engineers at Microsoft and Google.
Read the full explainer: WebMCP explained, with registerTool examples.
| TrendsAGI via | WebMCP | MCP server |
|---|---|---|
| Where the tools run | In the page, in your browser tab | On a server the assistant connects to |
| How it signs in | Your existing TrendsAGI session | OAuth sign-in or an API key per connection |
| Setup | None: open the app while signed in | Add https://api.trendsagi.com/mcp to the assistant |
| Works without a browser | No | Yes: Claude, ChatGPT, Cursor, Grok, Claude Code, scripts |
| Counts toward API limits | No, it is app use | Yes, each call is one API request |
The same read-only tools as the MCP server, run with your session.
Any visitor's agent can use these. Signed-in visitors get the account tools here too.
Sign in at app.trendsagi.com, open your browser's agent and ask, for example, “Which of my watched topics are rising fastest today, and what angle does TrendsAGI suggest for the top one?”
WebMCP is in an origin trial from Chrome 149. To try it on any recent Chrome, turn on chrome://flags/#enable-webmcp-testing and relaunch. Chrome's Model Context Tool Inspector extension lists the tools a page registered and lets you call them.
In an origin trial from Edge 150, on the same engine as Chrome.
Supports WebMCP.
Experimental support in the Leo assistant.
Not yet: Mozilla and WebKit have open standards-position requests.
Register the tools from your page and send each call to your server, which keeps your API key and checks your user's sign-in. The Python SDK serves both halves: TrendsAGITools.webmcp() lists the tools and tools.call() runs one.
GET https://api.trendsagi.com/api/agent/tools: every tool in WebMCP's shape, public.POST https://api.trendsagi.com/api/agent/tools/{name}: run one with an API key.const modelContext = document.modelContext ?? navigator.modelContext;
if (modelContext) {
const tools = await fetch("/trendsagi/tools").then((r) => r.json());
for (const tool of tools) {
await modelContext.registerTool({
...tool,
async execute(args) {
const response = await fetch(`/trendsagi/tools/${tool.name}`, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify(args ?? {}),
});
return JSON.stringify(await response.json());
},
});
}
}WebMCP is a proposed web standard from the W3C Web Machine Learning Community Group, edited by engineers at Microsoft and Google. A page calls document.modelContext.registerTool() to describe a tool (a name, a description, a JSON input schema and a JavaScript function), and the browser offers it to the AI agent built into the browser. The agent calls the function directly instead of clicking through the page.
No. They share ideas (named tools with JSON schemas) but MCP connects an assistant to a server over the network, while WebMCP tools live in a web page and run in the user's browser tab with the page's own session. TrendsAGI offers both: the hosted MCP server at https://api.trendsagi.com/mcp, and the same tools through WebMCP on app.trendsagi.com.
As of October 2026, Chrome (origin trial from Chrome 149, or the chrome://flags/#enable-webmcp-testing flag) and Edge (origin trial from Edge 150) support it, ChatGPT desktop supports it, and Brave has experimental support in Leo. Firefox and Safari have not shipped it.
No. Sign in to app.trendsagi.com and the app registers the tools for as long as you stay signed in. The tools run with your session, so the agent sees exactly what your account can see. Public tools on trendsagi.com need no account at all.
No. Every TrendsAGI tool reads data and is marked readOnlyHint. The one app tool that is not a read, open_app_page, only moves the tab to another TrendsAGI page. Adding watchlist topics, alerts or integrations stays in the app's own screens.
No. A tool call made with your browser session counts as app use, the same as opening that view yourself. Calls made with an API key, through the MCP server or the REST endpoint, count toward your plan's daily API limit.
Register the tools from your page with document.modelContext.registerTool() and forward each call to your own server, which holds your TrendsAGI API key and checks your user's sign-in. The Python SDK's TrendsAGITools.webmcp() returns the tool descriptions and tools.call() runs them. Never put an API key in page code.
Using an assistant outside the browser? Connect the TrendsAGI MCP server. Questions: contact us.