Misar.Blog MCP Server vs Yandex Metrica MCP
A side-by-side look at the Misar.Blog MCP Server and Yandex Metrica MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Misar.Blog MCP Server for marketing work as a local process; choose Yandex Metrica MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Misar.Blog MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MISARBLOG_API_KEY, MISARBLOG_BASE_URL. - You want tools like
login, status, upgrade.
Choose Yandex Metrica MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YANDEX_METRIKA_COUNTER_ID. - You want tools like
login, submit_code, get_metadata.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 64/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MISARBLOG_API_KEYMISARBLOG_BASE_URL | YANDEX_METRIKA_COUNTER_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 15 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 26 | 12 |
| Full listing | View Misar.Blog MCP Server | View Yandex Metrica MCP |
Tools & capabilities
Misar.Blog MCP Server tools 26
loginAuthenticate with your Misar.Blog account via browser — no API key copy-paste needed. Opens the Misar.Blog authorization page where you review the requested permissions and click 'Authorize'. Your API key is delivered straight back to this client and saved to ~/.misarblog/config.json.statusCheck whether you are authenticated with Misar.Blog and which account is connected. Run this first to verify your connection.upgradeShow your current Misar.Blog plan, how much of each quota you have left, and what upgrading unlocks, with the link to upgrade. Call it any time — not only after hitting a limit. Reads only: it never changes the plan or takes payment; the user upgrades by following the link. On a local install, open=true also opens that link in the user's browser.get_profileGet your Misar.Blog creator profileget_analytics_summaryGet analytics summary (views, revenue, subscribers) for a time periodlist_my_articlesList your articles on Misar.Blogget_articleGet a single article by slug, including full markdown contentpublish_articlePublish a new article (or schedule it) on Misar.Blogcreate_draftSave an article as a draft on Misar.Blog (for review before publishing)update_articleUpdate the title, body, or tags of an existing article or draft. Only the fields you pass are changed; omitted fields keep their current values.search_articlesSearch PUBLISHED articles across Misar.Blog by keyword, tag, or author — including other creators' work. Use list_my_articles for your own drafts and unpublished posts.research_topicResearch a topic and get AI-generated insights, sources, and a content outline. Useful before writing an article.- +14 more on the listing page
Yandex Metrica MCP tools 12
loginSign in to Yandex from here. Opens your browser to approve access; the code returns automatically over a local redirect, so this usually finishes in one call. If the local port is unavailable it returns a URL to approve and you then call submit_code with the code Yandex shows. Run this once (the token lasts ~1 year); needed before the data tools if you are not signed in yet.submit_codeComplete a copy-paste sign-in started by login: pass the code Yandex showed you after you approved access.get_metadataDiscovery tool. Lists the counters available to your token plus a curated catalog of common dimensions and metrics (Metrica has no enumeration API), attribution options and Logs API fields. Call this before run_report or logs_request to use real field names and to find a counterId. For a counter's own goals, segments, filters or grants, use describe_counter. Read-only.describe_counterRead a single counter's configuration — settings, goals, segments, filters, operations and access grants — choosing sections with `include`. The goals section returns the goal ids needed to build conversion metrics (ym:s:goal<id>reaches / conversionRate) in run_report, so call this with include=["goals"] before any conversion question. To list the account's counters, use get_metadata. Read-only.run_reportQuery a Yandex Metrica table report (/stat/v1/data): one or more metrics grouped by dimensions over a date range, with optional filter and sort. Read-only. Use get_metadata first to discover valid metric/dimension ids and the account counters.run_comparisonCompare two segments/periods (A vs B) for the same metrics and dimensions (/stat/v1/data/comparison). Returns per-metric values for A and B plus the absolute and percentage delta, computed server-side: delta = B − A (segment A is the baseline), delta_pct = (B − A) / A × 100. Defaults to last 7 days (B) vs the prior 7 days (A), so a positive delta means growth. Read-only.run_drilldownReturn one level of a hierarchical (tree) report (/stat/v1/data/drilldown). Each row has an "expandable" flag; pass parentId with the path of dimension keys to expand deeper. Requires dimensions. Read-only.run_timeseriesReturn metrics split into a time series (/stat/v1/data/bytime): each metric comes back as an array of values, one per interval (day/week/month/…) over the date range. Use for trends and charts. Optionally group by dimensions (topKeys rows). Read-only.logs_requestCreate a Yandex Metrica Logs API request for RAW, un-sampled rows (source="visits" sessions or "hits" events) over a date range. Checks feasibility, then queues preparation (takes minutes). Returns a request_id to poll with logs_status; then logs_download, then logs_clean. Discover field ids with get_metadata. Not read-only: preparing data consumes the counter storage quota.logs_statusInspect a Logs API request by request_id (status, parts, size, next step), or omit request_id to list all of the counter's log requests and current storage-quota usage. Poll this after logs_request until status="processed". Read-only.logs_downloadDownload prepared log data for a request_id (must be status="processed"; check logs_status). Default mode "sample" returns up to maxRows parsed rows inline — cheap and bounded. Mode "file" streams the FULL export to a file and returns its path plus a small preview; the raw content (potentially millions of rows) is never loaded into context. Read-only.logs_cleanFree the counter storage quota by cleaning a finished (processed) log request, or cancel one still being prepared. Dispatches by current status. Destructive: cleaned data must be requested again to download later.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Misar.Blog MCP Server
{
"mcpServers": {
"misar-blog-mcp-server": {
"command": "npx",
"args": [
"-y",
"@misarblog/mcp@latest"
],
"env": {
"MISARBLOG_API_KEY": "YOUR_MISARBLOG_API_KEY_HERE",
"MISARBLOG_BASE_URL": "YOUR_MISARBLOG_BASE_URL_HERE"
}
}
}
}
Yandex Metrica MCP
{
"mcpServers": {
"yandex-metrica-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-metrica-mcp"
],
"env": {
"YANDEX_METRIKA_COUNTER_ID": "YOUR_YANDEX_METRIKA_COUNTER_ID_HERE"
}
}
}
}
Frequently asked questions
Misar.Blog MCP Server is categorized under Marketing and uses a local stdio subprocess. Yandex Metrica MCP belongs to Marketing and uses a local stdio subprocess. Pick Misar.Blog MCP Server for marketing work and Yandex Metrica MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Misar.Blog MCP Server has no declared pricing — check the project's own site. Auth: api key required. Yandex Metrica MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add misar-blog-mcp-server and yandex-metrica-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Misar.Blog MCP Server has a quality signal of 64/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Yandex Metrica MCP has 64/100 (Good) with 2 views, 0 installs and 15 GitHub stars.