原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

AI Context Kit

作者:ofershap版本 0.1.2i★ –i在你的电脑上运行
注册名称io.github.ofershap/ai-context-kit

安装

概览

作者提供的说明(英文原文)

Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ai-context-kit": {
      "command": "npx",
      "args": [
        "-y",
        "ai-context-kit"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add ai-context-kit -- npx -y ai-context-kit

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ai-context-kit": {
      "command": "npx",
      "args": [
        "-y",
        "ai-context-kit"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ai-context-kit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ai-context-kit"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 ofershap 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32484 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32484 个服务器的 4% 更新
  • 基础检查结果等于或优于此分类中其他 32484 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

AI Context Kit 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.2)于8个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Recta

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

Recta

作者:RectaBuild

Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.

电脑或云端今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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:

  • Auto-generated context files reduced task success compared to providing nothing
  • Human-written ones only improved accuracy by 4%
  • Inference costs jumped 20%+ from wasted tokens
  • Performance dropped on some models because agents got too obedient - following unnecessary instructions instead of solving the actual problem

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 });


Quick Start

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

890 tokens (18%) - .cursor/rules/api-patterns.mdc

340 tokens (7%) - AGENTS.md

180 tokens (4%) - .cursor/rules/testing.mdc

111 tokens (2%) - .github/copilot-instructions.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.


What's Different

Other approachesai-context-kit
Context costNobody measures itToken count per file with budget check
ConflictsYou find out when the agent does something weirdDetects contradictions across all files automatically
DuplicatesSame rule in 3 files, 3x the tokensFlagged and scored
Task relevanceEvery rule injected every timeselect() picks only what matters for the current task
Multi-toolLocked to one IDE's formatWorks across Cursor, Claude Code, Copilot, Windsurf, Cline
CIHope for the bestlint exits with code 1 on errors. Drop it in your pipeline

What This Answers

  1. How much context am I injecting? Token count per file, percentage breakdown, budget check
  2. Are my rules fighting each other? Conflict detection across all files and formats
  3. What's wasting tokens? Directory listings, duplicate content, vague advice
  4. Which rules matter for this task? Task-relevant selection with token budget

How It Works

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

API

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:

RuleSeverityWhat it finds
token-budgetwarning/errorFiles over 2,000 tokens (warning) or 5,000 (error)
empty-rulewarningFiles too short to do anything
duplicate-contentwarningSame instruction repeated across files
conflicterror"always use X" in one file, "never use X" in another
directory-listingwarning10+ line directory trees that agents don't need
vague-instructioninfo"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


CLI

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).


Use with Vercel AI SDK / LangChain / Custom Agents

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.


Supported Formats

FormatFileUsed by

| Cursor (modern) | .cursor/rules/*.mdc

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx