MCP.Market

ctxlint MCP server

by YawLabs·io.github.YawLabs/ctxlint·v0.28.1·9 stars

Lint AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Established

9 stars6.5k downloads/wk

Reviews

Write one

Nobody has reviewed ctxlint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ctxlint tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How ctxlint compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 88% of 4,460 AI and agents servers
GitHub stars
9
more than 83% of 2,711 AI and agents servers
Downloads a week
6,479
more than 95% of 1,538 AI and agents servers with a package

Release history: 5 versions in the registry since 2026-09-15, latest 2026-10-31, typically one every 14 days.

Install ctxlint in Claude Code, Cursor or VS Code

Runs npx -y @yawlabs/ctxlint on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ctxlint -- npx -y @yawlabs/ctxlint
Add to Cursor

What the publisher says

From the ctxlint repository's README, as published. We do not edit it. Read it on GitHub

ctxlint

Lint your AI agent context files, MCP server configs, and session data against your actual codebase. Context linting + MCP config linting + session auditing. 16 AI tools, 8 MCP clients, cross-project consistency, auto-fix. Works as a CLI, CI step, pre-commit hook, or MCP server.

Your CLAUDE.md is lying to your agent. Your .mcp.json has a hardcoded API key. ctxlint catches both.

One click adds this to your local Yaw MCP config so it's available in every Yaw Terminal session. Or install manually below.

Why ctxlint?

Every AI coding tool ships a context file: CLAUDE.md, .cursorrules, AGENTS.md, .mcp.json. These files are the single most important interface between you and your agent — they tell it what to build, how to test, where things live.

But context files rot fast. You rename a file, change a build script, or switch from Jest to Vitest — and your CLAUDE.md still says the old thing. Your agent follows those stale instructions faithfully, then fails. You lose 10 minutes debugging what turns out to be a wrong path in line 12 of a markdown file.

Multiply that across a team with 5 context files, 3 MCP configs, and 2 people who touched the build system last week — and you have a real problem with no existing solution.

ctxlint is a linter purpose-built for this. It reads your context files, cross-references them against your actual codebase, and catches the drift before your agent does.

  • Instant startup — ships as a single self-contained bundle with zero runtime dependencies. npx downloads a ~400 KB tarball and starts immediately
  • Catches real problems — broken paths, wrong commands, stale references, contradictions across files
  • Smart suggestions — detects git renames and fuzzy-matches to suggest the right path
  • Auto-fix — --fix rewrites broken paths automatically using git history
  • Token-aware — shows how much context window your files consume and flags redundant content
  • Every AI tool — supports Claude Code, Cursor, Copilot, Windsurf, Gemini, Cline, Aider, and 9 more
  • Multiple outputs — text, JSON, and SARIF (GitHub Code Scanning)
  • MCP server — 7 tools for IDE/agent integration with tool annotations for auto-approval
  • Watch mode — --watch re-lints automatically when context files change

Install

Run directly (no install needed):

npx -y @yawlabs/ctxlint@latest

Project install (recommended for teams)

npm install -D @yawlabs/ctxlint
# or
pnpm add -D @yawlabs/ctxlint

Then add to your package.json scripts:

{
  "scripts": {
    "lint:ctx": "ctxlint --strict"
  }
}

Global install

npm install -g @yawlabs/ctxlint

Useful if you want ctxlint available in every project without per-project setup.

What It Checks

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

ctxlint: common questions

Is ctxlint MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the ctxlint safety report
How do I install ctxlint?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ctxlint need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is ctxlint maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v0.28.1.
What can I use instead of ctxlint?
Servers from other publishers that do the same job: Basic Memory MCP server, IWE (iwe.md) MCP server and Actual Budget MCP Server.
How does ctxlint compare with other AI and agents MCP servers?
safety score 91/100 (higher than 88% of 4,460 AI and agents servers); github stars 9 (more than 83% of 2,711 AI and agents servers); downloads a week 6,479 (more than 95% of 1,538 AI and agents servers with a package). Full comparison.

Alternatives to ctxlint

Same job from other publishers: the closest match first, then the best rated.

  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Actual Budget MCP Server
    MCP server exposing Actual Budget accounts, transactions, budgets and reporting to LLM assistants.
    B
  • Openflowkit
    Architecture diagrams for your agent: draw on the live OpenFlowKit canvas or edit diagram files.
    A
  • paper-preflight
    Checks every LaTeX reference against Crossref, dblp, arXiv, DataCite, PubMed and OpenAlex. No LLM.
    A

More from YawLabs →