Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Render a markdown API reference from caller-supplied TypeScript type declarations.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"types2docs": {
"command": "npx",
"args": [
"-y",
"@reneturcios/types2docs",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add types2docs -- npx -y @reneturcios/types2docs mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"types2docs": {
"command": "npx",
"args": [
"-y",
"@reneturcios/types2docs",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"types2docs": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/types2docs",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, 오늘냥이 (Oneul Nyangi)
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Real cat photos, diaries, profiles, age and food reference calculators, and breeds.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Documenting a TypeScript API usually means keeping a markdown reference in step with the types by hand, and the two drift apart. types2docs takes the other route: you supply the declaration facts you already have — each declaration's name, whether it is an interface, a type alias, an enum, or a function, its doc comment, and the kind-specific payload (the members, the alias's right-hand side, or the function signature) — and it renders the reference from those facts alone, in one pinned layout. Nothing is invented and nothing is reworded: every string in the document comes from your input, verbatim.
The layout never varies. The document opens with a # title line — "API Reference" unless you supply a title — followed by one section per declaration, in the order you supplied them. Each section is a ## heading with the declared name, the doc text as its own paragraph when one is present, a Kind: line, and then the kind body. An interface renders as a table with one row per member — member name, type text, and whether the member is required (yes when optional is absent or false, no when it is true) — followed by one line per documented member collecting its doc comment. An enum renders one line per member, with = when a value is present and the member's doc comment appended when it has one. An interface or enum with no members renders the single line (no members). A type alias and a function each render as a fenced ts block: for an alias, type = ; for a function, the signature exactly as supplied. Paragraphs and sections are separated by exactly one blank line, and the document ends with exactly one trailing newline. Alongside the markdown, the result carries counts: how many declarations were supplied, one tally per kind, and how many members the interfaces and enums hold in total.
The kind rules are structural, and breaking one is a validation error, not a rendering choice. members is required for interfaces and enums and forbidden for type aliases and functions. definition is required for a type alias and forbidden for every other kind; signature is required for a function and forbidden for every other kind. Inside members, type is required for interface members and forbidden for enum members, value belongs to enum members only, and optional is forbidden on enum members. Two declarations with the same name, or two members with the same name inside one declaration, are errors too. Every validation error names the offending path — for example types[1].members[0].type is required for interface members — and no partial document is produced. Unknown extra fields are ignored, including inside declarations and members.
npx @reneturcios/types2docs render --input args.json
npx @reneturcios/types2docs --version
args.json contains the full arguments object:
{
"title": "Widget API", "types": [ { "name": "Widget", "kind": "interface", "doc": "A widget in the catalogue.", "members": [ { "name": "id", "type": "string", "doc": "Unique identifier." }, { "name": "label", "type": "string", "optional": true } ] }, { "name": "WidgetId", "kind": "type", "definition": "string & { readonly brand: \"WidgetId\" }" }, { "name": "Colour", "kind": "enum", "members": [ { "name": "Red", "value": "\"red\"" }, { "name": "Blue", "value": "\"blue\"", "doc": "The calm one." } ] }, { "name": "makeWidget", "kind": "function", "signature": "function makeWidget(id: WidgetId): Widget" } ] }
The render is printed as JSON:
{
"markdown": "# Widget API\n\n## Widget\n\nA widget in the catalogue.\n\nKind: interface\n\n| Member | Type | Required |\n| --- | --- | --- |\n| id | string | yes |\n| label | string | no |\n\n- id — Unique identifier.\n\n## WidgetId\n\nKind: type\n\nts\ntype WidgetId = string & { readonly brand: \"WidgetId\" }\n\n\n## Colour\n\nKind: enum\n\n- Red = \"red\"\n- Blue = \"blue\" — The calm one.\n\n## makeWidget\n\nKind: function\n\nts\nfunction makeWidget(id: WidgetId): Widget\n\n", "counts": { "types": 4, "interfaces": 1, "type_aliases": 1, "enums": 1, "functions": 1, "members": 4 } }
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.
npx -y @reneturcios/types2docs mcp
MCP client config:
{
"mcpServers": { "types2docs": { "command": "npx", "args": ["-y", "@reneturcios/types2docs", "mcp"] } } }
render_api_reference — Render a markdown API reference from caller-supplied TypeScript type declarations: interfaces, type aliases, enums, and functions, in a pinned deterministic layout. Nothing is invented; every string comes from the input.types (array, required, at least 1 item) — the type declarations to document, in document order; each item:name (string, required, non-empty) — declared namekind (string, required) — one of "interface", "type", "enum", or "function"doc (string, optional) — doc comment text for the declarationmembers (array) — required for interface and enum, forbidden for type and function; each item:name (string, required, non-empty) — member nametype (string) — member type text; required for interface members, forbidden for enum membersvalue (string, optional) — enum member value text (enum members only)optional (boolean, optional) — whether the member is optional (interface members only); absent means falsedoc (string, optional) — doc comment text for the memberdefinition (string) — the alias's right-hand side, verbatim; required for kind "type", forbidden otherwisesignature (string) — the function signature, verbatim; required for kind "function", forbidden otherwisetitle (string, optional) — document title; defaults to "API Reference"; an empty string is allowed and renders as # Returns {markdown, counts}, where markdown is the rendered document and counts is {types, interfaces, type_aliases, enums, functions, members} in that key order.
docker run -i ghcr.io/cloudcorprecords/types2docs
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/types2docs render --input /w/args.json
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (pure local, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios