Skip to main content
Glama
Misar-AI

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Log in via browser

login

Authenticate with your Misar.Blog account through your browser without copy-pasting an API key. Review requested permissions, click Authorize, and receive your key saved locally.

Instructions

Authenticate 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoLocal callback port (9001–9099). Random by default.
forceNoForce re-authentication even if already logged in (rotates your API key).
base_urlNoMisar.Blog base URL for self-hosted instances.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.1.3
    • changedInput schema / properties / base_url / description
      Previous value: -"Base URL of a self-hosted Misar.Blog. Omit for the hosted service."New value: +"Misar.Blog base URL for self-hosted instances."
    • changedInput schema / properties / force / description
      Previous value: -"Re-authenticate even when already logged in. This ROTATES the API key and breaks any other client using the old one — only on explicit request."New value: +"Force re-authentication even if already logged in (rotates your API key)."
    • changedInput schema / properties / port / description
      Previous value: -"Local port for the one-shot callback listener, 9001-9099. Random by default; set it only when a firewall requires a fixed port."New value: +"Local callback port (9001–9099). Random by default."
  2. Changed3 schema fields changedv5.1.0
    • changedInput schema / properties / base_url / description
      Previous value: -"Misar.Blog base URL for self-hosted instances."New value: +"Base URL of a self-hosted Misar.Blog. Omit for the hosted service."
    • changedInput schema / properties / force / description
      Previous value: -"Force re-authentication even if already logged in (rotates your API key)."New value: +"Re-authenticate even when already logged in. This ROTATES the API key and breaks any other client using the old one — only on explicit request."
    • changedInput schema / properties / port / description
      Previous value: -"Local callback port (9001–9099). Random by default."New value: +"Local port for the one-shot callback listener, 9001-9099. Random by default; set it only when a firewall requires a fixed port."
  3. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare non-readOnly, openWorld, non-idempotent, non-destructive, but the description adds real value beyond them: it discloses an interactive browser step requiring user consent and a persistent on-disk side effect (~/.misarblog/config.json). It does not mention key rotation or port-conflict behavior, which remain only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the what and how, then the outcome (key saved to config). No filler, no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still closes the loop by explaining where the credential ends up. For a zero-required-parameter auth tool, an agent has everything needed to decide and call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the port, force, and base_url semantics are already fully documented. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Authenticate) and resource (Misar.Blog account) plus the exact mechanism (browser authorization page with an Authorize click). It is unmistakably distinct from the sibling content tools (search_articles, publish_article, etc.), which never touch auth.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"no API key copy-paste needed" clearly frames the scenario as an alternative to manual API-key configuration and signals this is the entry-point auth tool. It stops short of stating when not to re-run it (the schema's force flag covers that) and names no explicit alternative tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools