# Competitor Tracking Trends MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/trendsmcp-ai/Trends-MCP  
**GitHub Stars:** 44  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/competitor-tracking-trends-mcp-2

## Description
Brand and competitor trend volume over time, with growth signals. Free key at trendsmcp.ai

## Tools
Capabilities this server exposes over MCP:

- **get_time_series** — Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
- **get_growth** — Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
- **get_top_trends** — Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "competitor-tracking-trends-mcp": {
    "url": "https://api.trendsmcp.ai/mcp"
  }
}
```

## Documentation

## What Competitor Tracking Trends MCP does

Competitor Tracking Trends MCP MCP server gives AI agents access to trend measurements from Google, TikTok, YouTube, Amazon, Reddit, and more than 30 other sources. It is suited to brand monitoring, competitor research, market-signal checks, and questions about what is currently ranking on a platform.

The service exposes three MCP tools. `get_time_series` returns weekly or daily history for one keyword on one source. `get_growth` calculates point-to-point percentage change for a selected period, and can compare one keyword across multiple sources in a single call. `get_top_trends` returns a live ranked feed and does not accept a keyword.

## How it works

The hosted MCP endpoint is available at `https://api.trendsmcp.ai/mcp`. Requests use a Bearer API key, while the Claude.ai custom connector uses OAuth through `https://www.trendsmcp.ai/mcp`. The repository also includes a stdio adapter for local hosts and Glama. Local paid requests use the same service quota as hosted requests.

`get_time_series` requires both `keyword` and `source`, with one source per request. Its returned index ranges from 0 to 100 where the data pipeline supports normalization; some sources also provide absolute `volume` values. The REST API uses the same operation name through `mode`, with `get_trends` supported as an alias.

`get_growth` accepts presets such as `7D`, `30D`, `6M`, `12M`, `1Y`, `5Y`, `MTD`, `QTD`, and `YTD`, or custom recent and baseline dates. Multiple windows in one request still count as one request for the selected source and keyword. Its source parameter can contain a comma-separated list.

## Setup and configuration

Create an API key through the TrendsMCP account page before configuring clients. Hosted configurations generally send the key as `Authorization: Bearer YOUR_API_KEY`. The local stdio example uses the `TRENDSMCP_API_KEY` environment variable and starts with `python -m trends_mcp_server` after installing the package or repository.

The README documents configurations for Claude Code, Cursor, VS Code, Windsurf, Cline, and Claude Desktop. Claude Desktop requires the `mcp-remote` package because it does not provide native HTTP support. For Cline, the remote server type must be `streamableHttp`. Cursor uses an HTTP URL and headers, while Windsurf uses `serverUrl`.

## Tools and capabilities

- `get_time_series`: Retrieve weekly or daily history for one keyword and source.
- `get_growth`: Calculate percentage change over preset or custom comparison windows.
- `get_top_trends`: Read live rankings with optional limits, offsets, categories, and rank-change windows.

For MCP calls, `get_top_trends` requires a `type` value that exactly matches the feed name, including capitalization. It supports ranking or rank-change sorting, with rank-change windows from one to 30 days. The default result limit is 25 and the maximum is 200.

## Limitations and notes

Source-specific keyword formats apply, so a keyword valid for one source may require a different format elsewhere. `get_time_series` handles only one source per call. `get_top_trends` is feed-based rather than keyword-based, and some feed types require a category. On the REST API, leaving out `type` requests every feed and is billed per feed.

The free tier shown in the repository allows 100 requests per month. The service states that normalized 0–100 values are available only where the pipeline supports them, and absolute volume is not present for every source. Use the exact feed names and source catalog values documented by the service.

_Full upstream README: https://allmcps.com/mcp/competitor-tracking-trends-mcp-2/readme_