semantic_searchLABSCO SUMMARY
Answers about a library come from that library's documentation, not from memory.
The curated source list is the point — a search lands in the official docs for the package you named rather than in a blog post about an older version. The dependency scan and the project starters ride along in the same server, which keeps a fresh project's first hour in one place.
What it is
A documentation search server over a curated set of library documentation sites, with optional semantic search, dependency vulnerability scanning and project scaffolding alongside it.
What you get
- Documentation fetched from the official docs site for the library you name
- Semantic vector search over that corpus, as an optional extra install
- Python projects scanned for vulnerabilities against Snyk, Safety and OSV
- FastAPI and React project starters generated
- Learning paths and code examples for the libraries it covers
Requirements
Python, run through uvx or installed with pip. An optional search-provider API key enables live web search. Semantic search is a separate extra install, pinned to a single Python version, that brings its own model dependencies.
Setup effort
One command — uvx documentation-search-enhanced@1.9.0
USE CASES
01
Getting the current signature of a function you half remember
Search the library's own documentation and copy from what it says today.
02
Finding the right page when you cannot name it
Describe what you are trying to do and let semantic search find the section that covers it.
03
Checking a project for known vulnerabilities before you ship
Scan the dependencies against Snyk, Safety and OSV in one pass.
04
Starting a new service without copying an old one
Generate a FastAPI or React starter, then read the docs for the pieces you add on top.
10 tools
Listed in project docs. Your client may show a different list.
get_docsget_learning_pathget_code_examplesscan_project_dependenciessnyk_scan_projectgenerate_project_startermanage_dev_environmentcompare_library_securityget_current_configBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
uvx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx documentation-search-enhanced@1.9.0MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"documentation-search-enhanced": {
"command": "/Users/<YOUR_USERNAME>/.local/bin/uvx",
"args": [
"documentation-search-enhanced@1.9.0"
],
"env": {
"SERPER_API_KEY": "<YOUR_SERPER_API_KEY>"
}
}
}
}/Users/<YOUR_USERNAME>/.local/bin/uvx is your own uvx path — run which uvx to find it. SERPER_API_KEY is optional: without it the server uses its prebuilt index, so you can delete the env block.
Codex
CODEX · TERMINAL
codex mcp add documentation-search-enhanced \
-- uvx documentation-search-enhanced@1.9.0
