resolve-library-uriLABSCO SUMMARY
Two tools, one URL, no local install.
The whole value is the transport: usage otherwise matches the official Context7 documentation, so swapping the server block is the entire migration. The v1 API dependency is the thing to keep an eye on, and it is stated plainly at the top of the README rather than buried.
What it is
An HTTP-streaming MCP server for the Context7 documentation project. Where the usual setup runs a local process per client, this one is a single endpoint you point clients at — your own instance, or the author's public one.
What you get
- resolve-library-uri turns a library name into the identifier Context7 uses
- search-library-docs searches that library's documentation
- HTTP streamable transport, so a config entry is a URL rather than a command and a runtime
- Run your own with --bind-addr, --trusted-proxies for a reverse proxy, and --heartbeat-interval for networks that drop idle connections
Requirements
Either the public endpoint at https://context7.liam.sh/mcp with no key at all, or your own instance from the container image ghcr.io/lrstanley/context7-http. It talks to the v1 Context7 API, which needs no API key — the README warns that v1 may eventually be withdrawn, and that v2 requires keys and is more heavily rate-limited.
Setup effort
One command — docker run -it --rm ghcr.io/lrstanley/context7-http:latest
USE CASES
01
Giving an agent current library docs
Resolve the library, then search its documentation, without shipping a docs corpus to the machine.
02
Using Context7 from a client that cannot spawn processes
A URL-only server block works where a command-plus-runtime block does not.
03
Hosting it for a team
One container behind your own domain, with trusted-proxy handling and a heartbeat for flaky networks.
2 tools
Listed in project docs. Your client may show a different list.
search-library-docsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
Both documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
docker
TERMINAL
docker run -it --rm ghcr.io/lrstanley/context7-http:latestHosted endpoint
ENDPOINT URL
https://context7.liam.sh/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"context7": {
"url": "https://context7.liam.sh/mcp"
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"context7": {
"url": "https://context7.liam.sh/mcp"
}
}
}
