Skip to main content
Glama
smcdonnell7

Meeting Chief Lite

by smcdonnell7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Meeting Chief Lite

No user-submitted related servers found.

    Related Servers

    • transcripts-mcp

      Stormix
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      12
      MIT

    • sync-hub

      Ekonum
      A
      license
      Not graded
      quality
      B
      maintenance
      Centralizes 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.
      2 npm
      MIT
    • LoreConvo by labyrinth-analytics

      LoreConvoofficial

      labyrinth-analytics
      A
      license
      A
      quality
      A
      maintenance
      Persistent memory layer for MCP-compatible AI agents. Implements save/recall/search over a local SQLite session store via 14 MCP tools. Auto-loads relevant context at session start. No cloud dependency. Works with Claude, Cursor, Codex, Hermes Agent. Free (50 sessions) / Pro ($8/mo).
      33
      62 PyPI
      10
      Business Source 1.1

    • ChatCrystal

      ZengLiangYi
      A
      license
      A
      quality
      A
      maintenance
      Local-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.
      7
      121 npm
      58
      Apache 2.0

    • cursor-history-mcp

      S2thend
      A
      license
      A
      quality
      A
      maintenance
      MCP server for browsing, searching, exporting, and backing up your Cursor AI chat history directly into Claude via natural language.
      8
      144 npm
      32
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources