conductor
Related Servers
Alternatives to conductor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Claude Text Lab, enabling fact-preserving regeneration of Claude-generated text through inspect, sanitize, audit, rewrite, and benchmark operations, with auditable local quality gates and an unverified provenance verdict.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that turns coding workflows into explicit execution graphs (DAG) with deterministic command execution, human-in-the-loop gates, and tamper-proof run history for Claude Code.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enhances Claude Code with evidence-first engineering, protocol gates, project-aware verification, auditable traces, and durable autonomous execution.15 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for safely continuing long Claude Code sessions by cleaning transcripts, removing runtime noise, and generating verified resumable sessions with rollback support.1MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that connects Claude Code to your work environment through auditable tools for file operations, API calls, and command execution, with safety gates and configuration.-
- AlicenseAqualityDmaintenanceA safe, local MCP server that lets Claude drive a controlled software-development loop (inspect, read, plan, patch, apply, check, analyze, fix, summarize) on a project, using deterministic tools and real diffs/test runs.101MIT
TDQS
Scored across 23 tools
Most tools have clearly distinct purposes, but a few boundaries are slightly fuzzy: extract_contact overlaps with extract_emails/redact_pii, slugify overlaps with to_snake_case, and classify_sentiment overlaps with categorize. The descriptions generally clarify the distinctions, so misselection risk is low but not zero.
All names use consistent snake_case, which is a strong baseline. However, the convention mixes verb_noun (extract_emails, normalize_phone), noun_verb (word_count, json_extract, base64_encode), and bare verbs (summarize, truncate, translate), which is a minor inconsistency.
At 23 tools, the set is heavy for a text-processing utility server and sits at the upper edge of the appropriate range. Each tool is small and focused, but the overall surface feels broad rather than tightly scoped.
The server covers a wide range of text operations: normalization, extraction, transformation, classification, translation, encoding, and JSON repair/minification. Some generic utilities like regex replace, case conversion beyond snake_case, or HTML stripping are missing, but the core workflows are well supported.