MaxStat MCP Server

If you already use MaxStat MCP, the maxstat mcp mcp server is the piece that lets your assistant work with it directly. Search and analyze channels, posts, audience growth, views, and engagement in the MAX messenger.

What the server does

Разработчик и оператор: ООО «ФБМ Аналитикс» / FBM Analytics.

• Search and filter MAX channels and publications
• Retrieve channel profiles, audience growth, views, reactions, activity, and
• Retrieve post text, attachments, metrics, reaction details, histories, and
• Create and manage channel or keyword webhook subscriptions
• Inspect the active MaxStat plan, credit balance, and request-level usage

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Endpoint — https://maxstat.ru/api/mcp
• Cursor — Установка по ссылке или ~/.cursor/mcp.json
• Windsurf — ~/.codeium/windsurf/mcp_config.json
• Cline — Удалённый Streamable HTTP из llms-install.md
• get_categories — Категории и актуальное количество каналов в каждой категории
• search_channels — Отфильтрованные, отсортированные и постраничные карточки каналов
• get_channel — Полная карточка одного канала по идентификатору
• add_channel — Добавляет публичный или invite-only канал в очередь
• search_posts — Отфильтрованные, отсортированные и постраничные публикации
• get_channel_subscribers — Минимум, максимум, абсолютный и процентный рост и дневную историю
• get_channel_views — Суммарные, средние и максимальные просмотры и дневную историю
• get_channel_likes — Суммарные, средние и максимальные реакции и дневную историю

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: MAXSTAT_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MaxStat MCP's toolset — Endpoint, Cursor, Windsurf and 11 more — is a fair guide to whether it matches your workflow. It is maintained by fbmdata; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MaxStat MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.