Conducted MCP
An MCP server that helps AI agents plan and track software projects using the Conducted Development methodology, providing artifact validation, kickoff guidance, and project rituals.
README
Conducted MCP
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.
What it does
A connecting agent gets, on demand:
- A guided kickoff (
kickoffprompt +kickoff_questions/kickoff_plantools) — 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. - Strict artifact validation (
validate_artifact) — submit a goal brief / intent doc / session log / standup, get back{ valid, missing, warnings }. - Phase procedures (
next_procedure) — the ordered steps, what to read first, and the escalation points for wherever the agent is in the loop. - Mechanical rule checks (
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.
Why it's built this way (Model C)
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.
Quick start
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.
Or connect to the hosted endpoint (no install)
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.
Demo
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. <!-- a client-side screen recording will be added here -->
Development
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.
The methodology, in the repo
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-agnostic
License
MIT © 2026 Jonathan Mostov
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。