Misar.Blog MCP Server

Official23 toolsLive

by Misar-AI · TypeScript

Publish and manage articles, series, comments, reactions, newsletters and blog analytics.

io.github.Misar-AI/misarblog-mcp — Misar.Blog MCP Server

The Misar.Blog MCP server publishes and manages blog content including articles and series, plus comments, reactions, and newsletters. It also provides blog analytics, designed to run from any AI assistant. It supports MCP with 23 tools and additional prompts and resources.

🛠️ Key Features

Publish and manage articles
Manage series
Handle comments and reactions
Manage newsletters
Provide blog analytics
23 tools, 8 prompts, 5 resources, 6 agent skills
Works with Claude, Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, and ChatGPT

🚀 Use Cases

Article and series publishing from an AI assistant
Moderation-style workflows for comments and reactions
Newsletter management
Using blog analytics as part of content workflows

⚡ Developer Benefits

MCP server integration for content-publishing tasks
Tool coverage spanning publishing, engagement, newsletters, and analytics
TypeScript-based package ecosystem (as referenced in repo/publish context)

⚠️ Limitations

Scope is limited to blog publishing/management, engagement, newsletters, and analytics (no other domains indicated).

Topics

bloggingmcpmisar-blogai-agentanalyticsnewslettercrewailangchainmcp-serveraicontent-managementmodel-context-protocolpublishingtypescriptwritingai-writingclaudecontent-publishingcursorseo

Captured live from the server via tools/list.

upgrade

Show the account's current plan, how much of each quota remains, and what a higher plan unlocks. Called with no arguments it only reads — useful any time, not just after hitting a limit, and the natural follow-up when a write tool reports a quota error. Two arguments make it act rather than report, so pass them only on explicit instruction from the user: `start_trial` ENROLS the account in the free trial immediately (a real account change, not a preview), and `open` LAUNCHES a checkout page in the user's browser. Neither charges a card by itself. Requires an API key. No billing state changes unless you pass start_trial; the returned quota snapshot already reflects a trial started in the same call. For whether you are authenticated at all, use `status`.

Parameters3

open	boolean	optional	Open the checkout page in the user's default browser. Side effect on their desktop — only when they asked to upgrade.
plan	string	optional	Plan slug to open, e.g. 'pro' or 'business'. Defaults to the recommended plan. Only meaningful with open=true.
start_trial	boolean	optional	Enrol in the free no-card trial now, if eligible. This changes the account's plan — do not set it speculatively.

Raw schema

{
  "type": "object",
  "properties": {
    "open": {
      "type": "boolean",
      "description": "Open the checkout page in the user's default browser. Side effect on their desktop — only when they asked to upgrade."
    },
    "plan": {
      "type": "string",
      "description": "Plan slug to open, e.g. 'pro' or 'business'. Defaults to the recommended plan. Only meaningful with open=true."
    },
    "start_trial": {
      "type": "boolean",
      "description": "Enrol in the free no-card trial now, if eligible. This changes the account's plan — do not set it speculatively."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_profile

Fetch the authenticated account's own creator profile: id, username, display name, bio, public profile URL, and whether Stripe payouts are connected. Use it to confirm which account a key belongs to before acting on that account's behalf, to get your own profile id for tools that take a UUID, or to check stripe_connected before discussing paid posts. It only ever describes the caller — there is no tool here for looking up someone else's profile. Reads only; nothing is modified. Requires an API key, and takes no parameters. Errors if the key is missing or invalid, which is the quickest way to test authentication.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_analytics_summary

Summarise the account's performance over a trailing window: page views, gross and net revenue, and active subscriber count. Use it for 'how did I do this month' style questions. These are whole-account totals — it cannot break results down per article, and it covers a trailing window ending today rather than an arbitrary date range. Reads only. Requires an API key. Revenue is returned in cents (revenue_cents gross, revenue_net_cents after fees) with a formatted revenue_usd added for convenience — read the cents fields when doing arithmetic. Zero views is a real answer, not an error.

Parameters1

days

integer

optional

Size of the trailing window in days, ending today. 1-365, defaults to 30. Use 7 for a week, 365 for a year.

Raw schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 365,
      "default": 30,
      "description": "Size of the trailing window in days, ending today. 1-365, defaults to 30. Use 7 for a week, 365 for a year."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_my_articles

List articles owned by the authenticated account, newest first, including drafts and scheduled posts. Use this to find your own work — it is the only listing that sees unpublished content. To search across the whole site, including other creators, use search_articles instead. Reads only; nothing is created or modified. Requires an API key. Returns `{ articles, total }`, where each article carries id, slug, title, status, url, editor_url, tags and timestamps, but NOT the article body — call get_article for that. `total` counts all matches, not just the page returned.

Parameters2

status	string	optional	Return only articles in this state. Omit to return every state the account owns.
limit	integer	optional	Maximum articles to return, 1-100. Defaults to 20.

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "draft",
        "published",
        "scheduled",
        "archived"
      ],
      "description": "Return only articles in this state. Omit to return every state the account owns."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 20,
      "description": "Maximum articles to return, 1-100. Defaults to 20."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_article

Fetch a single article by slug, including its full Markdown body. Use this after list_my_articles or search_articles has given you a slug and you need the actual content — for reading, editing, or repurposing it. Fetching one article at a time is deliberate: the listing tools omit bodies so they stay cheap. Reads only; nothing is created or modified. Requires an API key for unpublished articles; published ones are readable without. Returns the article object with content_markdown populated. Errors if the slug does not exist or the account cannot see it.

Parameters1

slug

string

required

URL slug of the article, e.g. 'how-we-cut-build-times'. Not the numeric id, and not the full URL.

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "URL slug of the article, e.g. 'how-we-cut-build-times'. Not the numeric id, and not the full URL."
    }
  },
  "required": [
    "slug"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

publish_article

Create a new article and make it live immediately, or schedule it for a future time. This PUBLISHES: without schedule_at the article is world-readable the moment this returns, at the visibility you choose. If the piece is not ready, use create_draft instead and publish later. Each call creates a NEW article — it is not idempotent, so calling twice publishes twice; use update_article to change one that exists. Requires an API key and consumes one publish from the account's plan quota; the response warns when the allowance is nearly spent. Returns the created article with its public url and editor_url.

Parameters6

title	string	required	Headline, 1-250 characters.
body_markdown	string	required	Complete article body as Markdown. Images may be referenced by URL.
tags	array	optional	Up to 10 topic tags used for discovery and filtering.
cover_image_url	string	optional	Absolute URL of the hero image. generate_cover_image returns a URL suitable here.
schedule_at	string	optional	ISO 8601 timestamp to publish at, e.g. '2026-09-01T09:00:00Z'. Omit to publish immediately. A past timestamp publishes immediately.
visibility	string	optional	Audience: 'public' anyone, 'subscribers' newsletter subscribers, 'paid' paying members, 'private' only you. Defaults to 'public'.

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "maxLength": 250,
      "description": "Headline, 1-250 characters."
    },
    "body_markdown": {
      "type": "string",
      "minLength": 1,
      "description": "Complete article body as Markdown. Images may be referenced by URL."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "description": "Up to 10 topic tags used for discovery and filtering."
    },
    "cover_image_url": {
      "type": "string",
      "format": "uri",
      "description": "Absolute URL of the hero image. generate_cover_image returns a URL suitable here."
    },
    "schedule_at": {
      "type": "string",
      "description": "ISO 8601 timestamp to publish at, e.g. '2026-09-01T09:00:00Z'. Omit to publish immediately. A past timestamp publishes immediately."
    },
    "visibility": {
      "type": "string",
      "enum": [
        "public",
        "subscribers",
        "paid",
        "private"
      ],
      "default": "public",
      "description": "Audience: 'public' anyone, 'subscribers' newsletter subscribers, 'paid' paying members, 'private' only you. Defaults to 'public'."
    }
  },
  "required": [
    "title",
    "body_markdown"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

create_draft

Save an article as an unpublished draft. Nothing becomes visible to readers: use this whenever the work still needs review, and publish_article only when it should go live. The draft can be edited afterwards with update_article. Each call creates a NEW draft — not idempotent, so calling twice leaves two drafts. Requires an API key. Returns the draft with an editor_url for finishing it in the browser.

Parameters3

title	string	required	Working headline. Can be changed before publishing.
body_markdown	string	required	Article body so far, as Markdown.
tags	array	optional	Topic tags to carry through to publication.

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "description": "Working headline. Can be changed before publishing."
    },
    "body_markdown": {
      "type": "string",
      "minLength": 1,
      "description": "Article body so far, as Markdown."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Topic tags to carry through to publication."
    }
  },
  "required": [
    "title",
    "body_markdown"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

update_article

Change the title, body, or tags of an article or draft that already exists. Only the fields you pass are touched; omitted fields keep their current values. Passing `tags` REPLACES the whole tag list rather than adding to it, so send the full set you want. Editing a published article changes what readers see immediately; it does not unpublish or re-date it. Safe to repeat: the same call twice leaves the same result. Requires an API key, and the account must own the article. Errors if no updatable field is supplied. Returns the updated article.

Parameters4

id	string	required	Article or draft id from a listing tool. This is the id, not the slug.
title	string	optional	Replacement headline.
body_markdown	string	optional	Replacement body as Markdown. Replaces the whole body, not a patch.
tags	array	optional	Replacement tag list, up to 10. Overwrites the existing tags entirely.

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Article or draft id from a listing tool. This is the id, not the slug."
    },
    "title": {
      "type": "string",
      "minLength": 1,
      "maxLength": 500,
      "description": "Replacement headline."
    },
    "body_markdown": {
      "type": "string",
      "minLength": 1,
      "description": "Replacement body as Markdown. Replaces the whole body, not a patch."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "description": "Replacement tag list, up to 10. Overwrites the existing tags entirely."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

search_articles

Search PUBLISHED articles across all of Misar.Blog, including other creators' work. Use this for discovery, research, and competitive reading. It never returns drafts, scheduled, or private posts — not even your own — so reach for list_my_articles when you want your unpublished work. Reads only. No API key required; unauthenticated callers are rate-limited by IP. Filters combine with AND. Returns an array of article summaries without bodies; pass a slug to get_article for the full text. An empty array means no matches, which is not an error.

Parameters4

q	string	optional	Free-text query matched against title and body. Minimum 2 characters.
tag	string	optional	Restrict to articles carrying this exact tag.
author	string	optional	Restrict to one author, by username.
limit	integer	optional	Maximum results to return, 1-20. Defaults to 10.

Raw schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "minLength": 2,
      "description": "Free-text query matched against title and body. Minimum 2 characters."
    },
    "tag": {
      "type": "string",
      "description": "Restrict to articles carrying this exact tag."
    },
    "author": {
      "type": "string",
      "description": "Restrict to one author, by username."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "default": 10,
      "description": "Maximum results to return, 1-20. Defaults to 10."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

research_topic

Research a topic with AI and return insights, sources, and a suggested content outline. Use it at the START of a piece, before drafting — it produces raw material to write from, not a finished article and not a title. For titles use generate_title_seo; to see what already exists on Misar.Blog use search_articles. Nothing is saved: no draft, article, or file is created, and calling it has no effect on the blog. Requires an API key and consumes AI credits from the account's plan, so each call costs whether or not you use the output. Runs noticeably longer than a plain read, and being generative, two identical calls give different text. Returns prose to read, not structured JSON — verify any factual claims it makes.

Parameters1

query

string

required

The topic or question to research, 5-500 characters. Specific beats broad: 'how small SaaS teams price annual plans' returns more than 'pricing'.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 5,
      "maxLength": 500,
      "description": "The topic or question to research, 5-500 characters. Specific beats broad: 'how small SaaS teams price annual plans' returns more than 'pricing'."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

generate_title_seo

Generate 5 search-optimised article titles from a TOPIC OR KEYWORD, each with a keyword-strategy hint. Aims at high-volume, low-competition long-tail phrases and at AI answer engines (ChatGPT, Perplexity, Claude) as well as Google. Pick between the two title tools by what you have in hand: use this one when you have a topic or keywords and the article may not be written yet. Use suggest_titles when the draft already exists and you want titles drawn from its actual text. Passing `context` here does not make them equivalent — this one still optimises for the keywords you supply. Nothing is saved and no article is created or retitled; use update_article to apply a title. Requires an API key and consumes AI credits per call. Generative, so repeated calls return different titles.

Parameters2

prompt	string	required	Topic or target keywords, 3-500 characters. Include niche, audience and any long-tail phrase you want to rank for, e.g. 'best AI writing tools for beginner bloggers 2025'.
context	string	optional	Optional draft text (plain or Markdown, up to 8000 chars) so the titles match what the article actually says. Titles still follow `prompt` for keywords.

Raw schema

{
  "type": "object",
  "properties": {
    "prompt": {
      "type": "string",
      "minLength": 3,
      "maxLength": 500,
      "description": "Topic or target keywords, 3-500 characters. Include niche, audience and any long-tail phrase you want to rank for, e.g. 'best AI writing tools for beginner bloggers 2025'."
    },
    "context": {
      "type": "string",
      "maxLength": 8000,
      "description": "Optional draft text (plain or Markdown, up to 8000 chars) so the titles match what the article actually says. Titles still follow `prompt` for keywords."
    }
  },
  "required": [
    "prompt"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

suggest_titles

Generate 5 title options FROM AN EXISTING DRAFT, derived from what the article actually says. Pick between the two title tools by what you have in hand: use this one when the text exists and should drive the headline. Use generate_title_seo when you are starting from a topic or keyword, or want titles aimed at specific search terms — this tool takes no keyword input at all. Nothing is saved and the article is not retitled; apply a choice with update_article. Requires an API key and consumes AI credits per call. Generative, so repeated calls return different titles. Needs at least 20 characters of text to work from.

Parameters1

context

string

required

The article text to draw titles from, plain or Markdown, 20-8000 characters. More of the real draft yields better-fitting titles than a summary.

Raw schema

{
  "type": "object",
  "properties": {
    "context": {
      "type": "string",
      "minLength": 20,
      "maxLength": 8000,
      "description": "The article text to draw titles from, plain or Markdown, 20-8000 characters. More of the real draft yields better-fitting titles than a summary."
    }
  },
  "required": [
    "context"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

generate_cover_image

Generate an image from a text prompt with AI, upload it to the Misar.Blog CDN, and return its public URL for use as cover_image_url when publishing. Use it when no artwork exists yet; use upload_image for a file the user already has. Each call generates a NEW image and costs generation credits against the account's plan — it is not idempotent, so re-running to 'try again' bills again. Generation takes noticeably longer than other tools. Requires an API key. The resulting URL is public and cannot be deleted through this server. Results vary between runs for the same prompt.

Parameters2

prompt	string	required	What the image should show, in plain language, up to 1000 characters. Describe subject and style; avoid asking for text in the image.
size	string	optional	Output dimensions: '1792x1024' landscape (the default, best for article covers), '1024x1024' square, '1024x1792' portrait.

Raw schema

{
  "type": "object",
  "properties": {
    "prompt": {
      "type": "string",
      "minLength": 1,
      "maxLength": 1000,
      "description": "What the image should show, in plain language, up to 1000 characters. Describe subject and style; avoid asking for text in the image."
    },
    "size": {
      "type": "string",
      "enum": [
        "1024x1024",
        "1792x1024",
        "1024x1792"
      ],
      "default": "1792x1024",
      "description": "Output dimensions: '1792x1024' landscape (the default, best for article covers), '1024x1024' square, '1024x1792' portrait."
    }
  },
  "required": [
    "prompt"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_series

List every series the authenticated account owns. Despite the name this returns the whole collection, not one series — there is no single-series lookup. Use it to find a series slug before calling add_to_series, or to check whether a series already exists before create_series makes a duplicate. Reads only; nothing is created or modified. Requires an API key, and takes no parameters — it is unfiltered and unpaginated. Returns `{ series, total }` where each entry carries id, slug, title, description, url and article_count. An empty list means the account has no series yet, which is not an error.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

create_series

Create a new, empty series — a named collection that related articles can be added to. Creating the series does not move any article into it; follow up with add_to_series for each one. Call get_series first to avoid making a second series with the same title, since each call creates a NEW series and nothing deduplicates them. Requires an API key. The series and its URL become publicly reachable, though it shows nothing until articles are added. Returns the series with the slug that add_to_series needs.

Parameters2

title	string	required	Display name of the series. The slug is derived from this.
description	string	optional	Short summary shown on the series page. Optional.

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "description": "Display name of the series. The slug is derived from this."
    },
    "description": {
      "type": "string",
      "description": "Short summary shown on the series page. Optional."
    }
  },
  "required": [
    "title"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

add_to_series

Place an existing article into an existing series, optionally at a specific position. Both the series and the article must already exist — this creates neither. Identify them by SLUG, not id: get_series supplies the series slug and the article tools supply the article slug. Omit position to append at the end. Requires an API key. Adding an article does not change its publication status or URL; it only changes where it appears. Inserting at a position shifts the articles after it down. Errors if either slug is unknown.

Parameters3

series_slug	string	required	Slug of the target series, from get_series. Not its title or id.
article_slug	string	required	Slug of the article to add, from list_my_articles. Not its title or id.
position	integer	optional	1-based position within the series. Omit to append at the end. Inserting shifts later articles down.

Raw schema

{
  "type": "object",
  "properties": {
    "series_slug": {
      "type": "string",
      "description": "Slug of the target series, from get_series. Not its title or id."
    },
    "article_slug": {
      "type": "string",
      "description": "Slug of the article to add, from list_my_articles. Not its title or id."
    },
    "position": {
      "type": "integer",
      "minimum": 1,
      "description": "1-based position within the series. Omit to append at the end. Inserting shifts later articles down."
    }
  },
  "required": [
    "series_slug",
    "article_slug"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_comments

Read the comment thread on one article, oldest first, paginated. Use it to review reader feedback or summarise a discussion. It reads comments only; there is no tool here for posting or moderating a reply. Reads only. Requires an API key and counts against the plan's request quota. Page through with limit and offset — the default returns the first 20. Returns the comments with their authors and timestamps; an empty list simply means no comments yet, which is not an error.

Parameters3

article_id	string	required	UUID of the article, as returned in the `id` field by article tools. Not the slug.
limit	integer	optional	Comments per page, 1-100. Defaults to 20.
offset	integer	optional	Comments to skip before this page. Defaults to 0.

Raw schema

{
  "type": "object",
  "properties": {
    "article_id": {
      "type": "string",
      "format": "uuid",
      "description": "UUID of the article, as returned in the `id` field by article tools. Not the slug."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 20,
      "description": "Comments per page, 1-100. Defaults to 20."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "default": 0,
      "description": "Comments to skip before this page. Defaults to 0."
    }
  },
  "required": [
    "article_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_follow_status

Check whether the authenticated account follows a given profile, and how many followers that profile has. Use it before offering to follow someone, so you do not suggest an action that is already done. It answers about ONE profile identified by UUID — there is no tool here that lists everyone you follow. Reads only; following state is not changed. Requires an API key and counts against the plan's request quota. Returns the follow relationship and follower count. Errors if the UUID does not match a profile.

Parameters1

user_id

string

required

UUID of the profile to check, as returned in author fields by article tools. Not the username.

Raw schema

{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string",
      "format": "uuid",
      "description": "UUID of the profile to check, as returned in author fields by article tools. Not the username."
    }
  },
  "required": [
    "user_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_newsletter_subscribers

List the people subscribed to the authenticated account's newsletter, paginated. Use it to size the audience or export the list. For what has been SENT to them, use list_newsletter_issues instead. Reads only — no email is sent and no subscriber is added or removed. Requires an API key. This returns personal data (email addresses), so treat the result as confidential and do not echo it into shared transcripts. Page with limit and offset; the default returns the first 20.

Parameters2

limit	integer	optional	Subscribers per page, 1-100. Defaults to 20.
offset	integer	optional	Subscribers to skip before this page. Defaults to 0.

Raw schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 20,
      "description": "Subscribers per page, 1-100. Defaults to 20."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "default": 0,
      "description": "Subscribers to skip before this page. Defaults to 0."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_newsletter_issues

List newsletter issues the account has sent or scheduled, newest first. Use it to check what went out and when, or to confirm a scheduled send exists before queueing another. For WHO receives them, use list_newsletter_subscribers. Reads only — this neither sends nor cancels an issue. Requires an API key. Returns each issue with its subject, status and send time. An empty list means nothing has been sent yet, which is not an error.

Parameters1

limit

integer

optional

Issues to return, 1-50, newest first. Defaults to 10.

Raw schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10,
      "description": "Issues to return, 1-50, newest first. Defaults to 10."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_reactions

Read the reaction totals on one article, plus which reactions the authenticated account has left on it. Use it before add_reaction or remove_reaction so you know the current state — it is how you tell 'not yet liked' from 'already liked'. Covers one article at a time. Reads only; no reaction is added or removed. Requires an API key. Returns counts per type (like, clap, bookmark) alongside the caller's own reactions. Zero counts are a real answer, not an error.

Parameters1

article_id

string

required

UUID of the article, from the `id` field returned by article tools.

Raw schema

{
  "type": "object",
  "properties": {
    "article_id": {
      "type": "string",
      "format": "uuid",
      "description": "UUID of the article, from the `id` field returned by article tools."
    }
  },
  "required": [
    "article_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

add_reaction

Record one reaction — like, clap, or bookmark — from the authenticated account on an article. This acts publicly as the account holder, so only call it when the user has actually asked to react; do not react on their behalf to be helpful. Adds a single type per call — react twice for two types. Safe to repeat: if the reaction already exists the call succeeds and changes nothing, so it will not double-count. Requires an API key. Use remove_reaction to undo, and get_reactions to see the resulting totals.

Parameters2

article_id	string	required	UUID of the article to react to, from the `id` field of article tools.
type	string	required	Which reaction to add: 'like' approval, 'clap' stronger approval, 'bookmark' save for later.

Raw schema

{
  "type": "object",
  "properties": {
    "article_id": {
      "type": "string",
      "format": "uuid",
      "description": "UUID of the article to react to, from the `id` field of article tools."
    },
    "type": {
      "type": "string",
      "enum": [
        "like",
        "clap",
        "bookmark"
      ],
      "description": "Which reaction to add: 'like' approval, 'clap' stronger approval, 'bookmark' save for later."
    }
  },
  "required": [
    "article_id",
    "type"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

remove_reaction

Withdraw one reaction the authenticated account previously left on an article. Removes exactly the type you name and leaves the account's other reactions on that article intact — removing 'like' does not remove a 'bookmark'. Nothing else is deleted: the article and its comments are untouched. Safe to repeat: removing a reaction that is not there succeeds and changes nothing. Requires an API key. Call get_reactions first if you need to know what is currently set.

Parameters2

article_id	string	required	UUID of the article to un-react to, from the `id` field of article tools.
type	string	required	Which reaction to withdraw: 'like', 'clap', or 'bookmark'.

Raw schema

{
  "type": "object",
  "properties": {
    "article_id": {
      "type": "string",
      "format": "uuid",
      "description": "UUID of the article to un-react to, from the `id` field of article tools."
    },
    "type": {
      "type": "string",
      "enum": [
        "like",
        "clap",
        "bookmark"
      ],
      "description": "Which reaction to withdraw: 'like', 'clap', or 'bookmark'."
    }
  },
  "required": [
    "article_id",
    "type"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

README.md7 KBView on GitHub

Misar.Blog MCP Server

Publish and manage articles, series, comments, reactions, newsletters, and analytics — from any AI assistant.

23 tools · 8 prompts · 5 resources · 6 agent skills

Works with Claude (Desktop, Code, and web), Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, ChatGPT, and any other MCP-compatible client — over stdio or Streamable HTTP.

Install

Smithery (recommended)

bash

npx -y @smithery/cli install misar/misarblog-mcp --client claude

Claude Code

bash

claude mcp add misarblog -- npx -y @misarblog/mcp@latest

Manual (any client)

json

{
  "mcpServers": {
    "misarblog": {
      "command": "npx",
      "args": ["-y", "@misarblog/mcp@latest"],
      "env": { "MISARBLOG_API_KEY": "mbk_your_key_here" }
    }
  }
}

Ready-made configs for every client live in connectors/.

Remote (no install)

json

{
  "mcpServers": {
    "misarblog": {
      "type": "streamable-http",
      "url": "https://www.misar.blog/api/mcp",
      "headers": { "Authorization": "Bearer mbk_your_key_here" }
    }
  }
}

Authentication

Two options — no copy-paste needed for the first:

Browser login. Start the server with no key and run the login tool. It opens the Misar.Blog consent screen, you review the requested permissions, and the key is delivered straight back and saved to ~/.misarblog/config.json.
API key. Create one at https://www.misar.blog/dashboard/settings/api-keys and set MISARBLOG_API_KEY.

Self-hosted instances: set MISARBLOG_BASE_URL.

Tools

Tool	Description
`upgrade`	Show your current Misar.Blog plan, how much of each quota you have left, and what upgrading unlocks.
`get_profile`	Get your Misar.Blog creator profile.
`get_analytics_summary`	Get analytics summary (views, revenue, subscribers) for a time period.
`list_my_articles`	List your articles on Misar.Blog.
`get_article`	Get a single article by slug, including full markdown content.
`publish_article`	Publish a new article (or schedule it) on Misar.Blog.
`create_draft`	Save an article as a draft on Misar.Blog (for review before publishing).
`update_article`	Update the title, body, or tags of an existing article or draft.
`search_articles`	Search PUBLISHED articles across Misar.Blog by keyword, tag, or author — including other creators' work.
`research_topic`	Research a topic and get AI-generated insights, sources, and a content outline.
`generate_title_seo`	Generate 5 SEO/AEO/GEO-optimized article titles from a topic or keyword prompt.
`suggest_titles`	Generate 5 compelling, SEO-friendly article title options from your existing article content.
`generate_cover_image`	Generate a cover image using AI and upload it to the Misar.Blog CDN.
`get_series`	List all your series on Misar.Blog.
`create_series`	Create a new series to group related articles.
`add_to_series`	Add an existing article to a series.
`list_comments`	Get the comment thread for an article.
`get_follow_status`	Get follow status and follower count for a profile UUID.
`list_newsletter_subscribers`	Get your newsletter subscriber list.
`list_newsletter_issues`	Get your sent and scheduled newsletter issues.
`get_reactions`	Get reaction counts and your reactions for an article.
`add_reaction`	Add a reaction to an article.
`remove_reaction`	Remove a specific reaction from an article.

Prompts

Reusable workflows your client exposes as slash-commands.

Prompt	Description
`draft_article`	Write a complete, SEO-optimised article draft and save it to Misar.Blog.
`improve_seo`	Audit an article for SEO/AEO/GEO and apply the improvements.
`write_newsletter`	Draft a newsletter issue from recent published articles.
`article_ideas`	Generate article ideas grounded in what has and has not been covered.
`social_caption`	Write platform-specific promotional captions for an article.
`optimize_headline`	Generate and rank stronger headline options for an article.
`series_plan`	Plan a multi-part article series and set it up on Misar.Blog.
`engagement_report`	Summarise blog performance and recommend what to do next.

Resources

Read-only context an agent can attach without spending a tool call.

URI	Description
`misarblog://profile`	Your Misar.Blog profile — username, display name, bio, and payout status.
`misarblog://articles/recent`	Your 20 most recent published articles.
`misarblog://articles/drafts`	Your unpublished drafts, so work in progress can be resumed rather than restarted..
`misarblog://series`	Your series and the articles in each, in order..
`misarblog://analytics/summary`	Views, revenue, and subscriber counts for the last 30 days — the baseline for any performance question..

Agent skills

Bundled in skills/ — guidance an agent loads when a task matches.

Skill	Use when
`blog-analytics-report`	Report on Misar.Blog performance — views, revenue, subscribers, engagement. Use for "how is my blog doing", traffic reports, or content performance analysis.
`manage-article-series`	Plan and manage a multi-part article series on Misar.Blog. Use for "series", "multi-part", "part 2", or organising related posts into a sequence.
`newsletter-campaign-report`	Draft and review Misar.Blog newsletter issues and subscriber performance. Use for "newsletter", "email my subscribers", or newsletter performance questions.
`promote-article`	Write platform-specific promotional copy for a Misar.Blog article. Use for "share this post", "social caption", "promote my article", or writing X/LinkedIn/Reddit copy.
`publish-blog-post`	Write, draft, and publish an article on Misar.Blog. Use when the user wants to write a post, publish an article, save a draft, or turn notes into a blog post.
`seo-optimize-article`	Audit and improve an existing Misar.Blog article for SEO, AEO, and AI-answer-engine citability. Use for "improve SEO", "why isn't this ranking", "meta description", or "optimise for AI search".

Safety

Destructive and irreversible actions are annotated (destructiveHint) so clients can prompt before running them. The skills instruct agents to confirm before anything that sends mail, publishes content, or is otherwise visible to other people.

Discovery (initialize, tools/list, prompts/list, resources/list) never requires credentials, so registries can index the server without one. Every action does.

Install

Tools (23)

upgradeget_profileget_analytics_summarylist_my_articlesget_articlepublish_articlecreate_draftupdate_article

Configuration

Environment variables

MISARBLOG_API_KEYsecret

Your Misar.Blog API key (mbk_…). Create one at https://www.misar.blog/dashboard/settings/api-keys, or omit it and run the "login" tool to authenticate via browser.

MISARBLOG_BASE_URL

Override the API base URL. Only needed for self-hosted instances.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "misarblog-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@misarblog/mcp@5.1.2"
      ],
      "env": {
        "MISARBLOG_API_KEY": "<YOUR_MISARBLOG_API_KEY>",
        "MISARBLOG_BASE_URL": "<YOUR_MISARBLOG_BASE_URL>"
      }
    }
  }
}

io.github.Misar-AI/misarblog-mcp — Misar.Blog MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

upgrade

get_profile

get_analytics_summary

list_my_articles

get_article

publish_article

create_draft

update_article

search_articles

research_topic

generate_title_seo

suggest_titles

generate_cover_image

get_series

create_series

add_to_series

list_comments

get_follow_status

list_newsletter_subscribers

list_newsletter_issues

get_reactions

add_reaction

remove_reaction

Misar.Blog MCP Server

Install

Smithery (recommended)

Claude Code

Manual (any client)

Remote (no install)

Authentication

Tools

Prompts

Resources

Agent skills

Safety

Links

Install

Configuration

Related servers