A
licenseNot graded
qualityD
maintenanceLocal-first memory, pipelines, learning, feedback, and safe code tools for AI coding agents.
MIT
universal-brute-workpack
Related Servers
Alternatives to universal-brute-workpack
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEquips AI coding agents with filesystem, Git, database, and computation tools via the Model Context Protocol.1-
- FlicenseAqualityDmaintenanceActs as the 'Hands and Eyes' for an Autonomous AI Agent, bridging Large Language Models and your local development environment to enable safe file manipulation, context reading, command execution, and documentation verification.92-
- AlicenseBqualityCmaintenanceProvides coding agent capabilities including file operations, terminal commands, search functionality, and utility operations.2712 npm5MIT
- AlicenseCqualityCmaintenanceWraps the cursor-agent CLI to provide cost-effective tools for repository analysis, code search, planning, and editing. Offloads heavy thinking tasks from the host AI to reduce token usage while maintaining precise, scoped workspace operations.75 npmMIT
- AlicenseNot gradedqualityBmaintenanceTurns a one-person, multi-project workspace into state an agent can reason over, exposing live git status, Kanban boards, tasks, standups, and production health as queryable tools via MCP.MIT
TDQS
C2.8/5.0
Scored across 26 tools
Disambiguation4/5
Tool boundaries are mostly clear thanks to domain prefixes and distinct actions such as search.web vs search.fetch and fs.glob vs fs.grep. The main weaknesses are memory.recall, which is an explicit alias of memory.search, and worker.analyze vs worker.diff, which both operate on files in parallel and could be confused.
Naming Consistency5/5
All tools follow the same namespace.verb lower_snake_case pattern, e.g. search.web, fs.glob, file.read, audit.ingest_report, and agent.spawn. There is no mixing of camelCase, inconsistent verb styles, or unpredictable naming conventions.
Tool Count3/5
At 26 tools, this is on the heavy side and just above the 16-25 range that feels bloated for typical MCP servers. However, the universal workpack purpose spans search, filesystem, code, validation, memory, workers, audit, and agents, so most tools serve a distinct function and the count is borderline rather than extreme.
Completeness3/5
The toolkit covers a wide range of operations and the audit/worker pipeline is fairly complete, but there are notable lifecycle gaps for a universal workpack: no file delete, no directory create/stat, no memory write, and no way to terminate spawned agents. Some of these can be worked around with command.exec, but they are missing as first-class tools.
Maintenance
ActivityMaintained
ResponsivenessSyncing