ctxlint

Name: ctxlint
Author: YawLabs

by YawLabsversion 0.28.1i★ –iRuns on your computer

Registry nameio.github.YawLabs/ctxlint

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ctxlint": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/ctxlint",
        "serve"
      ]
    }
  }
}

Run this in your terminal

claude mcp add ctxlint -- npx -y @yawlabs/ctxlint serve

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ctxlint": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/ctxlint",
        "serve"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ctxlint": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/ctxlint",
        "serve"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account YawLabs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 3529 servers in this category
Published to the registry more recently than 79% of the other 3529 servers in this category
Basic checks equal to or better than 100% of the other 3529 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ctxlint safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.28.1) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ctxlint

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

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.

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

Check	What it finds
Broken paths	File references in context that don't exist in your project
Wrong commands	Build/test commands that don't match your package.json scripts or Makefile targets, and Gradle project paths or Maven `-pl` modules your build doesn't declare
Stale context	Context files not updated after recent code changes
Token waste	How much context window your files consume per session
Redundancy	Content the agent can already infer (e.g. "We use React" when react is in package.json)
Contradictions	Conflicting directives across context files (e.g. "use Jest" in one, "use Vitest" in another)
Frontmatter	Invalid or missing YAML frontmatter in Cursor .mdc, Copilot instructions, and Windsurf rules
CI coverage	Release/deploy workflows in `.github/workflows/` not documented in any context file
CI secrets	Secrets used in CI workflows (`${{ secrets.X }}`) not mentioned in context files
Inline secrets	Real secrets pasted into context files — private-key headers, AWS/GitHub/Anthropic/OpenAI/npm/Slack/Google/Stripe token shapes. Messages never echo the secret (6-char redacted prefix only)
Dead hooks	PreToolUse hooks / permissions entries in `.claude/settings.json` pointing at scripts that no longer exist (a dead gate silently no-ops). Scans project `.claude/settings.json[.local]` by default; pass `--hooks-global` to also scan the user-global `~/.claude/settings.json`
Missing secrets	GitHub secrets set on sibling repos but missing from current project
Diverged configs	Canonical config files (CI, tsconfig, etc.) drifting across sibling projects
Missing workflows	GitHub Actions workflows present in 2+ siblings but absent here
Stale memory	Claude Code memory entries referencing paths that no longer exist
Duplicate memory	Near-duplicate memories across projects (>60% content overlap)
Loop detection	Agent stuck in loops — repeated commands or cyclic patterns in session history
Memory overflow	`MEMORY.md` past Claude Code's 200-line / 25KB session-load cap — entries beyond it are invisible to the agent
Shared temp path	A fixed temp path (e.g. `/tmp/pkg.bak`) the agent writes and later reads back — any concurrent session can overwrite it in between
Unverified gate	A lint/typecheck/test/build run that errored or printed nothing, followed by agent prose claiming it passed
Default-branch edits	10+ files edited on `main`/`master` with no intervening commit or branch-away
Unresolvable SHA	A memory cites a commit SHA that does not resolve in this repository
Large reads	Whole-file Reads of 4,000+ tokens, with an estimate of the tokens they re-send as cached context on later turns (an info-level baseline)

Supported Context Files

File	Tool
`CLAUDE.md`, `CLAUDE.local.md`, `.claude/rules/*.md`	Claude Code
`AGENTS.md`, `AGENT.md`, `AGENTS.override.md`	AAIF / Multi-agent standard
`.cursorrules`, `.cursor/rules/.md`, `.cursor/rules/.mdc`, `.cursor/rules/*/RULE.md`	Cursor

| .github/copilot-instructions.md, .github/instructions/*.md, .github/git-commit-instructions.md | GitH

Only the beginning is shown; read the rest in the repo

ctxlint

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

ctxlint

Why ctxlint?

Install

Project install (recommended for teams)

or

Global install

What It Checks

Supported Context Files