NAVIG
OfficialRelated Servers
Alternatives to NAVIG
- AlicenseBqualityFmaintenanceA powerful Model Context Protocol (MCP) server for Docker operations, enabling seamless container and compose stack management through Claude AI.4505MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides tools for interacting with Supabase databases, storage, and edge functions.45MIT
- FlicenseBqualityFmaintenanceDEPRECATED — succeeded by SSH-Connect (Rust rewrite): https://github.com/mixelpixx/SSH-Connect1150-
Related Servers
- AlicenseNot gradedqualityAmaintenanceTurns web-based AI chat clients such as Claude, ChatGPT, Grok, and Postman into secure operators of a local machine by exposing 38 OAuth-gated tools over one MCP endpoint for files, shell, search, Git, SQLite, browser automation, DevTools, background tasks, localhost services, clipboard, notifications, ports, and Postman control. It keeps execution local-first and safe by default through a strict shell command whitelist and configurable folder access.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.MIT
- AlicenseNot gradedqualityAmaintenanceTurns web-based AI clients such as Claude, ChatGPT, and Grok into secure operators of a local machine by exposing an OAuth-gated MCP endpoint with 38 governed tools for file editing, whitelisted shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost fetches, ports, clipboard, notifications, and Postman control. Read-only and destructive operations are annotated, optional app providers can be toggled, and access is confined to permitted folders for safe, local-first desktop automation from the browser.MIT
- FlicenseNot gradedqualityAmaintenanceEnables web-based AI chat clients to securely operate a local machine through one OAuth-gated MCP endpoint, exposing governed tools for file read/write/edit, whitelisted shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost fetches, clipboard, notifications, ports, and Postman. It lets users build and edit projects, inspect databases and local APIs, drive browser workflows, and manage long-running jobs from a browser or mobile device without granting unrestricted shell access.-
- FlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 tools over a single OAuth-gated MCP endpoint, letting web-based AI clients such as Claude, ChatGPT, and Grok read and edit files, run whitelisted shell commands, search, query SQLite, use Git, automate browsers and DevTools, manage background tasks, reach localhost services, and control the clipboard, notifications, ports, and Postman. This turns remote AI chats into secure operators of a local machine without granting unrestricted shell access.-
- FlicenseNot gradedqualityAmaintenanceLocal MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.49-
TDQS
Scored across 15 tools
Each tool targets a distinct domain+action, and descriptions explicitly cross-reference neighbors to prevent confusion (e.g. navig_memory vs navig_recall vs navig_knowledge, navig_browser_debug vs navig_browser_user vs navig_web). The read/act pairing (debug vs debug_act, connectors vs connectors_act, runtime vs runtime_action) is clearly delineated. Boundaries are stated rather than left implicit.
Reads follow a uniform navig_<domain> pattern (navig_fleet, navig_knowledge, navig_recall, navig_web). Writes deviate slightly in verb suffix: navig_connectors_act and navig_browser_debug_act use '_act', navig_runtime_action uses '_action', while navig_memory_update and navig_automation_apply use other verbs. Mostly consistent with minor deviations.
15 tools sit at the top of the well-scoped range, and each earns its place: nine distinct read domains plus their corresponding state-changing counterparts. The read/act split is principled rather than redundant. No filler tools.
Strong lifecycle coverage: memory (read/update), runtime (read/action), automation (browse/apply), connectors (read/act), browser (inspect/act). Minor gaps remain—knowledge, recall, fleet and web are read-only with no write path, and memory lacks an explicit hard-delete. These are largely by design and workable.