
TrendsAGI
io.github.TrendsAGIPublished by GitHub account TrendsAGIv1.2.0Updated Nov 7, 2026
Trend data, insights and recommendations for AI agents. Read-only, with an Agent Skill.
Overview
Hosted, read-only MCP server that gives an assistant live social trend data, AI insights, recommendations and read-only SQL over TrendsAGI's dataset.
- What you can do
- List and search trending topics by category or phrase, sorted by velocity, growth or volume, with valid category names.
- Fetch a single trend, its volume time series, and AI insights covering summary, key themes, sentiment, audience and marketing angles.
- List evidence-backed recommendations with decision briefs, crisis events for monitored topics, and watchlist entries.
- Read the data schema and run one validated read-only SQL SELECT for filters, joins and aggregation.
- Check whether TrendsAGI can do a task and which tool or app page handles it, and read remaining daily API quota.
- When to use it
- Useful when an assistant needs current social trend signals, measured volume and velocity, or evidence-backed campaign angles rather than general web search. Suited to paid-media, growth and content planning questions such as what is accelerating in a category and who to target.
- Requirements
- Remote endpoint at api.trendsagi.com over streamable HTTP with OAuth sign-in and connection approval; clients without OAuth can send an API key as an Authorization Bearer header. A TrendsAGI account and API key are needed, and each call counts as one API request against the plan's daily allowance.
Installation
In SourceWeft
- Open TrendsAGI in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.TrendsAGI%2Ftrendsagi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"trendsagi": {
"type": "http",
"url": "https://api.trendsagi.com/mcp"
}
}
}README
TrendsAGI
[PyPI Version] [npm Version] [Python Versions] [License: MIT]
Real-time trend intelligence for your code and your AI agents: what is trending on social platforms right now, with measured volume, velocity and growth, AI insights on why each topic is moving, evidence-backed recommendations, crisis alerts and watchlists. Paid media and growth teams use it to target what is rising, time spend to the trend curve and brief creative on measured demand.
Install
Create an API key under Profile > API Keys at app.trendsagi.com and export it:
Quickstart
Command line
Every command has --help. In a terminal, lists print as tables; piped or with --json they print JSON, so trendsagi trends list | jq works. The key comes from --api-key, then TRENDSAGI_API_KEY, then the saved login. Commands that delete something or change live ads ask first; pass --yes in scripts. Exit codes: 0 success, 1 API error, 2 invalid usage, 4 missing or rejected key.
The commands are declared once in src/trendsagi/cli_spec.json; a dependency-free Node.js build of the same CLI lives in npm/ and is published as trendsagi on npm. Guide: trendsagi.com/api-docs/integrations/cli.
The client calls any endpoint too: client.request("GET", "/api/integrations/delivery/health", params={"lookback_hours": 24}).
Use TrendsAGI in your AI assistant (no install)
Add the hosted MCP server, sign in to TrendsAGI and approve the connection:
Then ask "What is accelerating fastest in Technology this week, and who should I target with it?" The hosted tools are read-only, and each call counts as one API request. Each connection gets its own key, listed as "AI connector: " under Profile > API Keys; delete it to disconnect. Clients without OAuth can send an API key as Authorization: Bearer <key>. Guide: trendsagi.com/mcp.
The hosted server also publishes the TrendsAGI paid-media skill over MCP (SEP-2640) at skill://trendsagi/SKILL.md. Clients that support the io.modelcontextprotocol/skills extension discover it with skills/list and load it with resources/read; the manifest carries a SHA-256 digest and byte size for every file. Clients without the extension still receive the server instructions and tool descriptions, and the plugin distributions keep a bundled copy of the skill.
Build an agent with Cursor Agent SDK
Agent SDK defines agents as a folder of Markdown and TypeScript. Add TrendsAGI with one file and the agent gets the hosted MCP server's read-only tools by name:
agent-sdk/ is a complete project to copy: instructions, a trend-brief skill, hosting settings (egress to api.trendsagi.com, a TRENDSAGI_API_KEY secret) and smoke evals. Guide: trendsagi.com/api-docs/integrations/agent-sdk.
Use TrendsAGI from your browser's agent (WebMCP)
WebMCP lets a web page hand tools to the AI agent built into the browser (Chrome and Edge in origin trials, ChatGPT desktop, Brave Leo). While you are signed in to app.trendsagi.com, the app registers TrendsAGI's read-only tools with document.modelContext, so the agent uses them with your session: no connector or API key, and calls count as app use rather than API usage. trendsagi.com offers public tools (docs search, trend reports, plans and the free calculators) to every visitor.
To put TrendsAGI tools on your own site, register them in your page and run them on your server, which keeps the API key:
webmcp/ has the browser module and a FastAPI server. Guide: trendsagi.com/webmcp.
Agent tools
One registry, every format. The tools are read-only by default; add_to_watchlist and update_recommendation appear only with allow_writes=True (or trendsagi mcp --allow-writes).
OpenAI
Claude, LangChain and others
With Claude, pass tools=tools.anthropic() and answer each tool_use block with {"type": "tool_result", "tool_use_id": block.id, "content": json.dumps(tools.call(block.name, block.input))}. tools.call never raises: errors come back as {"error": ...} so the model can read a rate limit or a bad argument and recover.
Local MCP server
Or in any MCP client's JSON config (Claude Desktop, Cursor, VS Code):
The local server publishes the same skill as the hosted endpoint, at
skill://trendsagi/SKILL.md, and declares the io.modelcontextprotocol/skills
extension. It is read from the installed package, so it stays in step with the
version of trendsagi you installed. Supporting references cover the tool
surface, paid-media workflow, read-only SQL and error handling.
Query with SQL
For answers no single endpoint returns, such as growth by category or the trends that match a watchlist:
Tables: trends, trend_snapshots (90 days of readings), trend_categories, trend_insights, watchlist, recommendations and crisis_events; the last three only contain your own account's rows. Queries are one validated SELECT, run read-only for at most 5 seconds, and count as one API request. A refused query raises exceptions.QueryError with a code (such as unknown_table or timeout), plus hint and position when known.
Recommendations with decision briefs
Each brief explains why an action is timely, the measured signals behind it and concrete next steps. Its confidence score measures evidence completeness, not the chance of success; use actionable and data_quality to hold back when signals are stale or incomplete.
Ad execution in your own infrastructure
GoogleAdsExecutor, MetaAdsExecutor, TikTokAdsExecutor and LinkedInAdsExecutor take credentials at runtime, use deterministic idempotency keys, and support dry-run previews and strict validation:
See INTEGRATIONS_BYOC.md for every executor.
Errors
Other commands
Plans and limits
The free Developer plan includes one API key and 100 API calls a day; Advantage, Scale and Enterprise raise the daily limit and add keys and team features. Calls above the daily allowance are billed as overage. See pricing.
Links
- API documentation and endpoint reference
- CLI guide
- MCP server guide and WebMCP guide
- Changelog
- Support: trendsagi.com/contact or [email protected]
License
MIT. See LICENSE.
Source: README.md at commit 278bc72
Tools
0Version history
3- v1.2.0LatestNov 7, 2026
- v1.1.1Nov 3, 2026
- v1.1.0Oct 13, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts