Skip to main content
Glama

Related Servers

Alternatives to kt-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Provides an MCP client with confined read/write access to one approved workspace, including file and directory CRUD, search, git, shell commands, Python tooling, data conversion, web fetch, HTTP testing, system diagnostics, and a todo list, under a security model with workspace confinement, secret redaction, audit logging, and optional read-only or command restrictions.
      68
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.
      19
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables any MCP-compatible AI, whether in the browser or running locally, to create and edit projects, run terminal commands and long-running jobs, and optionally use Docker, all guarded by a policy engine, workspace jail, authentication, and audit logging.
      23
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A desktop launcher and local MCP workspace server that enables ChatGPT and other MCP clients to securely read, edit, search, run commands, and show changes in selected local project folders.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT, Claude, and other web MCP clients to access and operate multiple VS Code workspaces through tools such as read, bash, edit, write, and workspace_info, with per-workspace tokens and role-based permissions.
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: file reading/writing, searching, shell execution, and job lifecycle management. The only meaningful overlap is edit versus multi_edit, but the descriptions make the single-replacement versus ordered-batch distinction clear enough.

    Naming Consistency4/5

    Core tools use short, conventional names like read, write, edit, glob, grep, bash, and python, while background-job tools consistently use the job_ prefix (job_status, job_wait, job_cancel). The mix of bare verbs/nouns and prefixed names is slightly uneven but still predictable and readable.

    Tool Count5/5

    Twelve tools is well-scoped for a coding workspace MCP: file editing, search, execution, and job management each have a small, justified set of operations. No tool appears redundant or out of place.

    Completeness4/5

    The surface covers the core coding-agent lifecycle: read/write/edit/multi_edit for files, glob/grep/tree for discovery, bash/python for execution, and job_status/job_wait/job_cancel for background processes. Minor gaps like a dedicated delete or move/copy tool exist, but agents can work around them via bash.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues