Roistat MCP 0.6.0

• Optional lazy tool loading (ROISTAT_TOOL_LOADING=eager|lazy, default eager = unchanged): lazy lists a small core plus roistat_enable_toolsets (toolsets with one-line description and token cost); enabling registers the tools at runtime and sends notifications/tools/list_changed. Allowlists, read-only mode and approval gates still apply. Setup wizard asks eager vs lazy. Startup tokens (tools/list + instructions, ≈chars/4): eager ≈5164, lazy ≈1435. Scope: enablement is per MCP session (FastMCP session visibility), so one client's enabled toolsets never appear for another. The HTTP transport here is stateless (every request is its own session), so enabled toolsets do not persist there: for shared HTTP use eager or ROISTAT_TOOLSETS. README lazy section lists verified tools/list_changed client support with sources.
• Opt-in toolset extras (not in default; default tool list and token budget unchanged): roistat_extra_read reads calltracking scripts, the phone pool, the events log (filters) and one client's activity feed (GET /project/clients/detail/feed?client=); PII redacted.
• roistat_prepare_write / roistat_apply_write add documented calltracking script create/update/delete, phone create/update/delete and events send/bulk send/add; deletes act on one object and need confirm_delete; same operator acceptance. They are off unless named in ROISTAT_WRITE_OPERATIONS (unset keeps the original four), so upgrading never widens an existing write deployment. Readback after apply: script/phone list lookup, or verified: false for events and new phones (no per-object readback), instead of failing an applied write. Script create/delete were previously listed as unsupported by mistake. Phone purchase is not in the public API.
• Security: calltracking forwarding values (options.redirect.value: phone, external SIP account or Roistat SIP password) and client-feed lead_hunter_* contacts (field = entered phone, name) are now redacted in roistat_extra_read, calltracking write responses, readback and stored write results.
• Fix: calltracking delete readback reports verified: true, deleted: true only when the listing provably covers every object; an empty, malformed or partial listing gives verified: false, deleted: null.
• Fix: a provider 429 during post-write readback now records the Retry-After cooldown; the applied write is still returned with an unverified readback.
• Fix: the lazy-loading fallback hint and README no longer suggest reconnecting (a new session drops toolsets enabled in the old one); use eager or ROISTAT_TOOLSETS.
• Default toolsets no longer mean "all": unset ROISTAT_TOOLSETS = default (everything except opt-in extras).
• Router generated from intents (tool; skill; roistat://guide/<topic>), fallbacks roistat://playbook and roistat://guide/tool-map.
• tests/test_routing_eval.py + tests/evals/routing_cases.json (24 RU/EN requests incl. paraphrases and negative cases).

Source: d611bf6 · Changes: v0.5.0...v0.6.0

Roistat MCP 0.5.0

• License: LicenseRef-ZAI-ONE 2.0 (source-available). Free install and use for yourself and your organisation, including commercial work; issues and pull requests welcome; copying code into other projects, redistribution, embedding and competing hosted services need written permission. Earlier releases keep their LicenseRef-ZAI-ONE 1.0 terms (see NOTICE). README first screen: one-line scope, why this MCP, maintenance and update check.

• Agent layer: router instructions (≤1200 chars; describes prepare → operator accept → apply), compact template descriptions and titles on all 28 tools.

• Toolsets meta, analytics, orders_visits, calls, settings_write (ROISTAT_TOOLSETS, ROISTAT_TOOLS, ROISTAT_DISABLED_TOOLS, ROISTAT_READ_ONLY=1); roistat://toolsets. All toolsets stay enabled by default, so existing setups keep every tool.

• format="markdown_table" on roistat_analytics_report and roistat_analytics_compare (unknown values stay blank).

• Resources roistat://playbook, roistat://guide/{metrics,dimensions,errors}; prompts channel_report, period_compare.

• Self-contained skills roistat-channel-roi, roistat-lead-audit, roistat-write-safe; Claude Code plugin manifest, Cursor rule, .agents/skills.

• scripts/token_budget.py + tests gate instruction, description and SKILL.md sizes.

• Install snippets in the Claude Code plugin manifest and README pin git+https://github.com/zai-one/roistat-mcp@v0.5.0 instead of the moving default branch.

Roistat MCP 0.4.0

• roistat_health_indicators: official project-state processes (GET /project/health/indicator/list), read-only.
• roistat_list_channels and roistat_list_channel_costs: advertising channels and manually entered costs
  (/project/analytics/source/list, /project/analytics/source/cost/list), bounded locally.
• roistat_list_managers: CRM managers (/project/integration/manager/list) with email and phone redacted.
• roistat_check_update: suggests a newer GitHub release with its notes link and update command;
  public API, 3 s timeout, 24 h cache, graceful offline, never auto-updates. A cached
  "update available" hint appears in server instructions and roistat_health.
  Opt out with ROISTAT_DISABLE_UPDATE_CHECK=1.
• Update check hardening: only plain version tags (v1.2.3) are accepted, from GitHub and from the
  cache; anything else is treated as no release and never reaches versions, commands or instructions.
  Every attempt is recorded: after a failure no new request for 30 minutes, force=true at most once
  a minute; the startup refresh follows the same rules. The clean-install gate and tests disable it.
• roistat_health_indicators tolerates odd provider values (unknown state instead of an error) and
  truncates names and messages to 500 characters.
• MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) on every tool.
• Capability matrix lists the indicator, channel and manager sections; their write methods stay closed.

English setup · Описание по-русски

Download the wheel or source archive below and verify SHA256SUMS. The installed setup
command generates local JSON/TOML client configuration; a source checkout is optional.
Your own provider credentials and API permissions remain required.

Verified on Python 3.12, 3.13 and 3.14 on Linux and Windows: existing contracts,
synthetic functional tests, clean wheel installation and real MCP stdio checks.
Live provider accounts and production deployment were outside this release verification.
GitHub verification · Source commit e491ae1068725400f799a73b052fce1208167a12.

ZAI.ONE is a digital agency for websites, SEO, advertising and analytics.
ZAI.ONE — интернет-агентство: сайты, SEO, реклама и аналитика.
Contact / Написать в Telegram about setup and integration.

LicenseRef-ZAI-ONE permits installation and internal use on your own or authorized
accounts; it is not an open-source license. Third-party rights remain unchanged.
Stars are welcome. Request changes through Issues.

Roistat MCP 0.3.0

• Analytics bundles for one or two periods: provider totals by interval, attribution, explicit missing values, request replay and response digests.
• Bounded local row slices and JSON/CSV exports, preserving project authorization and cleaning supported personal fields before export.
• Installable setup wizard and JSON/TOML client snippets that work outside the checkout.
• English and Russian agency information, integration contact and package installation guide.

English setup · Описание по-русски

Download the wheel or source archive below and verify SHA256SUMS. The installed setup
command generates local JSON/TOML client configuration; a source checkout is optional.
Your own provider credentials and API permissions remain required.

Verified on Python 3.12, 3.13 and 3.14 on Linux and Windows: existing contracts,
synthetic functional tests, clean wheel installation and real MCP stdio checks.
Live provider accounts and production deployment were outside this release verification.
GitHub verification · Source commit 640860cb522b4bf5dd96e2414e844a6c7bdb4114.

ZAI.ONE is a digital agency for websites, SEO, advertising and analytics.
ZAI.ONE — интернет-агентство: сайты, SEO, реклама и аналитика.
Contact / Написать в Telegram about setup and integration.

LicenseRef-ZAI-ONE permits installation and internal use on your own or authorized
accounts; it is not an open-source license. Third-party rights remain unchanged.
Stars are welcome. Request changes through Issues.

Roistat MCP 0.2.0

Install Roistat MCP on your own computer or server and connect an MCP client.

• Quick start and installation guide.
• Changes in 0.2.0.
• Python 3.12, 3.13 and 3.14 verified on Linux and Windows. Clean wheel installation, real stdio discovery and source-distribution builds passed using synthetic fixtures.
• Provider credentials and API access remain required. Live provider validation is an operator step.
• Proprietary LicenseRef-ZAI-ONE: install and use for your own or authorized accounts. Separately identified third-party licenses remain unchanged. Stars welcome; request improvements through Issues.

Download the wheel or source archive below; verify it against SHA256SUMS.
Exact source commit: dfcb2440473a0f974fdaa4bb839d303741c2c84e. Verification run.