mcpField
L
libdocs-remote

libdocs-remote

Local
github.com/CloudCorpRecordsDeveloper Tools0Updated 2w ago
Repository

About libdocs-remote

libdocs-remote is a local MCP server and CLI that forwards library documentation lookups to Context7’s hosted endpoint. It handles JSON and SSE responses, with an optional API key.

Key features

  1. 01Resolve library IDs
  2. 02Retrieve library documentation
  3. 03Parse JSON and SSE responses
  4. 04Optional Context7 API key

Use cases

  1. 01Find the Context7 ID for a library
  2. 02Fetch docs by library ID and topic

MCP support

Exposes `resolve-library-id` and `get-library-docs` to MCP clients. Each request is forwarded to the hosted Context7 MCP endpoint.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-libdocs-remote": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/libdocs-remote"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/libdocs-remote

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/libdocs-remote0.1.0
ocighcr.io/cloudcorprecords/libdocs-remote:0.1.0

Tools

2

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
libraryNamestringYesName of the library to resolve into a Context7-compatible library ID.

Details

From the project 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

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

CLI

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

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

MCP server

npx -y @reneturcios/libdocs-remote mcp

{
  "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

npm install
npm run build
npm test
npm run dev

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

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.