Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
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": {
"ai-context-kit": {
"command": "npx",
"args": [
"-y",
"ai-context-kit"
]
}
}
}Run this in your terminal
claude mcp add ai-context-kit -- npx -y ai-context-kitPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ai-context-kit": {
"command": "npx",
"args": [
"-y",
"ai-context-kit"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ai-context-kit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ai-context-kit"
]
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account ofershap, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
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.
ai-context-kit
How do you measure the token cost of your context?
You spent hours writing the perfect .md context file, just to find out that your agent got worse .
That's not a bug. That's what happens when nobody measures the cost of context.
You write a CLAUDE.md. Then someone adds .cursor/rules/. Then a teammate drops in an AGENTS.md. Then someone copies in a .cursorrules file from a blog post. Nobody removes the old ones.
Six months later your project has four context files that overlap, contradict each other, and dump 8,000 tokens of directory listings and "follow best practices" into every conversation. Your agent follows all of it. It gets slower. It gets confused. You blame the model.
An ETH Zurich study (February 2026) measured what actually happens when you give agents context files:
I kept hitting this in my own projects, so I built ai-context-kit - a toolkit to treat context like a budget. Measure it, trim it, inject only what the current task needs.
import { loadRules, measure, lint, select } from "ai-context-kit";
const rules = await loadRules("./");
measure(rules, 4000); // what does your context cost? lint(rules); // conflicts? duplicates? dead weight? select(rules, { task: "fix auth bug", // only inject what matters budget: 2000, // stay within token budget });
npm install ai-context-kit
Run the CLI on any project to see what you're actually injecting:
npx ai-context-kit measure
ai-context-kit measure - 6 rule file(s)
Total: 4,821 tokens
############ 2,100 tokens (44%) - .cursor/rules/conventions.mdc ######## 1,200 tokens (25%) - CLAUDE.md
Then lint it:
npx ai-context-kit lint
ai-context-kit lint - 6 rule file(s)
[!] .cursor/rules/conventions.mdc Rule is 2100 tokens. Consider splitting to keep each file under 2000 tokens.
[x] CLAUDE.md Conflicts with AGENTS.md: "always use semicolons" vs "never use semicolons"
[!] CLAUDE.md Duplicated line also found in .cursor/rules/conventions.mdc. Duplicates waste tokens.
[i] AGENTS.md Contains vague instruction matching "follow best practices". Specific instructions produce better results than general advice.
Score: 70/100 (FAILED)
That's the difference between guessing and knowing.
| Other approaches | ai-context-kit | |
|---|---|---|
| Context cost | Nobody measures it | Token count per file with budget check |
| Conflicts | You find out when the agent does something weird | Detects contradictions across all files automatically |
| Duplicates | Same rule in 3 files, 3x the tokens | Flagged and scored |
| Task relevance | Every rule injected every time | select() picks only what matters for the current task |
| Multi-tool | Locked to one IDE's format | Works across Cursor, Claude Code, Copilot, Windsurf, Cline |
| CI | Hope for the best | lint exits with code 1 on errors. Drop it in your pipeline |
ai-context-kit reads every context file format in the ecosystem, parses frontmatter, estimates token cost, and gives you tools to analyze and manage them.
loadRules() | Auto-detects .cursor/rules/, .cursorrules, CLAUDE.md, AGENTS.md, copilot-instructions.md, .windsurfrules, .clinerules |
measure() | Token cost per rule, percentage of total, budget check |
lint() | Conflicts, duplicates, bloat, vague instructions, useless directory trees. Scores 0-100 |
select() | Picks rules relevant to the current task. Respects a token budget. alwaysApply rules first, then by relevance |
sync() | Single source of truth. Write once in .cursor/rules/, sync to CLAUDE.md, AGENTS.md, and the rest |
init() | Starter template with tips from the research |
loadRules(rootDir?)const rules = await loadRules("./");
// Finds every context file in the project
const rules = await loadRules(".cursor/rules/"); // Or load from a specific directory
Returns RuleFile[] with parsed frontmatter, body, format, path, and token count.
measure(rules, budget?)const report = measure(rules, 4000);
report.totalTokens; // 3847 report.overBudget; // false report.rules; // sorted by size, each with tokens + percentage
lint(rules)const report = lint(rules);
report.score; // 85/100 report.passed; // true (no errors, warnings don't fail) report.issues; // array of { rule, path, severity, message }
What the linter catches:
| Rule | Severity | What it finds |
|---|---|---|
token-budget | warning/error | Files over 2,000 tokens (warning) or 5,000 (error) |
empty-rule | warning | Files too short to do anything |
duplicate-content | warning | Same instruction repeated across files |
conflict | error | "always use X" in one file, "never use X" in another |
directory-listing | warning | 10+ line directory trees that agents don't need |
vague-instruction | info | "follow best practices", "write clean code", "be consistent" |
select(rules, options)The core insight from the research: don't inject everything. Pick what matters.
const relevant = select(rules, {
task: "fix auth bug in /api/auth", budget: 2000, tags: ["security", "api"], exclude: ["style"], });
Scoring: alwaysApply: true in frontmatter gets highest priority. Then task words matched against file paths and content. Then tag matches. Budget is respected - highest-scored rules are included first until the budget runs out.
sync(options)Write rules once, sync everywhere.
await sync({
source: ".cursor/rules/", targets: ["CLAUDE.md", "AGENTS.md", ".github/copilot-instructions.md"], });
Supports dryRun: true to preview changes without writing.
init(options?)await init({ format: "cursor-rules" });
// Creates .cursor/rules/conventions.mdc with research-backed starter template
npx ai-context-kit lint # find issues
npx ai-context-kit lint --json # machine-readable output npx ai-context-kit measure # token cost breakdown npx ai-context-kit measure --budget 4000 # check against budget npx ai-context-kit sync --source .cursor/rules/ --target CLAUDE.md,AGENTS.md npx ai-context-kit init # scaffold starter rules npx ai-context-kit init --format claude-md
All commands support --path to point at a different project root. lint exits with code 1 on errors (warnings pass).
This isn't just for Cursor. If you're building agents with Vercel AI SDK, LangChain, or your own framework, ai-context-kit solves the same problem: how much context are you stuffing into the system prompt, and is it helping or hurting?
import { loadRules, select } from "ai-context-kit";
import { generateText } from "ai";
const allRules = await loadRules("./rules");
const relevant = select(allRules, { task: userMessage, budget: 3000, });
const systemPrompt = relevant.map((r) => r.body).join("\n\n");
const { text } = await generateText({ model: openai("gpt-4o"), system: systemPrompt, prompt: userMessage, });
Any framework that takes a system prompt string. Any rules stored as markdown files.
| Format | File | Used by |
|---|
| Cursor (modern) | .cursor/rules/*.mdc
Only the beginning is shown; read the rest in the repo