Back to Browse

Libdocs Remote MCP Server

Developer ToolsModerate5.5MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.5
Moderate5.5Moderate Risk

This is a thin forwarding wrapper that sends library lookups as JSON-RPC requests to the hosted Context7 endpoint over HTTPS, with no hardcoded secrets, shell execution, or filesystem access. The main considerations are that queries and the optional API key leave the machine for a third-party service, which is the documented purpose, and a few low-severity hardening items around redirects and unpinned installs. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "libdocs-remote": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/libdocs-remote@0.1.0"
      ]
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub 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.

Reviews

No reviews yet

Be the first to review this server!