Skip to main content
Glama
parseltongue-claude

parseltongue-claude

by nlebovits

Related Servers

Alternatives to parseltongue-claude

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling Claude to consult Codex (GPT-5.x) mid-task for second opinions, plan/diff review, brainstorming, and codebase exploration via structured debates and permission-controlled interactions.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server gives Claude Code persistent cross-session memory with semantic search, automatic detection and tracking of user corrections as behavioral patterns, and reflective framework evolution that improves judgment over time. Everything runs locally through Claude Code's hooks and extension points, with no cloud, accounts, or API keys required.
      6 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are largely distinct by function: create/register/load/check/query/get/clear each target a different aspect of the session lifecycle. The only mild overlap is parseltongue_check_consistency vs parseltongue_load_dsl (both return verification/consistency info) and get_state vs query, but descriptions make the boundaries reasonably clear.

    Naming Consistency4/5

    All tools follow the consistent parseltongue_verb_noun pattern (create_session, register_document, load_dsl, check_consistency, get_state, query, list_sessions, clear_session, dsl_reference). Minor deviation is the verb-less 'query' and 'dsl_reference', but these are readable and predictable overall.

    Tool Count4/5

    Nine tools is a reasonable count for a session-management plus DSL-engine server. Each tool serves a clear purpose without feeling bulky; slightly on the higher end for a content-verification tool but well within acceptable range.

    Completeness4/5

    The surface covers the full session lifecycle: create, register documents, load DSL, check, query, get state, list, and clear. Minor gaps exist (no delete_session/destroy session, no update/append operations), but the core verification workflow is well covered.