# Competitor Tracking API [Health: Active]

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

## Description
Track competitor brand demand across search, social and news. Free key at trendsapi.ai

## 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-api": {
    "url": "https://api.trendsapi.ai/mcp"
  }
}
```

## Documentation

## What Competitor Tracking API MCP server does

The Competitor Tracking API MCP server gives MCP-compatible clients access to trend data from the hosted Trends API. It is intended for tracking demand around competitor brands and other keywords across the service's supported sources, including search, social, and news data described by the listing.

The server exposes three operations:

- `get_trends` returns weekly historical data for a supplied source and keyword.
- `get_growth` returns percentage change for a supplied source and keyword.
- `get_top_trends` returns a live ranked feed selected by a feed type.

The MCP operations map to the REST API modes `get_time_series`, `get_growth`, and `get_top_trends`. Source names, feed types, and accepted keyword formats come from the linked Trends API catalogs rather than being defined in this repository.

## How it works

The Competitor Tracking API MCP server is hosted at `https://api.trendsapi.ai/mcp`. Clients connect over HTTP and send an `Authorization` bearer token with requests. A token can be obtained from the Trends API website; the repository describes this as a free key.

Tool calls require different inputs. Trend history and growth queries need both `source` and `keyword`. Ranked-feed requests need a `type` value. The service returns the corresponding history, percentage-change result, or live ranking feed.

Because the repository provides a remote endpoint, there is no local production server to build or run. The REST contract is maintained separately in the linked `trendsapi` repository.

## Setup and configuration

Configure the hosted endpoint directly in clients that support remote HTTP MCP servers. Cursor uses `~/.cursor/mcp.json` with an HTTP server entry, while VS Code uses `.vscode/mcp.json` with a server of type `http`. Both configurations include the endpoint URL and an `Authorization` header containing the bearer token.

Claude Desktop can connect through `mcp-remote` with the endpoint passed as an argument and the authorization header supplied through an environment variable. Claude.ai supports adding the same endpoint as a custom connector under Settings, Connectors, and Add custom connector.

Keep the token out of source-controlled configuration files where possible. The examples use `YOUR_TOKEN` as a placeholder and `AUTH_HEADER` for the Claude Desktop environment value.

## Tools and capabilities

The Competitor Tracking API MCP server supports these capabilities:

- Retrieve weekly time-series history with `get_trends`.
- Calculate percentage change with `get_growth`.
- Read live ranked trend feeds with `get_top_trends`.
- Select supported sources, feeds, and keyword formats documented by the Trends API catalogs.
- Query app downloads or app rankings when an Android bundle ID is supplied, such as `com.openai.chatgpt`.

## Limitations and notes

The Competitor Tracking API MCP server requires a valid bearer token and access to the hosted Trends API endpoint. The repository does not include a local production implementation. Tool coverage depends on the sources and feeds supported by the linked REST API, so callers should consult those catalogs before constructing requests.

App download and app ranking queries require an Android bundle ID. A brand name alone is not sufficient for those request types. The repository is licensed under MIT.

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