MCP SERVERAsk a question about an Elixir dependency in plain language and get the passages of its documentation that answer it, from an index you build per package and version.
LABSCO SUMMARY
Search answers only for packages whose embeddings already exist, so fetch is a real first step rather than an optimisation, and because both tools take a version, a dependency bump means fetching again. What that buys is a question asked the way you would ask a colleague, answered with the passages that bear on it.
Two tools over Elixir Hex package documentation: one downloads a package's docs and turns them into vector embeddings, the other answers a natural-language query against what has been embedded.
Node on your PATH, Ollama running with the mxbai-embed-large model pulled, and Elixir 1.16+ with Mix to fetch the docs. No account and no key; a package has to be fetched before you can search it.
One command — npx -y hexdocs-mcp@0.5.0
USE CASES
Fetch the package at the version in your mix file, then ask the question you would otherwise have taken to the docs site. The answer comes back as the passages that bear on it rather than as a page to skim.
Both tools take a version, so the version you are on and the version you are moving to can each be embedded, then given the same question. What differs in the answers is what changed in the docs.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fetchDownloads and processes the documentation for a specified Elixir Hex package and version, converting it to markdown, splitting it into semantic chunks, and generating vector embeddings. This enables fast and accurate semantic search with the search tool. Must be run before searching a package for the first time or to update embeddings.
searchSearches the documentation of one or more Elixir Hex packages using semantic vector embeddings. Given a natural language query, returns the most relevant documentation snippets. Requires that embeddings have been generated for the target package(s) using the fetch tool.
BEFORE YOU INSTALL
2 tools when we connected.
All 3 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y hexdocs-mcp@0.5.0{
"mcpServers": {
"hexdocs-mcp": {
"command": "npx",
"args": [
"-y",
"hexdocs-mcp@0.5.0"
]
}
}
}MCP servers
codybrom
FuelLabs
lrstanley
herring101