Spotify Trends API MCP server
Commit Nov 3, 2026Access Spotify podcast trends, listening signals, and historical growth data through an AI client.
Also known as trendsapi-ai/trends-mcp, spotify
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 1.0.2
- Last commit
- Nov 3, 2026
- License
- MIT
What is Spotify Trends API MCP?
Spotify Trends API accesses Spotify podcast trends, listening signals, and historical growth data through an AI client. It exposes 6 tools, such as get_time_series, get_growth, get_top_trends.
Summary generated from the project's README
About Spotify Trends API MCP server
Analyzing Spotify podcast trends and listening signals through an AI client allows developers to track audience growth and content popularity. This remote MCP server provides access to historical data and live ranked boards using specific tools like get_top_trends and get_time_series. Users can retrieve approximately five years of weekly history for specific keywords or calculate percent changes over various windows with the get_growth tool.
Setting up the server requires an authorization token from a trendsapi.ai account. It can be integrated into Cursor or VS Code via JSON configuration files using HTTP transport. For Claude Desktop, users run a command through npx to connect to the remote endpoint. The server also includes a get_usage tool to monitor request limits and plan details. While most features work with standard authentication, accessing top posts for TikTok or Instagram hashtags requires a Business plan.
What you can do with it
- 1Monitor live trending contentView a live ranked board of current trends to see what is popular right now.
- 2Manage API consumptionCheck how many requests remain in the current billing cycle and when the plan resets.
Written from the project's README. Every use case is checked against a quote from it.
How to install Spotify Trends API MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Spotify Trends API MCP in Claude Code
$ claude mcp add --transport http spotify https://spotify.api.trendsapi.ai/mcpInstall Spotify Trends API MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"spotify": {
"url": "https://spotify.api.trendsapi.ai/mcp"
}
}
}Install Spotify Trends API MCP in VS Code
.vscode/mcp.json
{
"servers": {
"spotify": {
"type": "http",
"url": "https://spotify.api.trendsapi.ai/mcp"
}
}
}Install Spotify Trends API MCP in VS Code CLI
$ code --add-mcp '{"name":"spotify","type":"http","url":"https://spotify.api.trendsapi.ai/mcp"}'Install Spotify Trends API MCP in Codex
$ codex mcp add spotify --url https://spotify.api.trendsapi.ai/mcpInstall Spotify Trends API MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.spotify] url = "https://spotify.api.trendsapi.ai/mcp"
Install Spotify Trends API MCP in Gemini CLI
$ gemini mcp add -s user --transport http spotify https://spotify.api.trendsapi.ai/mcpInstall Spotify Trends API MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"spotify": {
"url": "https://spotify.api.trendsapi.ai/mcp",
"type": "http"
}
}
}Spotify Trends API MCP tools 6
Detected from the READMEget_time_seriesget_growthget_top_trendsget_contextget_top_postsget_usage
Configuration
AUTH_HEADER
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletrendsapi-ai/trends-mcp is public and reachablegithub.com/trendsapi-ai/trends-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-03github.com/trendsapi-ai/trends-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-03-26 in 255 msPass
README
View on GitHubRemote MCP server
Hosted MCP at https://api.trendsapi.ai/mcp. Same five operations and catalogs as REST, plus a free get_usage. Token: trendsapi.ai/account.
REST contract: trendsapi-ai/trendsapi.
Tools
| MCP tool | REST mode |
Required | Returns |
|---|---|---|---|
get_time_series |
get_time_series |
source, keyword |
About 5 years of weekly history |
get_growth |
get_growth |
source, keyword |
Percent change over one or more windows |
get_top_trends |
get_top_trends |
type |
Live ranked board |
get_context |
get_context |
source, keyword |
Posts, videos, stories and comments about a keyword right now |
get_top_posts |
get_top_posts |
source, keyword |
Top posts for a hashtag on TikTok or Instagram (Business plan) |
get_usage |
(MCP only) | none | Plan, requests used and left, reset date. Free |
Sources, feeds, and keyword formats: hub keyword sources and live boards.
App Downloads / App Rankings need an Android bundle ID (com.openai.chatgpt).
Cursor
~/.cursor/mcp.json:
{
"mcpServers": {
"trend-feeds": {
"url": "https://api.trendsapi.ai/mcp",
"transport": "http",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
VS Code
.vscode/mcp.json:
{
"servers": {
"trend-feeds": {
"type": "http",
"url": "https://api.trendsapi.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
Claude Desktop
{
"mcpServers": {
"trend-feeds": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.trendsapi.ai/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer YOUR_TOKEN" }
}
}
}
Claude.ai and ChatGPT sign in with OAuth, no token: add https://trendsapi.ai/mcp as a custom connector (Claude: Settings → Connectors → Add custom connector; ChatGPT on the web: Plugins → + → Add custom MCP server, authentication OAuth).
No local production server in this repo.
License
MIT. See LICENSE.
Spotify Trends API MCP questions
How do I add Spotify Trends API MCP to Claude Code?
Run claude mcp add --transport http spotify https://spotify.api.trendsapi.ai/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Spotify Trends API MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Spotify Trends API MCP provide?
It exposes 6 tools, including get_time_series, get_growth, get_top_trends, get_context, get_top_posts.
How can I check my API usage?
You can use the get_usage tool which is exclusive to MCP to view your plan, requests used and remaining, and your reset date.
What is required to track App Downloads or App Rankings?
You must provide an Android bundle ID for these specific queries.