Skip to main content
Glama
Nippori709

AgentDock

by Nippori709
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AgentDock

No user-submitted related servers found.

    Related Servers

    • web-gpt-agent-core

      dbc-hbin
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects ChatGPT Web to a local development environment, enabling file reads and patches, shell execution, plan updates, and isolated worktree coordination through permissioned MCP tools.
      3
      MIT

    • CodexPro

      sedatustunova
      A
      license
      A
      quality
      C
      maintenance
      Enables ChatGPT Developer Mode to operate as a local coding agent by connecting to your own repository through MCP, allowing it to read, write, search, edit files, run safe verification commands, and manage handoff context for continued work.
      15
      198 npm
      MIT

    • Coding Local

      Syx403
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT to inspect selected local projects, make edits, run commands/tests, and review diffs through an authenticated MCP endpoint backed by a containerized workspace.
      Apache 2.0

    • Capyra

      dxeledx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT and other MCP clients to browse, search, edit and upload files, run commands and interactive terminals, inspect Git history and worktrees, dispatch coding agents, and install composable plugins within locally registered workspaces. Requests execute under the user's own machine with per-request approval or auto-approval, keeping files, tasks and results local unless explicitly returned.
      1
      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 22 tools

    Disambiguation4/5

    Most tools target distinct operations—workspace management, file read/write/edit, image inspection, and change review—with descriptions that explicitly separate them. The main sources of ambiguity are the generic local-workspace-bridge wrapper, which can call other tools indirectly, and the write/edit/apply_patch cluster, though their intended use cases are clarified.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun snake_case pattern like open_workspace, read_image, and show_changes. The hyphenated local-workspace-bridge and the single-word bash/tree are noticeable outliers, but they are isolated deviations rather than a systematic mixing of conventions.

    Tool Count3/5

    22 tools is on the heavy side and exceeds the typical 3–15 tool sweet spot. The count is somewhat justified by the broad scope—workspace lifecycles, file editing, image handling, diagnostics, and verification—but it still feels like more surface area than necessary.

    Completeness4/5

    The toolset covers workspace open/list/close/default management, file tree/search/read/write/edit/apply_patch, image inspection and cropping, bash verification, change summarization, skills, and self-test/config. Obvious gaps like an explicit delete/rename tool or git commit are absent, but apply_patch can handle file deletion and the remaining gaps are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources