Skip to main content
Glama
lubarinobr

domain-glossary-mcp

by lubarinobr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to domain-glossary-mcp

No user-submitted related servers found.

    Related Servers

    • Obsidian Dictionary MCP Server

      SaraHan774
      F
      license
      A
      quality
      D
      maintenance
      Enables the management of a technical terminology glossary within an Obsidian vault by providing tools to add, search, and retrieve term definitions. It supports structured Markdown entries featuring both developer-focused and simplified explanations for efficient knowledge management.
      4
      3
      -

    • learning-loop-mcp

      tiempor3al
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to index, search, and validate lessons learned across project repositories via a local SQLite index, providing learning-loop resources and verified-solution tracking without loading full files into conversations.
      11
      MIT

    • cardloom-mcp

      bangca85
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides long-lived, cross-project technical memory for AI agents via markdown cards stored in git and indexed by SQLite, enabling search, retrieval, and human-reviewed knowledge management.
      ISC
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: looking up a definition, saving or replacing one, and listing missing definitions. There is no meaningful overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_noun pattern: lookup_term, save_term, list_missing_terms. The naming style is uniform and predictable.

    Tool Count5/5

    Three tools is well-scoped for a domain glossary server. Each tool covers a necessary core action without redundancy or unnecessary surface area.

    Completeness4/5

    The glossary lifecycle is largely covered with lookup, save/replace, and gap identification. A delete_term tool and a way to list all defined terms would make it fully complete, but these are minor gaps that do not block the primary workflow.

    Resources