Skip to main content
Glama

Related Servers

Alternatives to Casama

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Bridges AI coding agents into Local and Remote-SSH/WSL/Dev Container VS Code windows, letting them read, edit, and search files, run commands and manage background tasks, and inspect live editor state, selections, and LSP diagnostics without installing anything on the remote host.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Codex conversations to delegate tasks to persistent worker subagents backed by models configured in VS Code, including BYOK endpoints. Provides workspace inspection and controlled editing tools, approval-gated shell commands, transcripts, and worker lifecycle management.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a running VSCode instance for real-time LSP data such as diagnostics, hover/definition/signature info, and symbol references instead of waiting on slow tsc or eslint runs. Also supports workspace-wide symbol renaming, opening files, listing workspaces, and executing VSCode commands.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Coolify self-hosted instances for application deployment, management, and monitoring. Features 4 unified tools optimized for VS Code's limits, covering app management, environment configuration, system administration, and built-in documentation.
      4
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets coding agents send questions, progress reports and approved PDFs into the user's own signed-in ChatGPT session through a local Chrome extension, then return the reply and its conversation URL. Keeps one ongoing conversation across devices and blocks duplicate or blind re-sends, all without an OpenAI API key.
      11
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The docs tools form a clear pipeline (list_doc_pages → search_docs → read_doc) and get_api_operation and check_plugin target clearly different resources (HTTP API spec and local plugin folders). The only mild overlap is that read_doc can also surface API reference pages, so an agent could occasionally reach for it when get_api_operation would give better structured output, but the descriptions mostly steer correctly.

    Naming Consistency5/5

    All five tools use a consistent verb_noun snake_case pattern: read_doc, list_doc_pages, search_docs, get_api_operation, check_plugin. Nouns are singular/plural consistently by convention (doc vs doc_pages, docs), and no mixed styles appear.

    Tool Count5/5

    Five tools is well within the ideal range and each one has a distinct role: discovery (list/search), retrieval (read), API lookup, and local validation. Nothing appears redundant or bolted on.

    Completeness4/5

    Docs discovery and retrieval are fully covered, and API reference plus plugin validation round out the surface nicely. Minor gaps exist — there's no way to enumerate all API operations or pull the full OpenAPI document, and check_plugin has no companion scaffolding/init tool — but agents can work around these via keyword queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues