libdocs-remote
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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-remoteRelated MCP server: astrolabe-mcp
CLI
libdocs-remote resolve "next.js"
libdocs-remote docs /vercel/next.js
libdocs-remote docs /vercel/next.js --topic routing --tokens 20000
libdocs-remote --versionExit 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
Tool | Input | What it returns |
|
| The matching libraries as returned by the hosted endpoint. |
|
| 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 devTests run entirely on fake-fetch fixtures, including plain-JSON and SSE upstream bodies; no network is used.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
A paid remote MCP for Context7 MCP docs, built to return verdicts, receipts, usage logs, and audit-r
Public MCP endpoint for collaborative research and knowledge discovery.
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that bridges to the Context7 API, enabling querying documentation context, searching projects, and retrieving project metadata.115 npm5MIT
- FlicenseNot gradedqualityCmaintenanceProvides unified search and navigation across multiple project documentations via the Model Context Protocol (MCP). Any MCP-compatible agent can discover and retrieve knowledge from all indexed projects.1-
- AlicenseAqualityCmaintenanceMCP server for local, offline-capable library documentation. It resolves library IDs and retrieves up-to-date docs via hybrid search from a persistent SQLite cache.31MIT

cortexify-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables any MCP client to read and write a Cortexify library, including saved links, documents, notes, collections, and the Cortex AI copilot.-