kernelee-mcp-tools
Architecture-index MCP tools for kernelee apps that combine static analysis and runtime wiring into a JSON index, enabling coding agents to query control flow and dependencies via the Model Context Protocol.
README
kernelee-mcp-tools
Architecture-index MCP tools for kernelee
apps — a ts-morph static scan and the kernel's own runtime wiring projection,
assembled into one JSON index and served to coding agents over the
Model Context Protocol. The TS port of
swift-kernelee's
KernelIntrospect / KernelIntrospectMCP.
A kernelee app's control flow is data (symbols, pipes, buffer states), so it can be indexed and queried instead of grepped: "who drives this endpoint?", "who writes this state?", "what is one hop downstream of this symbol?".
What it does
Three cooperating pieces:
- Foundation (
kernelee-mcp-tools) — builds anIndexDocumentfrom: the runtime wiring projection (projectWiringGraphover the app's live pipe catalog), a ts-morph static scan of the app's tsconfig program (input types,readsState/writesState, drive sites —dispatch/call/runand ReactuseDispatch— per-stage flows, fork branch selectors, declaration/implementation addresses), and a git stamp. Written atomically toindex.json. - MCP server (
kernelee-mcp-tools/server) —runKernelIntrospectMCPServer(configuration): a stdio MCP server that re-readsindex.jsonper query and prepends a staleness verdict (fresh/stale/unknownvs. the current working tree) to every answer. - CLI (
kernelee-introspect) —kernelee-introspect <config-module>regenerates the index from a consumer-supplied config and prints a one-line summary. Wire it into the app's build so the index can never silently rot.
The tools
| Tool | Args | Answers |
|---|---|---|
arch_overview |
— | The map: ring × device symbol counts, every endpoint headline, state / shared-stage / part lists. Start here. |
arch_endpoint |
key |
One endpoint in full: the stage tree (kinds, flows, notes, fork branches), its binding, and who drives / diverts-to / reads / writes around it. |
arch_state |
state |
One buffer state: declaration, named mutations, writers, and readers split into circuit vs. presentation. |
arch_trace |
from, edges?, depth? |
A typed-edge BFS neighborhood (drivenBy, divertsTo, callsSymbol, reads, writes, usesSharedStage) around any node. |
arch_refresh |
— | Runs the consumer's refresh command, then reloads the index. |
Misses come back with nearest-key suggestions rather than bare errors.
Consumer integration
The package hardcodes nothing about your app — everything arrives by injection. A consumer supplies two small pieces:
-
An
IntrospectConfigmodule for the CLI — repo root, tsconfig path, catalog file/function, state files, output path, and optional CI gates (failOnWiringIssues,failOnOffBufferControlValues, each with an allowlist):// package.json "scripts": { "introspect": "tsx node_modules/.bin/kernelee-introspect scripts/introspect.config.ts", "build": "npm run introspect && vite build" } -
A thin MCP launcher that bakes its defaults and starts the server — registered in the MCP client (e.g. Claude Code's
.mcp.json) as a stdio server:// scripts/introspect-mcp-server.mjs import { runKernelIntrospectMCPServer, configurationFromEnvironmentOverridingDefaults } from 'kernelee-mcp-tools/server'; await runKernelIntrospectMCPServer(configurationFromEnvironmentOverridingDefaults({ indexPath: '.claude/introspect/index.json', repoRoot: process.cwd(), refreshCommand: 'npm run introspect', refreshTimeoutSeconds: 300, }));Every default can be overridden via
KERNEL_INTROSPECT_INDEX_PATH,KERNEL_INTROSPECT_REPO_ROOT,KERNEL_INTROSPECT_REFRESH_COMMAND,KERNEL_INTROSPECT_REFRESH_TIMEOUT_SECONDS.
The reference consumer is
kernelee-lifegame — see its
scripts/introspect.config.ts, scripts/introspect-mcp-server.mjs, and
docs/kernel-introspect-mcp.md (an end-user guide with example outputs and
client-registration recipes).
Development
npm run build # tsc → dist/ (the bin needs this before first use)
npm test # vitest run — unit + MCP end-to-end integration tests
npm run typecheck # tsc --noEmit
Dependencies: @modelcontextprotocol/sdk, ts-morph, zod;
kernelee is a peer dependency. fixtures/authoringShapes/ is a minimal
kernelee app the scan tests run against; docs/ holds implementation
gotcha notes.
License
MIT © s-age
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。