docs-rag-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@docs-rag-mcp search for documentation about TF-IDF indexing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
docs-rag-mcp
MCP server that searches a local markdown corpus with TF-IDF retrieval and serves full documents as resources.
Architecture: docs/*.md → chunk + TF-IDF index (rag.py) → FastMCP exposes search_docs tool and doc://{path} resource (server.py).
MCP surface
Kind | Name | Description |
Tool |
|
|
Resource |
| Full markdown for a relative path (e.g. |
Related MCP server: Inkdex
Run
uv sync
uv run fastmcp run server.py # stdio (Claude Desktop, Cursor)
uv run fastmcp run server.py -t http -p 8000 # HTTP for MCP InspectorTest
uv run fastmcp list server.py
uv run fastmcp call server.py search_docs --query "TF-IDF" --k 3Add your own notes under docs/ and restart the server (or re-run) to re-index.
Claude Desktop
See docs/claude-desktop-config.md for claude_desktop_config.json snippet. Use an absolute --directory path.

Available Tools
1 toolsearch_docsA
Search the documentation corpus with TF-IDF retrieval.
Inputs: query (required), k. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between overlapping tools. The purpose of search_docs is singular and clear.
The single tool name 'search_docs' follows a clear verb_noun pattern, which is consistent for the server's scope. There are no other names to compare, so it is perfectly consistent.
A single tool for a docs RAG server is borderline but acceptable, as search is the primary function. However, it feels slightly thin, and additional tools like list_docs or get_doc could enhance usability.
For a documentation search server, search_docs covers the core retrieval need. Minor gaps exist such as no ability to list available document sources or fetch a specific document directly, but these are not critical for basic RAG workflows.
Maintenance
Related MCP Connectors
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Read-only search and Markdown access to liz's public docs, prompts, resources, and an MCP App.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides structured, addressable access to a local markdown vault with heading-anchored fragments, BM25 search, and stable IDs for verifiable retrieval.24 npm2MIT
- AlicenseAqualityDmaintenanceEnables semantic search over local markdown documentation by indexing files and ranking results using vector similarity and BM25 fusion.18 npmApache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve content from local Markdown notes using term-frequency scoring.2ISC
- AlicenseNot gradedqualityCmaintenanceBuilds a keyword-searchable index from markdown documentation bundles and serves it to LLM agents via MCP, with retrieval logging and reporting for curation.MIT