MELRA
Related Servers
Alternatives to MELRA
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to understand, run, test, diagnose, review, benchmark, and validate real local software projects through the Model Context Protocol. It provides workspace-confined safe execution, structured evidence instead of raw logs, and Git checkpoints with guarded rollback that never destroys user work.4 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents and MCP-compatible clients to enforce policy-approved actions using risk tiers, reversible checkpoints, and token approval bounds.7-
- AlicenseAqualityBmaintenanceOwner-signed authorization before agent actions. Hosted Vizier v0.5.13 MCP: https://vizier.agendamcp.dpdns.org/mcp. ALLOW/BLOCK/REVIEW; anonymous calls never ALLOW. Your integration enforces the decision. SDK v0.5.13: https://www.npmjs.com/package/@agenda-intelligence/vizier-sdk. Grants are signed; legacy receipts are unsigned. Python stdio is a separate catalog.36 npmMIT
- AlicenseCqualityCmaintenanceAn MCP execution layer that lets capable AI models safely control a developer workstation for file edits, terminal and process execution, Git operations, language-server analysis, browser and Windows UI automation, media processing, job/resource control, and checkpointing. It also coordinates durable single- or multi-agent tasks across providers with leases, dependency graphs, evidence logs, repair loops, and separate verification gates.1281ISC
- FlicenseNot gradedqualityBmaintenanceEnables deterministic task routing, contract enforcement, and effect authorization across domain owners while exposing a minimal MCP interface and read-only observability.-
TDQS
Scored across 11 tools
The set is organized into two parallel families (task-level and workflow-level) with clearly distinct plan/execute/status/cancel roles, so most tools are easy to tell apart. A few pairs invite confusion: melra_workflow_control (halt/resume, state preserved) vs melra_workflow_cancel (terminate), and melra_execute vs melra_workflow_advance (both perform execution at different granularities).
All names use snake_case with a consistent melra_ prefix, which is highly predictable. The deviation is structural rather than stylistic: task operations are unprefixed (melra_plan, melra_execute) while the analogous workflow operations are domain-prefixed (melra_workflow_plan, melra_workflow_advance), so the two parallel families don't mirror each other exactly.
Eleven tools is well within the sweet spot and each one maps to a real step in the governed task/workflow lifecycle (discover, plan, execute, status, cancel, control, receipt). No tool appears redundant or trivially included.
The surface covers task and workflow lifecycles well: plan, execute/advance, status, cancel, control, and receipts, plus capability discovery. Minor gaps exist, such as no enumeration/list operation for existing tasks or workflows and no workflow-level receipt retrieval, which an agent would have to work around via status projections.