Skip to main content
Glama

Related Servers

Alternatives to k-exaone-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents such as ChatGPT, Claude, and local LLMs to operate an enterprise digital-operations platform through MCP, exposing 19 model tools and 3 app-only tools for identity, data, workflow, files, and PII-controlled operations with role-based permissions and two-phase confirmations.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables delegating tasks to agents you configure yourself through OpenAI-compatible Chat Completions backends, with automatic or explicit routing, synchronous calls, persistent asynchronous jobs, and multi-step reviewed workflows. It returns proposals and analyses only, leaving file changes, command execution, and approvals under the MCP client's control.
      28 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code to delegate bounded tasks like code review, boilerplate generation, commit messages, format conversion, and embeddings to local or cloud OpenAI-compatible LLMs, reducing token costs while keeping the main model in control.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP chat clients to read explicitly shared local source files and search results without spending local model quota, while also providing an experimental quota-relay workflow for extended modes.
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools occupy completely separate roles: ask_exaone performs model delegation/inference, while exaone_status reports configuration, token usage, and API health. An agent cannot plausibly confuse a query tool with a diagnostics tool, and the descriptions reinforce the boundary.

    Naming Consistency4/5

    Both names are snake_case and share the `exaone` token, giving a recognisable family. However, ask_exaone is verb-first while exaone_status is prefix-first, a minor structural deviation rather than a real inconsistency.

    Tool Count4/5

    Two tools is thin in absolute terms, but the server's scope is deliberately narrow (single-model delegation plus health check), and both tools earn their place. Nothing is missing that would warrant an extra tool purely for count's sake.

    Completeness4/5

    The core lifecycle is covered: stateless asks, file-passing, multi-turn follow-ups via conversation_id, and a status/connectivity check. Gaps are minor — there is no way to list, inspect, or delete existing conversation threads, and no parameter/model discovery beyond status.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues