Skip to main content
Glama
MaximilianMauroner

t3-code-mcp

by MaximilianMauroner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to t3-code-mcp

No user-submitted related servers found.

    Related Servers

    • herdr-voice-mcp

      lorenzkromer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables voice-driven control of coding agents via Claude on your phone, allowing status checks, stand-ups, sending prompts, and receiving push notifications when agents finish or need decisions.
      MIT

    • sofa-coder

      PennyBurden
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables hands-free voice collaboration with a coding agent: you speak requirements aloud and hear only short, plain-language progress and completion summaries while the agent edits code, runs tests, and fixes bugs in the background. It also handles continuous speech recognition with automatic turn detection, barge-in interruption, and spoken approval prompts before risky operations.
      1
      MIT

    • RepoMind Bridge

      idanidev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to receive and act on voice-captured tasks delivered as GitHub issues, including retrieving full context, adding notes, asking the developer questions, and closing tasks when complete.
      MIT

    • t3-mcp

      wynn-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any agent to spawn and manage T3 Code agent threads over HTTP MCP — starting research or coding agents, sending follow-ups, waiting for results, and answering approval prompts. It pairs once as a T3 device, exposes 15 tools, and keeps operations retry-safe.
      10 npm
      MIT
    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.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and the t3_run_* and t3_thread_* groups are largely well separated. The closest ambiguities are t3_run_interrupt vs t3_thread_interrupt and t3_thread_get vs t3_thread_messages, but the descriptions establish clear boundaries.

    Naming Consistency4/5

    All tools share the t3_ prefix and snake_case, with a mostly predictable resource_action pattern. Minor inconsistencies exist: plural forms like projects_list and pending_actions_list mix with singular forms, and connection_status and thread_messages are noun-like names rather than clear verb-first operations.

    Tool Count4/5

    At 15 tools, the surface is at the high end but still justifiable given projects, threads, runs, pending actions, and connection inspection each have separate workflows. A few operations could arguably be consolidated, but the set is not bloated enough to be a real usability problem.

    Completeness4/5

    The main workflow is covered end-to-end: project creation, thread creation and messaging, run waiting and interruption, and pending-action response are all present. Gaps remain around explicit project/thread updates or deletion, though thread archive and thread send act as partial lifecycle operations.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources