feishu-kb-mcp
Related Servers
Alternatives to feishu-kb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable agents to author, query, and maintain a self-hosted wiki through typed tools backed by SQLite, including full-text search, revisions, links, tags, media, and correction work queues. It supports configurable read, author, and admin tool surfaces for creating, updating, deleting, reviving, and section-editing pages.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP-capable agent to write and maintain its own wiki of small linked markdown pages with a typed ontology, storing, indexing and retrieving them through keyword (BM25) search plus ontology-graph traversal, typed-relation management, page reads and writes, linting and listing. It also offers an optional vision tool that extracts objects and text from images so text-only models can learn from screenshots, charts and scans.MIT
- FlicenseNot gradedqualityDmaintenanceProvides structured search, schema-validated writes, and linting for a markdown knowledge base, enabling agents to operate the wiki over a single streamable-HTTP MCP endpoint.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, read, update, delete, search, and explore linked Markdown pages in a self-hosted knowledge base through MCP tools.14 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.27 npm1MIT
- AlicenseNot gradedqualityBmaintenanceA machine-local, agent-writable knowledge base MCP server that lets coding agents autonomously record and retrieve hard-won operational facts, incidents, and corrections as markdown pages in a git repo, with provenance, talk pages, and search.4 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource+action: search vs read vs outline for retrieval, create/append/replace_text/rename/move for different write operations, plus status, sync, audit, and a guarded delete proposal. The descriptions make the boundaries between the write tools (append at end vs literal text replacement) explicit, so an agent can reliably choose.
All tools share a consistent kb_ prefix and snake_case, mostly following a verb_noun pattern (kb_search, kb_read, kb_create, kb_move, kb_propose_delete). Two tools are noun-style (kb_status, kb_outline), a minor deviation from the verb convention but still readable and predictable.
12 tools is well within the ideal 3-15 range and each maps to a clear responsibility: discovery, reading, authoring, restructuring, maintenance, and safe deletion. Nothing appears redundant or bloated for a knowledge-base server.
The surface covers the full lifecycle: search/read/outline for retrieval, create/append/replace/rename/move for updates, guarded delete via proposal, plus sync and audit for maintenance. Minor gaps exist, such as no explicit version-history or batch-read operation, but core workflows are fully supported.