MCP Agent Operations
Related Servers
Alternatives to MCP Agent Operations
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables LLM agents to perform local development and automation over MCP STDIO, including project context retrieval, file read/write and patching, shell/Python execution, Git inspection, work-state tracking, and validation. It runs as a local Python process with Dev and Safe execution modes and audit logging for trusted single-developer environments.16Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to control a local computer over stdio with filesystem operations, ripgrep search, shell command execution, and persistent process sessions.14MIT
- 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.14 npmMIT
- FlicenseAqualityDmaintenanceLightweight MCP server that exposes tools for system information and weather lookup, designed for agent integration via stdio.1-
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1533 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.2,507 npmMIT
TDQS
Scored across 25 tools
Each tool has a clearly distinct purpose, especially within the claims cluster where verbs like acquire, extend, release, and status differentiate them. No two tools seem to perform the same action, though the many claim-related tools could require careful reading.
The naming convention is consistent within each domain (claim_*, skill_*, render_hierarchy_*, verify_*) but mixes noun_verb (claim_acquire) and verb_noun (create_hierarchy_plan) patterns across the server. This inconsistency could make tool naming less predictable.
With 25 tools, the count is at the high end and feels heavy for an MCP server. The multiple domains justify some breadth, but the set could likely be consolidated without losing clarity.
Claims have strong lifecycle coverage, but other areas have gaps: hierarchy plans have no delete operation, skills only support read/load/validate without creation or removal, and references only load/refresh. Some obvious operations are missing, making the surface incomplete.