unfour
Related Servers
Alternatives to unfour
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceSecure 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.228 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.2132MIT
- AlicenseNot gradedqualityAmaintenanceLocal-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.16 npmMIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1531 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives your AI assistant full awareness of your local dev environment — running processes, Docker containers, git state, open ports, log files, and more.7 npm1MIT
TDQS
Scored across 63 tools
Tools are grouped by resource prefix (workspace/api/db/ssh) and mostly target a distinct action and resource, with clear separation between read-only querying, execution, and explain paths. The main ambiguities are unfour.connection.list versus db/ssh.list_connections and ssh.run_diagnostic versus ssh.exec, but the descriptions provide enough guidance to avoid frequent misselection.
Most tools follow a consistent <domain>.<verb>_<noun> pattern, using predictable list/get/create/update/delete verbs. Minor deviations such as unfour.connection.list, unfour.workspace.current, and unfour.ssh.save_task instead of create_task/update_task slightly break the otherwise regular convention.
At 63 tools, this is a very large MCP surface, well above the 25+ threshold even though the domain spans workspace, API, database, and SSH concerns. The namespaces are logical, but many operations could be consolidated, especially environment variable CRUD, task-run lifecycle handlers, and repeated *_connection tools.
The tool set provides strong full-lifecycle coverage for workspace variables, API requests/collections/environments, database connections/query paths, and SSH connections/tasks/files, plus activity and health diagnostics. Notable minor gaps include no explicit API folder operations (folders only appear during cascading collection deletion) and no per-entry DB history detail, but these are workable gaps rather than dead ends.