search_docsLABSCO SUMMARY
The index is a build step you own, not a background service.
Nothing is indexed until you run the build command, and nothing refreshes until you run it again — which is the trade for having the whole documentation set on disk and searchable without a hosted search dependency. Search returns five results by default, so ask for more when you are looking for a section rather than an answer.
What it is
An MCP server that fetches the .mdx files from the docs/ directory of the bucketeer-io/bucketeer-docs repository, builds a keyword and full-text index over them, and answers questions from that index. Content is cached locally with SHA hashes so a rebuild only touches files that actually changed.
What you get
- Bucketeer documentation searched by relevance, returning title, URL, path, description, excerpt and score for each hit, with the result count capped by
limit—search_docs - The full markdown body of one document by the
pathreturned in a search result, with its title, description and URL —get_document
Requirements
Node.js 18+ and npm. No account and no key — the docs it indexes are public. The package is @bucketeer/docs-local-mcp-server (1.3.0) and runs over stdio via npx. Build the index before the first run: npx @bucketeer/docs-local-mcp-server build-index, and add --force when you want a rebuild that ignores the cache. Cached documents land in files/docs/, the index in files/index/document-index.json.
Setup effort
Follow the published steps — npx @bucketeer/docs-local-mcp-server build-index
USE CASES
01
Answering feature-flag questions from the current docs
Search for the behaviour you are unsure about, then pull the matching page in full so the answer quotes the documentation rather than paraphrasing a memory of it.
02
Finding the right SDK integration page
Search on the SDK and the task together, read the excerpt and score on each hit, and open only the page that actually covers your platform.
03
Keeping an offline copy of the documentation current
Re-run the index build after a docs release; only files whose SHA changed are refetched, so the update is cheap enough to run routinely.
2 tools
Listed in project docs. Your client may show a different list.
get_documentBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @bucketeer/docs-local-mcp-server build-indexAdd the server to your MCP client with one of the configurations below (Cursor mcp.json or claude_desktop_config.json)
MCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"bucketeer-docs": {
"type": "stdio",
"command": "npx",
"args": [
"@bucketeer/docs-local-mcp-server"
]
}
}
}
