Libdocs

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Resolve library names and fetch current, version-specific documentation via Context7.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that resolves library names to Context7 IDs and fetches current, version-specific documentation and code examples for coding agents.

What you can do
  • Resolve a library name into Context7-compatible library IDs, with titles, descriptions and trust figures
  • Fetch a library's current documentation and code examples by ID, optionally focused on a topic and capped at a token budget
  • Report lookup failures such as unknown IDs, rate limits or unreachable hosts as tool errors
When to use it
Useful when an assistant writes or reviews code against third-party libraries and needs up-to-date, version-specific docs instead of possibly stale training knowledge. It fits coding agents that want to look up a library's API before answering.
Requirements
Runs as a local stdio process, started with npx or the Docker image. Network access to the Context7 service is required. An optional CONTEXT7_API_KEY environment variable is sent as a Bearer token when set; no sign-up is needed to run keyless.
Before you install
If you set CONTEXT7_API_KEY, that credential is sent to the Context7 service as a Bearer token. Library names and IDs, and the topics you query, go to that third-party service. Token budgets below the service minimum of 10000 are raised to 10000.

Installation

In SourceWeft

  1. Open Libdocs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

libdocs

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.

Install

bash
npx @reneturcios/libdocs resolve "next.js"

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/libdocs

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
# 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 --version

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.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/libdocs mcp

MCP client configuration:

json
{  "mcpServers": {    "libdocs": {      "command": "npx",      "args": ["-y", "@reneturcios/libdocs", "mcp"],      "env": {        "CONTEXT7_API_KEY": "your-key-if-you-have-one"      }    }  }}

The env block is optional — leave it out entirely to run keyless.

Tools

ToolInputWhat it returns
resolve-library-idlibraryName (string, required)The matching libraries, each with its title, Context7-compatible library ID, description, and the token, snippet, and trust figures the service reports.
get-library-docscontext7CompatibleLibraryID (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.

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.

Development

bash
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

License

MIT — see LICENSE.

Source: README.md at commit bcd2961

Tools

2

resolve-library-id

Resolve a library name into a Context7-compatible library ID, returning the matching libraries.

ParameterslibraryNamerequired

get-library-docs

Fetch current documentation and code examples for a library using its Context7-compatible library ID.

Parameterstopictokenscontext7CompatibleLibraryIDrequired

Version history

1
  1. v0.1.0LatestOct 31, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts