Lolik Trend Radar MCP Server

Live trends → money-ready intelligence: forecasts, virality scores, opportunities, daily briefs.

Local serverstdio

What is the Lolik Trend Radar MCP server?

Lolik Trend Radar MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Live trends → money-ready intelligence: forecasts, virality scores, opportunities, daily briefs.

What you get

The Lolik Trend Radar MCP server — live trend → money-ready intelligence as MCP tools for Claude (Desktop / Code), Cursor and any MCP client. No repo clone, no build: run it with npx. Every tool call uses your Lolik API key, so auth, credits and rate limits apply — the same metered API as REST.

What the assistant can call

Once Lolik Trend Radar is connected, these are the calls the assistant has available:

  • get_trends — Top trending topics by niche
  • forecast — Timing / momentum / lifecycle for a topic
  • virality_score — Virality score + breakout probability + hook type
  • get_news — Freshest news stories
  • opportunities — Ranked opportunities + possible monetization
  • get_brief — Daily what-to-post brief: phased alerts + receipts + pattern + mover
  • rescue_hooks — Hooks for your topic from live validated title patterns, with measured proof
  • grade_draft — Grade a draft title against this week's validated patterns (score math in code)
  • prebreakout — What's accelerating now, pre-peak
  • get_viral_patterns — Validated viral patterns (what's working now)
  • get_usage — Credits + rate-limit status
  • lolik_content_brain — One-call brief: trends + opportunities + forecast

Configuration and credentials

You will need 2 environment variables: LOLIK_API_KEY, LOLIK_API_BASE_URL. 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.

Setting it up

Installation goes through your MCP client rather than a global install: point it at @lolikai/mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Lolik Trend Radar's toolset — get_trends, forecast, virality_score and 9 more — is a fair guide to whether it matches your workflow. It is maintained by lolikai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Lolik Trend Radar's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lolik Trend Radar.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the lolik trend radar mcp server does with a few real requests.

Available tools

ToolWhat it does
get_trendsTop trending topics by niche
forecastTiming / momentum / lifecycle for a topic
virality_scoreVirality score + breakout probability + hook type
get_newsFreshest news stories
opportunitiesRanked opportunities + possible monetization
get_briefDaily what-to-post brief: phased alerts + receipts + pattern + mover
rescue_hooksHooks for your topic from live validated title patterns, with measured proof
grade_draftGrade a draft title against this week's validated patterns (score math in code)
prebreakoutWhat's accelerating now, pre-peak
get_viral_patternsValidated viral patterns (what's working now)
get_usageCredits + rate-limit status
lolik_content_brainOne-call brief: trends + opportunities + forecast

How to install the Lolik Trend Radar MCP server

{
  "mcpServers": {
    "lolik": {
      "command": "npx",
      "args": ["-y", "@lolikai/mcp"],
      "env": {
        "LOLIK_API_KEY": "your-value",
        "LOLIK_API_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LOLIK_API_KEYCredential the server authenticates with.Yes
LOLIK_API_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Lolik Trend Radar to get trends.
  • Use Lolik Trend Radar to forecast.
  • Use Lolik Trend Radar to virality score.

Frequently asked questions

It connects Lolik Trend Radar to MCP-compatible AI assistants such as Claude and Cursor, exposing 12 tools (get_trends, forecast, virality_score, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lolik Trend Radar directly.