MCP Server Overview
Connect AI assistants to MisarBlog via the Model Context Protocol (MCP).
MCP Server
The MisarBlog MCP server exposes your blog content and writing tools to any MCP-compatible AI assistant (Claude, Cursor, Windsurf, etc.), letting you publish, draft, and research directly from your AI workflow.
What You Can Do
| Tool | Description |
|---|---|
list_articles | List your articles (filter by status, limit) |
get_article | Get full article content by ID or slug |
create_draft | Create a new draft from markdown |
update_article | Update title, body, or tags of a draft |
publish_article | Publish a draft article |
search_articles | Search published articles by keyword, tag, or author |
Authentication Flow
Unlike REST API keys (which you create in the dashboard), MCP keys are generated automatically during the MCP connect flow:
- Your MCP client sends a session-authenticated request to
POST /api/v1/auth/mcp-connect - MisarBlog generates an
mbk_API key, hashes it, and stores the hash in your profile - The raw key is delivered to your local MCP client via a
localhostcallback URL - Your MCP client stores the key and uses it for all subsequent tool calls
No manual copy-paste required. See Setup for the full walkthrough.
Base Transport
The Misar.Blog MCP server supports two transports: HTTP (remote, no install) and stdio (@misarblog/mcp npm package). Tool calls are authenticated with your mbk_ key via the Authorization: Bearer header or MISARBLOG_API_KEY env var.
MCP server URL: https://api.misar.io/blog/v1/mcp
Next Steps
- Setup — Install and configure the MCP server
- Tools Reference — All available tools with parameters and examples