Misar.Blog MCP Server

What Misar.Blog MCP Server MCP server does

Misar.Blog MCP Server MCP server gives an MCP-compatible AI client access to publishing and audience-management functions on Misar.Blog. It can retrieve a creator profile, list personal articles, fetch complete article markdown by slug, and search published work by keyword, tag, or author. Personal drafts and unpublished articles are handled through the account-specific listing tool rather than public search.

Writing workflows include topic research, AI-generated title suggestions, article drafting, updates, scheduling, and publication. The server can also create and organize article series, upload a local image, or generate a cover image and send it to the Misar.Blog CDN. For audience operations, it exposes newsletter subscribers and issues, article comments, follower status, and reactions. Analytics provide views, revenue, and subscriber figures for a selected period.

How it works

The server communicates with an MCP client over local stdio or Streamable HTTP. A local process can be launched with the npm package, while a remote configuration can point to Misar.Blog's MCP endpoint. Discovery operations such as listing tools, prompts, and resources do not require credentials, but actions do.

Authentication can begin with the login tool. The user reviews permissions in a browser, authorizes access, and receives a key that the client stores in ~/.misarblog/config.json. Alternatively, the client can provide an API key through configuration. The status tool reports whether the connection is authenticated and which account is active. The upgrade tool only reads plan and quota information and returns an upgrade link.

Setup and configuration

Install the npm package through a client connector or configure it manually as an MCP server. A local setup can use npx -y @misarblog/mcp@latest; a remote setup uses the Streamable HTTP URL with a bearer token. The repository also provides ready-made connector configurations for supported clients.

Set MISARBLOG_API_KEY when using API-key authentication. Browser login can be used instead, so an API key is not required for that flow. Set MISARBLOG_BASE_URL when connecting to a self-hosted Misar.Blog instance. API-key access is required by tools such as comments, follows, newsletters, and reactions, and some of those calls count against the plan's request quota.

Tools and capabilities

Misar.Blog MCP Server MCP server includes tools for:

• Creating drafts, updating articles, publishing immediately, or scheduling publication.
• Researching topics and generating SEO-, AEO-, and GEO-oriented title ideas.
• Suggesting titles from existing content and generating or uploading cover images.
• Creating series and adding existing articles to them.
• Reading analytics, profiles, article content, public search results, comments, reactions, and follow data.
• Reading newsletter subscribers and sent or scheduled newsletter issues.

It also exposes reusable prompts for drafting articles, improving SEO, writing newsletters, planning series, creating social captions, and reporting on engagement. Read-only resources provide profile data, recent published articles, drafts, series, and a 30-day analytics summary.

Limitations and notes

Search covers published articles across Misar.Blog, including other creators' work; it is not the tool for finding personal drafts or unpublished posts. Several audience-related operations require an API key. Publishing, sending communications, and other externally visible actions are marked for client confirmation through destructive-action annotations and bundled workflow guidance. The upgrade tool does not change a plan or process payment; the user must follow its returned link.