llm-wiki-mcp
Related Servers
Alternatives to llm-wiki-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceConnects RAG knowledge bases to Claude Desktop and Claude Code, allowing retrieval-augmented generation from ingested documents.-
- AlicenseNot gradedqualityDmaintenanceEnables querying enterprise documents (DOCX, PDF, PPTX) using natural language, with hybrid search and MCP integration for Claude Desktop and other agents.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to query a local Zendesk Help Center knowledge graph for semantic search, article retrieval, content gap analysis, and editorial intelligence tasks.3-
- AlicenseBqualityDmaintenanceConnects Claude to a Wiki.js instance, enabling page search, retrieval, listing, and creation.410 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to search and query personal document collections (PDF, Word, Markdown, text) using semantic search and conversational AI with full context preservation across exchanges.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Desktop to search custom knowledge bases using retrieval-augmented generation via a simple MCP tool.MIT
TDQS
Scored across 2 tools
The two tools, 'ingest' and 'query', have clearly distinct purposes: one adds documents to the wiki, the other retrieves information. There is no ambiguity or overlap in their functionality.
Both tool names follow a single-verb pattern that directly describes their action ('ingest' and 'query'), making them consistent and predictable.
With only two tools, the server feels under-scoped for a wiki knowledge base. While the tools cover core ingest and query actions, a more complete server would include additional management tools.
The server lacks essential operations such as listing wikis, deleting wikis, or updating ingested content. Users have no way to manage the wiki beyond ingesting and querying, which are significant gaps.