{"id":"d92d01b1-38bf-453c-a9a3-52d73f9d1025","slug":"libdocs","kind":"mcp","name":"libdocs","summary":"Resolve library names and fetch current, version-specific documentation via Context7.","owner":"CloudCorpRecords","repoUrl":"https://github.com/CloudCorpRecords/libdocs","license":"MIT","licenseTier":"permissive","trust":"community","stars":0,"match":null,"fewStars":true,"format":"mcp","createdAt":"2026-10-31T02:48:17.000Z","addedAt":"2026-10-31T04:39:40.517Z","logoUrl":"https://avatars.githubusercontent.com/u/95189389?u=8e277e1a24ff84ae7b49c89e6897fa44178a5c34&v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["browser-web","writing"],"tags":[],"runtime":"node","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-31T04:42:15.001Z","sample":false,"url":"https://conduits.dev/tools/libdocs","language":"TypeScript","transports":["stdio"],"install":{"npm":"@reneturcios/libdocs"},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# libdocs\n\nlibdocs answers the question every coding agent runs into: what does\nthe current version of this library actually do? You give it a library\nname, it finds the library's Context7-compatible ID, and then it pulls\nthe up-to-date documentation and code examples for that library —\noptionally focused on one topic and capped at a token budget you pick.\nIt works from the command line or as an MCP server for agents.\n\nAn API key is optional. When `CONTEXT7_API_KEY` is set, libdocs sends\nit as a Bearer token; when it is not set, requests simply go out\nwithout one. There is no sign-up step to get started.\n\n## Install\n\n```bash\nnpx @reneturcios/libdocs resolve \"next.js\"\n```\n\nOr run the container image:\n\n```bash\ndocker run -i ghcr.io/cloudcorprecords/libdocs\n```\n\nThe container defaults to the MCP server (see below). Pass CLI\narguments to use it as a CLI instead.\n\n## CLI\n\n```bash\n# Find the Context7-compatible IDs for a library name\nlibdocs resolve \"next.js\"\nlibdocs resolve react\n\n# Fetch documentation for an exact library ID\nlibdocs docs /vercel/next.js\nlibdocs docs /vercel/next.js --topic routing --tokens 20000\n\nlibdocs --version\n```\n\nExit codes: `0` on success, `1` when a lookup fails (the error names\nthe problem, including the HTTP status when the service answers with\none), `2` for usage errors.\n\nToken budgets below the service minimum of 10000 are raised to 10000,\nmatching the upstream behaviour.\n\n## MCP server\n\nOne bin serves both faces. The `mcp` subcommand starts a stdio MCP\nserver:\n\n```bash\nnpx -y @reneturcios/libdocs mcp\n```\n\nMCP client configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"libdocs\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@reneturcios/libdocs\", \"mcp\"],\n      \"env\": {\n        \"CONTEXT7_API_KEY\": \"your-key-if-you-have-one\"\n      }\n    }\n  }\n}\n```\n\nThe `env` block is optional — leave it out entirely to run keyless.\n\n### Tools\n\n| Tool | Input | What it returns |\n| --- | --- | --- |\n| `resolve-library-id` | `libraryName` (string, required) | The matching libraries, each with its title, Context7-compatible library ID, description, and the token, snippet, and trust figures the service reports. |\n| `get-library-docs` | `context7CompatibleLibraryID` (string, required), `tokens` (number, optional), `topic` (string, optional) | The library's documentation and code examples as plain text, focused on `topic` when one is given. |\n\nResolution talks to the service's search endpoint; documentation is\nfetched per library ID in plain-text mode. Lookup failures (unknown\nIDs, rate limits, unreachable hosts) are reported as tool errors.\n\n## Development\n\n```bash\nnpm install\nnpm run build   # tsc -> dist/\nnpm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)\nnpm run dev     # run the CLI from source via tsx\n```\n\n## License\n\nMIT — see `LICENSE`.\n"}