resolve-library-id
Resolve a library name into a Context7-compatible library ID, returning the matching libraries.
libraryName必填
io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 7, 2026
Resolve library names and fetch current, version-specific documentation via Context7.
本機 MCP 伺服器,將套件名稱解析為 Context7 套件 ID,並抓取最新、對應版本的說明文件與程式碼範例,供編碼助理使用。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
參照 儲存庫 中的啟動說明。
libdocs answers the question every coding agent runs into: what does the current version of this library actually do? You give it a library name, it finds the library's Context7-compatible ID, and then it pulls the up-to-date documentation and code examples for that library — optionally focused on one topic and capped at a token budget you pick. It works from the command line or as an MCP server for agents.
An API key is optional. When CONTEXT7_API_KEY is set, libdocs sends
it as a Bearer token; when it is not set, requests simply go out
without one. There is no sign-up step to get started.
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Exit codes: 0 on success, 1 when a lookup fails (the error names
the problem, including the HTTP status when the service answers with
one), 2 for usage errors.
Token budgets below the service minimum of 10000 are raised to 10000, matching the upstream behaviour.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
MCP client configuration:
The env block is optional — leave it out entirely to run keyless.
Resolution talks to the service's search endpoint; documentation is fetched per library ID in plain-text mode. Lookup failures (unknown IDs, rate limits, unreachable hosts) are reported as tool errors.
MIT — see LICENSE.
來源:README.md,提交 bcd2961
Resolve a library name into a Context7-compatible library ID, returning the matching libraries.
libraryName必填Fetch current documentation and code examples for a library using its Context7-compatible library ID.
topictokenscontext7CompatibleLibraryID必填已滿足適用檢查項的 90%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
npx @reneturcios/libdocs resolve "next.js"docker run -i ghcr.io/cloudcorprecords/libdocs# Find the Context7-compatible IDs for a library namelibdocs resolve "next.js"libdocs resolve react
# Fetch documentation for an exact library IDlibdocs docs /vercel/next.jslibdocs docs /vercel/next.js --topic routing --tokens 20000
libdocs --versionnpx -y @reneturcios/libdocs mcp{ "mcpServers": { "libdocs": { "command": "npx", "args": ["-y", "@reneturcios/libdocs", "mcp"], "env": { "CONTEXT7_API_KEY": "your-key-if-you-have-one" } } }}npm installnpm run build # tsc -> dist/npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev # run the CLI from source via tsx