Skip to main content
Glama
Sign In
mcp-cli

mcp-cli

by qodalis-solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-cli

No user-submitted related servers found.

    Related Servers

    • Claude Code MCP

      jawkjiang
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.
      7
      3 npm
      1
      MIT

    • Claude Code Bridge

      Cyruskraad
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.
      MIT

    • Claude Code MCP Server

      sohampatwardhan
      A
      license
      A
      quality
      B
      maintenance
      Lets AI agents create and drive Claude Code cloud sessions natively over stdio, exposing typed tools to start a session from a task description, queue follow-up messages into an existing session, and check the CLI's sign-in state. Each tool maps to a fixed Claude Code CLI invocation with strict schemas and structured JSON results, so agents never write shell commands or run local sessions.
      7
      542 npm
      MIT

    • Claude Code Manager WAN

      medelmouhajir
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables ISLI agents and MCP clients to dispatch natural-language coding and terminal tasks to a locally-installed Claude Code CLI, supporting both one-shot execution and persistent sessions with workspace and security controls.
      -

    • codex-app-server-mcp

      4714407
      A
      license
      A
      quality
      B
      maintenance
      Bridges MCP clients such as Claude Code and Cursor to independent Codex app-server sessions, letting them start, poll, steer, review, compact, cancel, and answer prompts for asynchronous Codex tasks over local stdio or a remote authenticated WebSocket. Runs read-only by default, with workspace-write sandboxing only when a user explicitly enables it, and reports job status, model listing, and progress back to the client.
      10
      20 npm
      1
      MIT

    • Claude Code Orchestration

      LevyBytes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an orchestrating assistant to drive Claude Code sessions running inside a Podman Linux VM by sending requests, reading status and events, checking acknowledgements, choosing model and effort, pulling native context reports, and opening or resuming the sidebar conversation. It routes control through a host CLI and MCP interface over Podman exec into a private relay inside the VM, keeping host access scoped and inside the owner-approved sandbox.
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct need: docs discovery (search), docs consumption (read), type/signature lookup (api), and project creation (scaffold). The search/read pair is explicitly linked in the descriptions ('read one in full with qcli_docs_read', 'Lists the topics when nothing matches'), so the boundary is unambiguous.

    Naming Consistency4/5

    All tools share a consistent qcli_ prefix and lowercase snake_case, which makes the family instantly recognizable. The component ordering varies (qcli_docs_search is noun_verb, qcli_scaffold_plugin is verb_noun) and qcli_api is a bare noun, a minor inconsistency but still readable.

    Tool Count4/5

    Four tools is a lean but justified surface for a docs-plus-scaffolding helper: one search, one read, one API reference, one generator, with no redundancy. It is on the thin side since there is no tool for exercising or validating what you build, but every tool earns its place.

    Completeness3/5

    Documentation retrieval (search + read) and API introspection are fully covered, but the lifecycle stops at creation: there is no tool to build, run, test, or inspect an existing plugin/project, and no way to list available recipes or installed plugins except indirectly through search. Agents will hit a dead end after scaffolding, having to fall back on shell commands.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources