Library MCP
Related Servers
Alternatives to Library MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA local MCP server that allows AI systems to search and retrieve information from a custom knowledge base generated from markdown files. It provides tools for natural language text search, category browsing, and specific content chunk retrieval.3-
- FlicenseNot gradedqualityCmaintenanceMCP server that enables full-text search and link navigation over Markdown files as a knowledge graph.-
- FlicenseNot gradedqualityCmaintenanceA CLI tool and MCP server that turns markdown documentation into a searchable, queryable knowledge base.29 npm-
- FlicenseCqualityCmaintenanceMCP server to query and modify an Obsidian vault or any folder of markdown files. It provides search, tag filtering, backlinks, and CRUD operations on notes, with path traversal protection.11-
- AlicenseAqualityDmaintenanceAn MCP server for managing Obsidian-style note vaults, providing tools for full-text search, note creation, and backlink tracking. It enables users to navigate, structure, and update their personal knowledge base through natural language.9MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for reading and searching Markdown notes in any directory, such as an Obsidian vault. It integrates with MCP clients like Claude Desktop to access note contents.803 npm-
TDQS
Scored across 7 tools
Most tools have distinct purposes focused on different retrieval methods (by date, slug/URL, tag, text content) and tag operations, but 'get_by_slug_or_url' and 'get_by_text' could potentially overlap if users confuse slug/URL with text content queries. The descriptions help clarify, but there's minor ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., get_by_date_range, list_all_tags, search_tags). The naming is predictable and readable throughout the set, with no deviations in style.
With 7 tools, this is well-scoped for a library/blog content server. It covers core retrieval operations and tag management without being overwhelming, and each tool serves a clear purpose in the domain.
The toolset provides good read/search coverage for blog content and tags, but lacks any create, update, or delete operations, which are notable gaps for a full CRUD lifecycle. Agents can retrieve and rebuild but not modify content, limiting workflow completeness.