unfour
Related Servers
Alternatives to unfour
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceSecure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.-
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that enables AI-assisted coding through workspace-scoped tools for file reading/editing, command execution, jobs, Git, LSP, media, browser, and desktop workflows. It enforces OAuth, workspace ACL, trust policies, and file/secret guards so owners can safely grant inspect, edit, or trusted capabilities.32 npmMIT
- AlicenseCqualityBmaintenanceLocal-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.133MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.33 npmMIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1541 npm3MIT
- 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
TDQS
Scored across 72 tools
The domain.action naming and detailed descriptions generally make each tool's purpose distinct, and cross-references such as run_diagnostic vs exec help. However, with 72 tools there are minor overlaps, e.g. generic connection.list vs ssh.list_connections/db.list_connections, and multiple history/list surfaces that could be confused.
All tools follow a consistent snake_case namespaced pattern: unfour.<domain>.<action>. Verbs are used predictably (list, get, create, update, delete, run, etc.), with only expected noun-style exceptions like current and health.
72 tools is far beyond a practical, well-scoped set for an agent. Even across several domains, this volume is excessive and many fine-grained CRUD/list operations could be consolidated or exposed through resource parameters.
Coverage is broad across workspaces, API requests/environments, SSH connections/tasks/files, database connections/tables/query/export, Flow runs, activity, and health. Minor gaps exist, such as no workspace create/delete tools and no explicit API folder CRUD, but core workflows are covered.