Skip to main content
Glama

Conducted MCP

Server Details

Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Mostov82/conducted-mcp
GitHub Stars
1
Server Listing
Conducted MCP
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool addresses a distinct aspect of the methodology: decision logging, gate evaluation, kickoff planning and questions, procedure retrieval, standup scheduling, and artifact validation. No two tools have overlapping purposes.

Naming Consistency3/5

All names use snake_case but mix verb_noun (evaluate_gate, validate_artifact) with noun_phrase patterns (kickoff_plan, next_procedure, standup_due). The pattern is not fully consistent, though each name is still readable.

Tool Count5/5

With 7 tools, the server covers the key lifecycle points of the Conducted Development methodology without being too sparse or bloated. Each tool serves a clear purpose within this scope.

Completeness4/5

The tools cover decision logging, gate checks, kickoff, procedure guidance, standup triggers, and validation. Missing an explicit tool for session execution, but next_procedure provides steps, mitigating the gap.

Available Tools

7 tools
decision_log_guidanceJudge whether a situation belongs in the Decision LogAInspect

Encode the Decision-Log 'when to use it' rules. Set whichever apply: escalation_fired, gate_resolved_cross_cutting, affects_multiple_tickets, override_architectural, confined_to_one_session. Returns { should_log, reason, entry_template? }; when should_log is true the Context/Trigger/Decision/Rationale/Affects skeleton is returned. A decision confined to one session does not need an entry — the session notes suffice.

Inputs: escalation_fired, override_architectural, confined_to_one_session, affects_multiple_tickets, +1 more.

evaluate_gateEvaluate whether a goal brief's gates are resolvedAInspect

Encode the goal-brief rule that no session may begin while any gate is open. Supply either a structured gates list ([{ id, resolved }]) or a goal-brief content string, in which case the GATE LIST checkboxes (- [ ] / - [x]) are parsed. Returns { all_resolved, unresolved, may_begin } where may_begin === all_resolved. The server reads no files — the content is agent-supplied.

Inputs: gates, content.

kickoff_planAssemble the kickoff file planAInspect

Assemble, from the bundled templates, the four _template.md copies (front-matter tokens replaced), decision-log.md, and a filled AGENT_CONVENTIONS.md (kickoff guide Steps 2–5). Supply project_type, the interview answers, optional detected (brownfield pre-fill fallback), and optional existing (the agent's inventory of files already present). Returns { files: [{ path, content, action }], missing, open_questions, warnings }. The plan is ready iff missing is empty (D5 strict); a file with any unresolved {{…}} token is reported in missing. Idempotent: already-present files are 'review'/'skip', never overwritten. The server returns content + paths only — it writes nothing (Model C, D2/D6).

Inputs: answers (required), project_type (required), detected, existing.

kickoff_questionsGet the kickoff interview question setAInspect

Return the branched kickoff interview (DECISIONS.md D3/D4). Supply project_type: 'greenfield' asks the full set; 'brownfield' uses the agent-supplied detected facts (language, framework, tests, CI, existing docs) to pre-fill candidates and drop fully-inferable questions — except LOCKED_DOCS, which is always asked because it is human judgment. Returns { project_type, questions, inferred, notes }; the server reads no files.

Inputs: project_type (required), detected.

next_procedureGet the procedure for a methodology phaseAInspect

Return the ordered procedure for where the agent is in the methodology loop. Supply phase (one of: kickoff, goal_brief, intent_doc, session_open, session_active, session_close, standup) and optional facts (e.g. a ticket id) to tailor the output. Returns { steps, reads_first, escalation_points, notes? } sourced from the bundled guides and conventions — the procedure half of advisor + validator. The server reads no files.

Inputs: phase (required), facts.

standup_dueJudge whether a standup is dueAInspect

Given agent-supplied facts, decide whether a standup is due. Triggers in priority order: a deliverable gate reached → 'gate'; else a dependency intersection → 'intersection'; else more than five working days since the last standup → 'weekly'; else 'none'. Working days are an input (the working week varies by team), never computed from a calendar. Returns { due, reason, detail }.

Inputs: today, gate_reached, last_standup_date, dependency_intersection, +1 more.

validate_artifactValidate a methodology artifactAInspect

Strictly check whether a Conducted Development artifact's text satisfies the methodology's required structure. Supply the artifact's type and its full text (the server never reads files). Returns { valid, missing, warnings }: missing lists required sections that are absent, empty, or contain only unmodified template placeholder text (blocking); warnings lists sections that are present but look thin (advisory, non-blocking). valid is true iff missing is empty.

Inputs: content (required), artifact_type (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.