Log inSubmit server
KatanA Markdown Linter logo

KatanA Markdown Linter

Workspace-scoped stdio MCP server for checking, fixing, and formatting Markdown with markdownlint-compatible rules.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install KatanA Markdown Linter

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "katana-markdown-linter": {
      "command": "npx",
      "args": [
        "--yes",
        "katana-markdown-linter@0.20.1"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

KatanA Markdown Linter provides agents with structured access to Markdown linting, safe fixes, and formatting for a selected workspace. It runs as a stdio MCP server and uses the project's Rust-based `kml` engine to process Markdown files. Reach for it when an agent needs consistent documentation checks or controlled repairs without embedding a separate linter workflow.

Use cases

  • Check documentation files for Markdown rule violations
  • Apply conservative fixes to workspace Markdown
  • Format indentation and newline layout
  • Review localized rule descriptions in documentation tools

Key features

  • Markdownlint-compatible rule checks
  • Structured stdio MCP access
  • Safe lint-driven fixes
  • Markdown layout formatting
  • Workspace-root scoping
  • Localized rule metadata

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

16/16 checks healthy over the last 92d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · katana-markdown-linter@0.20.1 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.2kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How KatanA Markdown Linter works

What KatanA Markdown Linter does

KatanA Markdown Linter brings the project's Markdown analysis engine to MCP-compatible agents and tools. It is designed for technical writing, specification documents, and documentation workflows where an agent needs machine-readable lint results or controlled file changes.

The underlying engine follows the markdownlint rule model and supports the active upstream rule catalog. Its capabilities cover three related tasks: checking Markdown for rule violations, applying fixes where changes are considered safe, and normalizing layout through formatter behavior. The project also provides a standalone CLI, Rust library, editor server, and distribution packages, but the MCP component is the workspace-oriented interface for agent use.

How it works

The MCP server communicates over standard input and output and is scoped to a workspace. Start it with the kml-mcp executable and provide an absolute workspace root when needed. Agents can then request structured Markdown lint access against files in that workspace rather than relying on shell output parsing.

The same engine supports safe lint-driven fixes and a formatter for indentation and newline normalization. Safe fixes are intended for low-risk violations; the broader CLI separately exposes explicit opt-in handling for unsafe fixes. This separation makes the MCP server suitable for workflows that need diagnostics first and conservative rewriting afterward.

The project supports localized rule metadata and descriptions for English, Japanese, Simplified Chinese, Traditional Chinese, Korean, Portuguese, French, German, Spanish, and Italian. That localization is part of the underlying engine and can help applications present rule information in a user-facing language.

Setup and configuration

Install the package through Cargo, npm, PyPI, GitHub Releases, or Homebrew. Cargo installs the Rust package and CLI; npm and PyPI provide launchers that obtain the matching release archive on first use. The npm package exposes kml-mcp, and the documented launch pattern supplies --workspace-root with an absolute path.

For example, an npm-based setup can run the MCP process with npx --yes katana-markdown-linter@latest kml-mcp --workspace-root /absolute/path/to/workspace. A globally installed package can invoke the same kml-mcp executable directly. Configure the command and its arguments in the MCP client that launches stdio servers.

The repository also supports the kml CLI through Cargo, npm, PyPI, standalone release archives, and Homebrew. This can be useful for validating the same lint behavior in local scripts or CI alongside agent-driven checks. The project is licensed under MIT.

Tools and capabilities

  • Markdownlint-compatible rule checks.
  • Structured lint access through MCP.
  • Safe fixes for low-risk violations.
  • Formatting for indentation and newline normalization.
  • Workspace-oriented operation through a stdio process.
  • Localized rule metadata and descriptions across multiple languages.

The broader kml toolchain also supports JSON output, stdin processing, ignore handling, statistics, configuration schema access, and rule documentation. These features belong to the project’s CLI or library surfaces; use the MCP server when the primary requirement is exposing Markdown analysis to an agent.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about KatanA Markdown Linter

KatanA Markdown Linter is an MCP server that connects agents to Markdown files in a selected workspace over stdio. Its main tools provide structured linting, conservative fixes, and formatting, using a markdownlint-compatible Rust engine for technical writing, specifications, and documentation workflows.

Install it through npm, PyPI, Cargo, a GitHub Release archive, or Homebrew, then launch the `kml-mcp` executable. npm and PyPI provide launchers that download the matching release archive on first use; the documented npm command accepts `--workspace-root` with an absolute workspace path.

Pass the workspace path with `--workspace-root` when starting `kml-mcp`. The documented usage uses an absolute path, such as `/absolute/path/to/workspace`, so the MCP process operates against the intended Markdown workspace.

Yes. KatanA Markdown Linter uses a standard stdio MCP interface, so it can be configured in Cursor as an MCP server. Start `kml-mcp` with the desired workspace root and provide the executable and arguments through Cursor’s MCP configuration.

Yes, it supports safe lint-driven fixes and formatter behavior for layout normalization. The project distinguishes low-risk safe fixes from unsafe fixes that require explicit opt-in in its CLI, making conservative repair the appropriate default for agent workflows.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKatanA Markdown Linter AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/katana-markdown-linter?style=directory)](https://allmcps.com/mcp/katana-markdown-linter)
HTML Embed
<a href="https://allmcps.com/mcp/katana-markdown-linter"><img src="https://allmcps.com/api/badge/katana-markdown-linter?style=directory" alt="KatanA Markdown Linter on AllMCPs" /></a>