Roistat MCP
MCP server for Roistat: end-to-end analytics reports, period comparison, orders, calls and visits with personal data masked
Install
git clone https://github.com/zai-one/roistat-mcp.git
cd roistat-mcp
uv sync --frozen
uv run --frozen python scripts/configure.py
uv run --frozen roistat-mcp --config mcp.local.json --check-configRequires Python 3.12-3.14 and uv. The wizard asks for the API key and project IDs.
This is third-party code. Review the repository files before installing.
What it does
The server exposes Roistat data for the projects you allow in the config. The agent gets analytics reports with attribution models, compares periods, and reads orders, statuses, leads and funnel data, plus calltracking, visits, clients and duplicate leads. Phone numbers, emails and visitor IPs are masked in supported responses. Report bundles cover one or two periods with provider totals, exact request parameters and JSON or CSV export. Writing to Roistat is off by default and needs separate configuration.
Who it is for. For marketers and analysts who study how ad spend relates to sales in Roistat.
Good fit when
- You need to understand why leads or revenue dropped this week
- You need to compare two periods on cost, leads and sales
- You need a report with reproducible parameters for a team or client
Not a fit when
- Your project is not on Roistat
- You need bulk CRM data changes: the server is read-oriented
Example request
Compare last week with the week before for my project: cost, leads, sales and revenue. Separate data-backed changes from hypothesesLimitations
Requires a Roistat API key and project IDs. Needs Python 3.12-3.14 and uv; there is no PyPI package, it runs from a cloned repository or release archive. The license is proprietary, not open source: use is allowed for your own accounts. Reports use a fixed metric list, and an empty response does not mean zero activity.
How to disable. Remove the roistat block from your MCP client config and delete the roistat-mcp folder with its local key files.
MCP
- Transport
- stdio, http
- Authentication
- API key
Security check
- Reads CRM and call data; some personal fields may remain unmasked
- Stores the Roistat API key locally
README in short
The README, in English and Russian, describes what the server covers: reports, funnel, calls and visits, and report bundles. Quick start is a clone, uv sync and the configure.py wizard with a config check. It gives an mcpServers block for Claude Desktop and Cursor and a first test prompt. An authenticated HTTP mode exists for server deployments. Built by the ZAI.ONE agency under its own license.
FAQ
Can the agent change anything in Roistat?
Not by default. Data changes need separate configuration and approval.
Where is the key stored?
The setup wizard stores secrets in private local files and refuses to overwrite an existing config.
Related
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents
A Claude Code skill set for auditing sites for AI search: citability, AI crawler access, llms.txt, schema and reports
The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request
Google Search Console MCP
Google Search Console MCP Server for SEOs
An MCP server for Google Search Console: queries and pages with clicks and positions, URL indexing checks, sitemaps and ready SEO skills