Spot keyword demand rising or fading across search and social. Free key at trendsapi.ai
Spot keyword demand rising or fading across search and social. Free key at trendsapi.ai. Exposed over MCP by the seo trends api mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The same API key powers the Trends API MCP server, so Claude, Cursor, VS Code, ChatGPT and any MCP-compatible client can query this data in natural language.
Everything the assistant can do here goes through one of these:
get_trends — Historical trend series for a keyword on one of 15 sourcesget_growth — Growth % over 3M / 6M / 12M / 5Y windowsget_top_trends — 21 live trending feeds (Google, TikTok, YouTube, X, Reddit, Amazon, Steam, Spotify...)Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: AUTH_HEADER, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. SEO Trends API's toolset — get_trends, get_growth, get_top_trends — is a fair guide to whether it matches your workflow. It is maintained by ai.trendsapi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against SEO Trends API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_trends | Historical trend series for a keyword on one of 15 sources |
| get_growth | Growth % over 3M / 6M / 12M / 5Y windows |
| get_top_trends | 21 live trending feeds (Google, TikTok, YouTube, X, Reddit, Amazon, Steam, Spotify...) |
{
"mcpServers": {
"trendsapi": {
"url": "https://api.trendsapi.ai/mcp",
"transport": "http",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTH_HEADER | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.