open-context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Custom host for HTTP transport (e.g., 0.0.0.0). | |
| port | No | Custom port for HTTP transport (e.g., 9011). | |
| transport | No | Transport mode to use (stdio or http). Defaults to stdio. | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open-context_search_docsB | Search for documentation topics across all available documentation sources |
| open-context_get_docsC | Get detailed documentation for a specific topic or library |
| open-context_list_docsA | List all available documentation languages and their topics |
| open-context_get_go_infoA | Fetch and cache information about specific Go versions or Go libraries from official sources |
| open-context_get_npm_infoB | Fetch and cache information about npm packages from the npm registry |
| open-context_get_python_infoB | Fetch and cache information about Python packages from PyPI (Python Package Index) |
| open-context_get_rust_infoA | Fetch and cache information about Rust crates from crates.io |
| open-context_get_node_infoA | Fetch and cache information about Node.js versions from nodejs.org |
| open-context_get_typescript_infoB | Fetch and cache information about TypeScript versions from GitHub releases |
| open-context_get_nextjs_infoA | Fetch and cache information about Next.js versions from GitHub releases |
| open-context_get_react_infoB | Fetch and cache information about React versions from GitHub releases |
| open-context_get_ansible_infoA | Fetch and cache information about Ansible versions from GitHub releases |
| open-context_get_terraform_infoB | Fetch and cache information about Terraform versions from GitHub releases |
| open-context_get_jenkins_infoA | Fetch and cache information about Jenkins versions from GitHub releases |
| open-context_get_kubernetes_infoB | Fetch and cache information about Kubernetes versions from GitHub releases |
| open-context_get_helm_infoA | Fetch and cache information about Helm versions from GitHub releases |
| open-context_get_docker_imageA | Fetch and cache information about Docker images from Docker Hub, including available tags and image details |
| open-context_get_github_actionA | Fetch and cache information about GitHub Actions from GitHub API, including action metadata, inputs, and outputs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| use-docs | Use open-context documentation for the current conversation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct technology or documentation function, with no overlap. Info fetchers for different technologies are clearly separated, and documentation tools have unique purposes.
All tools follow a consistent verb_noun snake_case pattern with the server prefix, e.g., 'open-context_get_ansible_info' and 'open-context_list_docs'. There is no mixing of styles.
18 tools is slightly high but still reasonable for a server covering many technologies and documentation. Each tool serves a clear purpose without unnecessary duplication.
The tool set covers fetching info on a wide array of popular technologies and provides documentation retrieval features. Minor gaps exist (e.g., missing Java/Maven), but core functionality is well-covered.