Skip to main content
Glama
ssubbotin

longwire

by ssubbotin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to longwire

No user-submitted related servers found.

    Related Servers

    • grok-mcp

      TuTouPower
      A
      license
      A
      quality
      C
      maintenance
      Exposes local Grok Build bridge as MCP stdio server, enabling code agents like Claude Code to run Grok models, check status, and manage runs.
      6
      40 npm
      MIT

    • 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
      1
      MIT

    • grok-delegate

      zai-one
      A
      license
      B
      quality
      A
      maintenance
      Local stdio MCP bridge that delegates coding work to the Grok CLI agent via isolated git worktrees and typed receipts. Provides MCP tools for interacting with the Grok CLI across stdio, WebSocket, and legacy transports.
      23
      2
      MIT

    • MCP SSE Proxy

      gomarble-ai
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Bridges STDIO-based MCP clients with SSE-based MCP servers, allowing applications like Claude Desktop to connect to remote MCP servers that use SSE transport.
      9
      -
    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.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: create or load a session, send a prompt, cancel an in-flight prompt, or check connection status. There is no meaningful overlap between any two tools.

    Naming Consistency4/5

    All tools share the consistent grok_ prefix and use snake_case, which makes them recognizable as a family. Minor inconsistency exists because some names use verb-object order (session_create, session_load) while others are single verbs or nouns (prompt, cancel, status).

    Tool Count5/5

    Five tools is well-scoped for a focused Grok Build ACP client. Each tool covers a necessary part of the session lifecycle and interaction flow without redundancy or bloat.

    Completeness4/5

    The tool surface covers the core workflow: session creation/loading, prompting, cancellation, and status checks. A session deletion/close tool is a minor missing piece, but agents can still complete practical workflows without it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources