All MCP Servers
Dev Tools & GitMCP RegistrymcpbB · 71

KatanA Markdown Linter MCP server

io.github.HiroyukiFuruno · Updated

Markdown linter, workspace-scoped stdio MCP server, and self-hosted text-only remote MCP server.

At a glance

KatanA Markdown Linter is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y https://github.com/HiroyukiFuruno/katana-markdown-linter/releases/download/v0.20.1/katana-markdown-linter-0.20.1.mcpb`, and declares no required credentials. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

VS CodeVS Code InsidersCursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install KatanA Markdown Linter in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install KatanA Markdown Linter in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add kml -- npx -y https://github.com/HiroyukiFuruno/katana-markdown-linter/releases/download/v0.20.1/katana-markdown-linter-0.20.1.mcpb

  2. Verify it's connected

    bash
    claude mcp list

  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What tools does KatanA Markdown Linter expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

The published package could not be downloaded or read for analysis.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • 0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%0%

    0 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (0.20.1).

Documentation

Full README

katana-markdown-linter

A markdownlint-compatible Rust engine, <code>kml</code> CLI, formatter, safe fixer, editor server, and agent-ready MCP server.

<strong>Installation</strong> | <strong>CLI Usage</strong> | <strong>Library API</strong> | <strong>Editor Integration</strong> | <strong>MCP Server</strong>

What is kml

katana-markdown-linter is a fast Markdown lint engine for technical writing, specification documents, and AI-agent-assisted documentation workflows.

The project shares the KatanA visual identity, but keeps a standalone boundary: the crate, CLI, wrappers, editor server, and MCP server do not depend on KatanA Desktop.

See Markdown syntax support for the tested specification baseline, shared syntax boundaries, and safe-fix verification.

Features

  • markdownlint-compatible checks for the active upstream rule catalog
  • Safe fixes for low-risk rule violations and explicit opt-in unsafe fixes
  • Formatter mode for layout normalization without changing author intent
  • Embeddable Rust API for applications that need linting or fixing in-process
  • `kml` CLI with JSON output, stdin support, ignore handling, and statistics
  • Editor integration through a stdio Language Server Protocol server
  • MCP server for agents and tools that need structured lint access
  • Multi-channel distribution through Cargo, GitHub Releases, npm, PyPI, and Homebrew

Library API

Use the crate directly when embedding linting into another Rust application.

  • lint(content, options)
  • fix(content, options)
  • available_rules()
  • localized_available_rules(language_code)
  • implemented_rules()
  • missing_rules()
  • rule_catalog()
  • localized_rule_catalog(language_code)
  • resolve_locale_code(language_code)
  • resolve_locale_code_or(language_code, fallback)
  • localized_rule_description(rule_id, fallback_description, language_code)
  • supported_locales()
  • upstream::get_rule_documentation(rule_id, locale)
  • MarkdownLintConfig
  • MarkdownLintConfig::schema()
  • MarkdownLintConfig::to_lint_options()

available_rules() returns canonical English metadata. For user-facing rule catalogs, call localized_available_rules(language_code), localized_rule_catalog(language_code), RuleMeta::localized_description(...), or localized_rule_description(...) so applications can pass UI language codes without reimplementing kml's fallback policy.

Excerpt — the full document is on GitHub.

Maintain KatanA Markdown Linter? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![KatanA Markdown Linter on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-hiroyukifuruno-kml)](https://mcp-skills-hub.vercel.app/mcps/io-github-hiroyukifuruno-kml)

Catalog data refreshed . Something wrong? Report it.