Configdoc

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

将代码中读取的每个配置选项及其默认值提取到一份清单中。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Extracts every config option read in the code, with its default, into one inventory.

已验证STDIO仅桌面商业与电商

概览

Configdoc 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Configdoc,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

configdoc

Every config option in the code, with its default, in one document. You pass configdoc the source files as text, and it scans them for direct environment reads — the config surface most code bases actually use — and returns a single inventory:

  • Both read forms — process.env.NAME and import.meta.env.NAME are extracted, where NAME follows the uppercase env convention ([A-Z_][A-Z0-9_]*). Lowercase or mixed-case names are not matched, and destructured reads (const { X } = process.env) and non-env config objects are out of scope by design.
  • Defaults — when a read is immediately followed by ?? or || and a literal, that literal is the read's default: a string literal contributes the raw text between its quotes (escapes are not interpreted), a number literal contributes itself as written. A fallback that is an identifier, a call, or anything else captures no default.
  • One entry per option — each distinct name appears once, sorted ascending, with the default captured by the first read of that name (in scan order: files in input order, lines top to bottom, matches left to right) that captures one — null when no read does — plus the total number of reads of that name across all files and the distinct files it is read in, sorted ascending.

Input is validated strictly: a missing or empty file set, a file missing path or content, an empty, non-string, or duplicate path, or a non-string content is an error naming the offending path (for example files[0].content must be a string), and no partial inventory is produced. The scan is pure and local: no network, no configuration, no files read beyond the input you pass in.

CLI

bash
npx @reneturcios/configdoc extract --input args.jsonnpx @reneturcios/configdoc --version

args.json contains the full arguments object:

json
{  "files": [    {      "path": "src/config.ts",      "content": "const port = process.env.PORT ?? 8080;\nconst host = process.env.HOST ?? \"localhost\";"    },    {      "path": "web/env.ts",      "content": "export const api = import.meta.env.API_URL;"    }  ]}

The inventory is printed as JSON:

json
{  "options": [    { "name": "API_URL", "default": null, "reads": 1, "files": ["web/env.ts"] },    { "name": "HOST", "default": "localhost", "reads": 1, "files": ["src/config.ts"] },    { "name": "PORT", "default": "8080", "reads": 1, "files": ["src/config.ts"] }  ],  "total_options": 3,  "files_scanned": 2}

Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid input file, or invalid input), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/configdoc mcp

MCP client config:

json
{  "mcpServers": {    "configdoc": {      "command": "npx",      "args": ["-y", "@reneturcios/configdoc", "mcp"]    }  }}

Tools

  • extract_config_options — Extract every configuration option read in the code, with the default each read falls back to, in one inventory.

    • files (array, required, at least one) — source files as {path, content} objects; path is unique across the set and content is the full source text (it may be empty)

    Returns {options, total_options, files_scanned}, where each option is {name, default, reads, files}.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/configdocdocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/configdoc extract --input /w/args.json

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

来源:README.md,提交 a8d09ac

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分