KatanA Markdown Linter
Lint Markdown in-repo from your agent via a workspace-scoped stdio MCP server before publishing docs or READMEs.
Overview
KatanA Markdown Linter is an MCP server for the Build phase that lints Markdown inside your workspace through agent-callable tools.
What is this MCP server?
- KatanA Markdown Linter rules exposed as MCP tools for agent-driven fixes
- Workspace-scoped stdio transport for local Claude Code and Cursor setups
- Optional self-hosted text-only remote MCP server for team or CI-style lint runs
- Published as versioned mcpb package (v0.19.4) with pinned file SHA256
- Pairs with doc-heavy workflows: skills, ADRs, and catalog README maintenance
- Server version 0.19.4
- Stdio MCP transport plus optional self-hosted remote MCP
- Distributed via pinned mcpb artifact with SHA256 verification
What problem does it solve?
Agents and founders ship broken headings, inconsistent lists, and linter failures in Markdown only after a manual pass or CI failure.
Who is it for?
Solo builders who treat Markdown as source of truth for skills, docs, and landing copy and want linting inside Claude Code or Cursor.
Skip if: Teams that only need one-off HTML or Notion exports with no in-repo Markdown workflow.
What do I get? / Deliverables
Your agent can lint and reason about Markdown fixes in the same session you edit READMEs, skills, and docs.
- Lint diagnostics for Markdown files in scope
- Agent-actionable fix guidance aligned with KatanA rules
- Repeatable doc checks before merge or publish
Recommended MCP Servers
Journey fit
Documentation quality gates sit in the Build phase when solo builders ship READMEs, skill files, and product docs alongside code. Docs subphase is the canonical shelf for Markdown linting that keeps agent skills, changelogs, and landing copy structurally consistent.
How it compares
Docs-focused MCP linter, not a general-purpose web scraper or LLM chat server.
Common Questions / FAQ
Who is KatanA Markdown Linter for?
Indie developers and agent users who maintain Markdown-heavy repos—skills, docs, and READMEs—and want lint results inside the editor agent.
When should I use KatanA Markdown Linter?
Use it during Build and Ship when you are editing documentation, preparing a release README, or cleaning catalog pages before publish.
How do I add KatanA Markdown Linter to my agent?
Register the stdio MCP server from the published mcpb package in your client’s MCP config, point it at your workspace root, and invoke lint tools from the agent.