step-engineer
Related Servers
Alternatives to step-engineer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Google Gemini to autonomously read, write, search, and patch code files and run whitelisted developer commands inside a sandboxed local workspace for edit-and-verify coding workflows.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect, edit, and test code within a bounded repository environment to solve software engineering tasks and verify fixes.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to run bounded local profiling, tracing, and benchmarking analyses on explicit artifacts or commands, returning typed evidence with provenance, coverage, and limitations.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to perform batched, token-efficient file and search operations with tolerant, automatically verified edits and diffs. It supports sandboxed workspace access, optional command execution, caching, and post-edit syntax/import checks.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to inspect real project sources, compile client-authored design specifications and design tokens, apply safe hash-preconditioned source edits, and verify running pages using Playwright screenshots, axe-core accessibility checks, PNG diffs, and browser timing data. Creative direction stays with the AI client while the server supplies explicit contracts, controlled operations, and measurable evidence rather than generic text responses.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a cloud coding agent to delegate a focused coding task to a local Ollama or OpenAI-compatible model through a bounded workspace, file allowlist, and required external checks. Changes are applied only after verification against the declared scope, with failed post-apply checks rolled back and the rollback itself confirmed.66 PyPI11MIT
TDQS
Scored across 4 tools
Each tool maps to a distinct phase of the optimization job lifecycle: submit starts, get_status polls, get_result retrieves final output, cancel aborts. No two tools share the same action or resource, so an agent can easily choose the right one.
All four tools use snake_case with a consistent verb_noun pattern (submit_optimization, get_optimization_status, get_optimization_result, cancel_optimization). The structure is predictable and unambiguous.
Four tools cover the essential async job lifecycle without redundancy. This is a well-scoped set for a focused optimization service.
The surface covers the full lifecycle: create, poll status, fetch results, and cancel. No obvious operation is missing for managing an optimization job, and the run_id-centric design avoids dead ends.