Meeting Chief Lite
Related Servers
Alternatives to Meeting Chief Lite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables searching and reading local Cursor, Claude Code, and Codex session transcripts from any MCP client, with fuzzy, regex, and full-text search, plus optional semantic search.14MIT
- AlicenseNot gradedqualityBmaintenanceCentralizes verbatim local AI conversation history into a SQLite database and exposes it via an MCP server, enabling tools like Claude Code and Codex to retrieve exact context from other tools.1 npmMIT
- AlicenseAqualityBmaintenanceLocal memory of your coding-agent sessions. Imports Claude Code, Codex, opencode and Copilot transcripts, extracts decisions and learnings with a link back to the session turn, and lets agents search them over MCP.91MIT

LoreConvoofficial
AlicenseAqualityAmaintenancePersistent memory for AI agents across Claude Code, Cowork, Codex, Cursor and Hermes Agent. Saves, searches and recalls sessions from a local SQLite store through 40+ MCP tools, with auto-save and auto-load hooks, project tagging and export/import. Also a Hermes Agent memory provider plugin in the official catalog. Free: keyword search, 50 sessions. Pro ($8/mo): semantic search and team memory.33349 PyPI12Business Source 1.1- AlicenseAqualityAmaintenanceLocal-first AI PKM memory server for coding conversations. Imports Claude Code, Cursor, Codex CLI, Trae, and GitHub Copilot chats into notes, semantic search, tag graphs, Markdown exports, and MCP memory tools.7121 npm61Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cursor, Zed, and Windsurf to recall associative context from a folder of markdown notes, combining vector search entry points with one-hop [[wikilink]] graph expansion and cross-encoder reranking over a single SQLite file. It also appends a zero-token per-turn ledger of asks, files, tools, and decisions that agents can consult across sessions.242 PyPI12MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: 'meetings' handles browsing and retrieving transcripts, 'search' focuses on finding content within transcripts, and 'status' manages system health and operations. The descriptions clearly differentiate these domains, eliminating any ambiguity for agent selection.
All tool names follow a consistent, simple noun-based pattern ('meetings', 'search', 'status') that is readable and predictable. There are no deviations in style or convention, making the set easy to navigate and understand.
With 3 tools, the count is slightly low but reasonable for a 'lite' server focused on meeting transcripts. It covers core operations (browse, search, status), though it might benefit from additional tools for actions like updating or deleting data, but it's well-scoped for its apparent purpose.
The tool set provides good coverage for browsing, searching, and managing meeting transcripts, with no obvious dead ends. Minor gaps exist, such as lack of explicit update or delete operations for transcripts, but agents can likely work around this given the server's focus on retrieval and search.