Libdocs Remote

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

Forward Context7 library documentation lookups to the hosted remote MCP endpoint.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that forwards library documentation lookups to the hosted Context7 remote endpoint, returning library IDs and docs.

What you can do
  • Resolve a library name into a Context7-compatible library ID, with matching libraries returned.
  • Fetch current documentation and code examples for a library by its ID, optionally narrowed by topic and token budget.
  • Report upstream HTTP, JSON-RPC and connectivity failures as tool errors with the underlying message.
When to use it
Useful when an assistant needs up-to-date library documentation and code examples while coding, and you prefer a small local stdio server in front of the hosted Context7 service rather than calling it directly.
Requirements
Runs as a local process via npx (npm package) or Docker (OCI image). Network access to the hosted Context7 remote MCP endpoint is required. CONTEXT7_API_KEY is optional; when set it is sent as a header to that endpoint.
Before you install
Lookup queries and library names are sent to the third-party hosted Context7 endpoint. The optional CONTEXT7_API_KEY is passed to that service, so treat it as a secret. The server only reads documentation; it does not write data.

Installation

In SourceWeft

  1. Open Libdocs Remote 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-remote

libdocs-remote is the hosted variant of the library-docs lookup. Instead of calling a REST API locally, it forwards each request as a JSON-RPC tools/call to the hosted Context7 remote MCP endpoint at https://mcp.context7.com/mcp and returns the answer it gets back. It understands both plain JSON answers and text/event-stream (SSE) answers, reading the JSON-RPC payloads out of the data: lines.

Use it when you want the hosted service to do the work and only need a local stdio server (or a small CLI) in front of it.

CONTEXT7_API_KEY is optional. When it is set, it is sent as the CONTEXT7_API_KEY header documented for the hosted endpoint; when it is absent, no such header is sent and that is not an error.

Install

bash
npx @reneturcios/libdocs-remote resolve "next.js"docker run -i ghcr.io/cloudcorprecords/libdocs-remote

CLI

bash
libdocs-remote resolve "next.js"libdocs-remote docs /vercel/next.jslibdocs-remote docs /vercel/next.js --topic routing --tokens 20000libdocs-remote --version

Exit codes: 0 success, 1 lookup error, 2 usage error.

MCP server

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

The env block is optional.

Tools

ToolInputWhat it returns
resolve-library-idlibraryName (string, required)The matching libraries as returned by the hosted endpoint.
get-library-docscontext7CompatibleLibraryID (string, required), tokens (number, optional), topic (string, optional)Documentation text as returned by the hosted endpoint.

Upstream failures — HTTP errors, JSON-RPC errors, unreachable hosts — are reported as tool errors with the underlying message.

Development

bash
npm installnpm run buildnpm testnpm run dev

Tests run entirely on fake-fetch fixtures, including plain-JSON and SSE upstream bodies; no network is used.

License

MIT — see LICENSE.

Source: README.md at commit 5802022

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.0LatestNov 1, 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