kb-mcp-server
Related Servers
Alternatives to kb-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes one SQLite-backed notes store over both stdio and an HTTPS/SSE endpoint, letting Claude Code, Claude Desktop, Claude web, and Claude mobile read and write the same shared state with full-text search. Provides write, read, search, and list tools so a note created on one surface is immediately visible from any other.15 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables to create notebooks and notes with tags, and perform full-text search across notes using FTS5 syntax, all stored locally in SQLite.-
- FlicenseBqualityDmaintenanceEnables indexing and retrieving notes with full-text search using SQLite, plus building knowledge graphs to find relationships between concepts. Supports natural language note management, tagging, and semantic connections.16-
- FlicenseBqualityBmaintenanceEnables a personal graph-based memory system with CLI, HTTP API, and MCP interfaces for storing nodes, relationships, documents, and attachments. It provides local, scriptable alternatives to Obsidian/Engram with SQLite FTS5 search and integration with other tools via MCP.21-
- AlicenseNot gradedqualityBmaintenanceProvides a local-first, long-term memory service that lets AI agents and humans save, search, and retrieve Markdown notes across sessions with full-text BM25 retrieval and source-attributed evidence snippets.2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Obsidian vaults for creating, reading, searching, and managing notes, daily notes, TODOs, session reports, and backlinks through both stdio and HTTP/SSE transports.103,458 npm4MIT
TDQS
Scored across 5 tools
Each tool targets a distinct action on a single note resource: create, retrieve, update, delete, and search. There is no overlap or ambiguity; an agent can easily select the correct tool.
All tool names follow a consistent verb_noun pattern in snake_case: create_note, get_note, update_note, delete_note, search_notes. The convention is predictable and readable.
With 5 tools, the set is well-scoped for a note management server. It covers essential operations without bloat, and each tool earns its place.
The server provides full CRUD plus full-text search, covering the core lifecycle. However, it lacks an explicit 'list all notes' operation, which could be a minor gap for some workflows.