open-context_search_docsLABSCO SUMMARY
Fetches from the registry, not from a bundled copy.
The distinction that matters against a bundled documentation set is freshness: a package published this week is reachable because the server asks the registry, and a cache with a TTL keeps the second question fast. The breadth across DevOps tools is unusual too — Helm chart and Terraform versions are exactly the sort of thing a model states confidently and wrongly.
What it is
A Go documentation server that fetches from the sources of record — pkg.go.dev, the npm registry, PyPI, crates.io, GitHub releases and Docker Hub — rather than serving a snapshot. Results are cached locally with a configurable TTL, defaulting to 7 days, and returned as Markdown. It runs over stdio for local use or HTTP for a shared remote instance.
What you get
- Documentation over whatever you have loaded:
open-context_search_docssearches everything,open-context_get_docsretrieves a specific topic andopen-context_list_docsbrowses what is available - Language ecosystems:
open-context_get_go_infofor Go versions and packages,open-context_get_npm_info,open-context_get_python_infofor PyPI packages,open-context_get_rust_infofor crates - Runtime and framework versions:
open-context_get_node_info,open-context_get_typescript_info,open-context_get_react_info,open-context_get_nextjs_info - DevOps tooling:
open-context_get_kubernetes_info,open-context_get_helm_info,open-context_get_terraform_info,open-context_get_ansible_info,open-context_get_jenkins_info, plusopen-context_get_docker_imagefor Docker Hub images andopen-context_get_github_actionfor actions such as actions/checkout
Requirements
Nothing — no account, no key. Install through Homebrew with the project's tap, the install script, or build from source with Go 1.25 or higher. The client entry points at the binary directly for stdio; for a shared instance run ./open-context --transport http --host 0.0.0.0 --port 9011 and connect over HTTP. Nothing needs pre-fetching — documentation is retrieved on demand and cached.
Setup effort
One command — go install github.com/incu6us/open-context@latest
USE CASES
01
Checking a package's current version and API
Ask the registry directly rather than trusting a model's recollection of what the package looked like.
02
Pinning a Docker base image or a GitHub Action
Look up the published tags or action versions before writing them into a workflow file.
03
Writing Go against the right release
Fetch Go version information and package documentation from go.dev and pkg.go.dev in one call.
04
Sharing one documentation cache across a team
Run it in HTTP transport on a server so several people hit the same warm cache instead of each fetching separately.
18 tools
Listed in project docs. Your client may show a different list.
open-context_get_docsopen-context_list_docsopen-context_get_go_infoopen-context_get_npm_infoopen-context_get_python_infoopen-context_get_rust_infoopen-context_get_node_infoopen-context_get_typescript_infoopen-context_get_react_infoopen-context_get_nextjs_infoopen-context_get_ansible_infoopen-context_get_terraform_infoopen-context_get_jenkins_infoopen-context_get_kubernetes_infoopen-context_get_helm_infoopen-context_get_docker_imageopen-context_get_github_actionBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
go on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
go install github.com/incu6us/open-context@latestMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"open-context": {
"command": "<YOUR_PATH_TO_OPEN_CONTEXT>"
}
}
}Claude Code — Local binary
CLAUDE CODE — LOCAL BINARY · TERMINAL
claude mcp add --transport stdio open-context -- <YOUR_PATH_TO_OPEN_CONTEXT>Claude Code — Remote HTTP
CLAUDE CODE — REMOTE HTTP · TERMINAL
claude mcp add --transport http open-context <YOUR_SERVER_URL>:9011
