Server data from the Official MCP Registry
Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.
Stateless advisor + validator for Conducted Development: kickoff, artifact validation, rule checks.
Remote endpoints: streamable-http: https://conducted-mcp.jonathanmostov.workers.dev/mcp
Conducted MCP is a well-structured, stateless advisory server with no authentication requirements (appropriate for its role), secure code practices, and permissions appropriately scoped to its purpose. The server is read-only, holds no data, and poses minimal security risk. Minor code quality observations do not materially affect the security posture. Supply chain analysis found 2 known vulnerabilities in dependencies (1 critical, 0 high severity). Package verification found 1 issue.
3 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
An MCP server that helps an AI agent plan and track a software project the way a disciplined team would — and it was built using the very methodology it ships.
Conducted MCP exposes Conducted Development — a lightweight, intent-driven methodology — to any MCP-capable agent (Claude Desktop, Cursor, and others). It is a stateless advisor + validator: it holds no project data and touches no files or git. The agent does all the I/O; the server supplies judgment — validate this artifact, is a standup due, what's the procedure for this phase, does this decision belong in the log.
The differentiator: this repository's own
work/folder — goal briefs, intent docs, a decision log, and cycle standups — was produced under the methodology the tool implements. It is the proof of process, not a sample.
A connecting agent gets, on demand:
kickoff prompt + kickoff_questions / kickoff_plan tools) — a branching Q&A that bootstraps a project's planning structure for greenfield or existing codebases. For existing code the agent inspects the repo and the server pre-fills answers so the human confirms rather than authors from scratch.validate_artifact) — submit a goal brief / intent doc / session log / standup, get back { valid, missing, warnings }.next_procedure) — the ordered steps, what to read first, and the escalation points for wherever the agent is in the loop.standup_due, evaluate_gate, decision_log_guidance) — the rituals a solo practitioner most often lets slide, as stateless judgments over supplied facts.The methodology's guides, templates, and conventions are served as read-only resources (conducted://guide/*, conducted://template/*, conducted://conventions) so an agent can learn the rules in-band.
The server cannot enforce — an agent always has direct file access. So instead of pretending to be a gatekeeper, it is an advisor: pure functions returning judgments and procedures, no side effects, nothing to host with no data and no auth-to-data. That makes it portable, trivially testable, and cheap to run locally or remotely. The reasoning is written up in docs/DESIGN_SKETCH.md and the resolved trade-offs in DECISIONS.md.
Published on npm as conducted-mcp — runs with zero install via npx.
Add the server to your MCP client. Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json):
{
"mcpServers": {
"conducted": {
"command": "npx",
"args": ["-y", "conducted-mcp"]
}
}
}
Then ask your agent to "run the Conducted kickoff for this project," or call any tool directly.
A stateless Streamable HTTP endpoint runs live on Cloudflare Workers — connect by URL, nothing to install:
{
"mcpServers": {
"conducted": {
"url": "https://conducted-mcp.jonathanmostov.workers.dev/mcp"
}
}
}
Because the server is stateless and holds no data (Model C), the endpoint is safe to run unauthenticated, guarded by rate limiting.
See docs/DEMO.md for a real transcript of the kickoff flow — the front-door prompt, the branched interview, and the phase procedures — captured verbatim from the running server.
npm install
npm run build # bundles the methodology text, then strict tsc
npm test # vitest
npm run lint # eslint + prettier
npm start # run the stdio server
The server is TypeScript on the official @modelcontextprotocol/sdk, ESM, strict mode. See CONTRIBUTING.md for the layout and conventions.
work/goal-briefs/ — the goal briefs that drove this buildwork/intent-docs/ — one per ticket, the per-session contractswork/standups/ — cycle-gate standupswork/decision-log.md — the append-only record of decisionsAGENT_CONVENTIONS.md — how every session runs, model- and tool-agnosticMIT © 2026 Jonathan Mostov
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.