A
licenseNot graded
qualityA
maintenanceEnables dispatching work to DeepSeek Harness agents from Claude Code/Codex, with native progress UI, tier policy, and vision/image generation through MCP tools.
128 npm
142
MIT
forge
by TT-Wang
Related Servers
Alternatives to forge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA flight recorder for Claude Code that captures tool calls and observations into a SQLite database, then classifies them into a distilled timeline for incident troubleshooting.MIT
- FlicenseNot gradedqualityDmaintenanceTransforms Claude from a code generator into a programming partner capable of testing, debugging, and optimizing code automatically through a secure execution environment.-
- FlicenseBqualityNot gradedmaintenanceBridges Claude Code to a Cloud Orchestrator API, providing access to multi-AI consensus, web search, code execution sandboxes, long-term memory, knowledge graphs, deployment management, and 20+ integrated AI and developer tools.28-
- AlicenseNot gradedqualityBmaintenanceMCP bridge for using local Claude CLI as a bounded reviewer and analysis delegate for Codex.MIT
- AlicenseNot gradedqualityFmaintenanceAn autonomous software-engineering pipeline for Claude Code that runs on real evidence: codebase intelligence tools, git analytics, deterministic verification rules, and zero LLM-judges-LLM. Every claim traces to a paper and every PR passes its own gates.1MIT
TDQS
A4.9/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a distinct, well-defined purpose with clear boundaries. For example, forge_logs is for event stream queries, iteration_state handles retry tracking, memory_recall/save manage learned patterns, session_state handles session persistence, and validate/validate_plan handle different validation scopes. The descriptions explicitly state what each tool should and should not be used for, preventing confusion.
Naming Consistency5/5
All tools follow a consistent snake_case naming convention with clear verb_noun patterns. Tools like forge_logs, iteration_state, memory_recall, memory_save, session_state, validate, and validate_plan maintain perfect consistency throughout the set, making them predictable and easy to understand.
Tool Count5/5
With 7 tools, this server is well-scoped for its forge orchestration domain. Each tool serves a specific, necessary function in the workflow (logging, state management, memory, validation), and none feel redundant or missing. The count supports comprehensive coverage without being overwhelming.
Completeness5/5
The tool set provides complete coverage for forge orchestration workflows. It includes logging (forge_logs), state management (iteration_state, session_state), knowledge persistence (memory_recall/save), and validation at both module and plan levels (validate, validate_plan). There are no obvious gaps—agents can manage the entire lifecycle from planning through execution to learning.
Maintenance
ActivityMaintained
ResponsivenessNo issues