icfmcp

icfmcp

Enables AI assistants to search, summarize, and retrieve records from ICF knowledge files using tag-based and full-text search, with support for ICX indexes.

Category
访问服务器

README

icfmcp

An MCP (Model Context Protocol) server that lets AI harnesses — Claude Code, Claude Desktop, and any other MCP client — search and read Indent Comma Format (ICF) knowledge files via their ICX indexes.

Point it at one or more .icf files (or directories of them) and it exposes tag search, one-line summaries, full-text search, record retrieval, and validation as MCP tools over stdio. When a sibling .icx index file exists it is used directly; otherwise an index is generated in memory with icf.js.

Requirements

  • Node.js >= 20

Install & run

npm install
npm run build

# serve a directory (scanned recursively for *.icf) and/or individual files
node dist/index.js path/to/knowledge-dir another/file.icf
# or, via the bin:
npx icfmcp path/to/knowledge-dir

The server speaks MCP on stdin/stdout; status lines go to stderr.

Registering with Claude Code

claude mcp add icf -- node <absolute-path>/icfmcp/dist/index.js <absolute-path-to-knowledge-dir>

Or in Claude Desktop's claude_desktop_config.json:

{
  "mcpServers": {
    "icf": {
      "command": "node",
      "args": ["<absolute-path>/icfmcp/dist/index.js", "<absolute-path-to-knowledge-dir>"]
    }
  }
}

Tools

Tool Input Behavior
list_documents Registry overview: name, path, record count, schema ids, whether the index came from a .icx file or was generated, tag count.
list_tags document? All tags with the number of records carrying each, sorted by count descending.
search_by_tag tag, document?, matchMode? Records carrying a tag. exact (default) is case-insensitive equality; contains is a case-insensitive substring match. Returns document, recordId, uuid, summary, tags, and Line/Offset/Size when known.
get_record document, recordId One record in full: resolved data as JSON, @record attributes, its index row, and the raw ICF block text. Also resolves master rows by id.
get_summaries document?, tag? recordId → one-line summary for every record that has one, optionally filtered by tag.
search_text query, document? Case-insensitive full-text search over raw record blocks; returns matching lines with recordId and absolute line numbers.
validate_document document? or icf? Errors and warnings from the ICF validator, for a served document or inline ICF text.

Every tool returns a single JSON text block. Recoverable problems (unknown document or record, missing arguments) come back as { "error": "..." } with isError: true — never a protocol failure.

How the ICX 1.2 Tags/Summary flow works

ICX is ICF's companion index format. Version 1.2 adds two optional per-row fields and two inverted collections that make an index self-sufficient for triage (ICX v1.2 §7–§9, §15):

  • Tags — search keywords per index row, joined with + (a literal + is escaped as \+). Tags are ideally typed master references like Project:ICF, so they resolve against the index's own master rows.
  • Summary — a one-line synopsis of the record.
  • tagindex[] — inverted map: tag → +-joined record ids.
  • summaryindex[] — record id → summary.

The intended harness flow — and what this server implements for you:

  1. Read the small index once (list_documents, list_tags).
  2. Filter rows by tag (search_by_tag) — from the per-row Tags field and tagindex[], merged.
  3. Triage candidates by summary (get_summaries) without opening the ICF.
  4. Fetch only the winning records (get_record) — the raw block, resolved data, and byte positions.

When no .icx exists, the server generates the index in memory and fills the same information straight from the source: every field value that is a typed reference to a declared master type becomes a tag (ICX §7 generator behavior), and a record's summary attribute or Summary field becomes its summary. Documents and indexes are cached by mtime+size and reloaded automatically when files change — including when a .icx appears next to an .icf after startup.

Development

npm run dev -- tests/fixtures   # run from source (tsx)
npm test                        # vitest
npm run typecheck               # src + tests
npm run build                   # tsc -> dist/

See CLAUDE.md for the architecture notes.

License

MIT © Edison Williams

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选