Hosting

Local stdio process

Transport

stdio

Endpoint

Local process; no hosted endpoint documented

Authentication

No credentials were configured; the tested read-only tool “ui_search” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

• Node.js 18+
• The npm package repository matched the repository linked from the public profile.

Setup steps

1. npx -y mcp-probe-kit@4.1.1

The server returned 29 tools in tools/list. Only “ui_search” was invoked with a synthetic read-only input and succeeded.

• init_project

  当用户提供一句话需求时使用。基于 Spec-Driven Development 理念，分析需求并生成完整的项目规格文档（需求分析/技术设计/任务拆解）。适合项目初期的需求澄清和规划

  Parameters: input, project_name, project_root
  01
• gencommit

  当用户需要生成 Git commit 消息时使用。返回 Conventional Commits 规范说明、步骤、输出模板和示例，供 AI 根据变更内容生成最终 commit message。它不直接代写最终消息，也不应被判定为空结果

  Parameters: changes, type, project_root
  02
• git_work_report

  基于 Git diff 分析生成工作报告（日报/周期报） 核心功能： - 支持日报模式（单个日期）和周期报模式（日期范围） - 自动读取指定日期的所有 Git 提交 - 对每个提交执行 git show 获取完整 diff - 使用 AI 分析 diff 内容提取实际工作内容 输出格式： - 只输出「工作内容」部分 - 每条以 - 开头，中文，简洁专业 - 格式：做了什么 + 改了哪里/达到什么效果 - 不输出：提交哈希、文件列表、统计数据、风险总结 使用示例： - 日报：git_work_report --date 2026-1-27 - 周期报：git_work_report --start_date 2026-2-1 --end_date 2026-2-6

  Parameters: date, start_date, end_date, output_file, project_root
  03
• code_review

  当用户需要审查代码、真实 Git diff 或托管 Plan 的交付一致性时使用。MCP 可确定性收集 changed files、Plan 声明范围、产物、测试、公共契约、架构和 revision 证据；代码语义问题仍由 Agent 审查，不伪装成静态扫描器

  Parameters: code, file_path, project_root, plan_id, diff_mode, base_ref, head_ref, max_diff_chars, focus
  04
• code_insight

  当用户需要基于代码图谱分析调用链、上下文和影响面时使用。默认桥接 GitNexus，支持 query/context/impact 模式；不可用时自动降级并返回原因

  Parameters: mode, query, target, repo, project_root, goal, task_context, direction, max_depth, include_tests
  05
• refactor

  当用户需要重构代码、改善代码结构时使用。指南型工具：注入 code/file_path 与重构清单，由 Agent 分析后输出重构计划 JSON；MCP 不自动修改源文件

  Parameters: code, file_path, project_root, goal
  06
• gentest

  当用户需要为代码生成单元测试时使用。指南型工具：注入 code/file_path 与测试清单，由 Agent 生成完整测试代码；MCP 不自动生成或运行测试

  Parameters: code, file_path, project_root, framework
  07
• workflow

  仅当 Agent 阅读 Skill 和各工具 description 后仍不确定该调用哪个 MCP 时使用的兜底选择指南。workflow 不做自然语言意图识别：scenario=auto（默认）只返回工具选择规则与速查表，不从 intent 猜 firstTool；Agent 根据完整对话自行判断或澄清。若 Agent 已明确场景，可传显式 scenario 获取该场景的确定性 firstTool、phases 和参数提示。同时确保用户项目已存在 .agents/skills/mcp-probe-kit/SKILL.md 与 AGENTS.md 中的 Skill 引用（缺失则自动创建/更新）。

  Parameters: intent, scenario, project_root
  08
• init_project_context

  生成/更新项目上下文写作计划（delegated）：MCP 写入 AGENTS.md 与 layout.json；project-context 分类文档与 graph-insights 由 Agent 按返回的 plan 落盘。新功能请先 start_feature，修 bug 请先 start_bugfix。

  Parameters: docs_dir, index_style, output, output_dir, filename, locale
  09
• estimate

  当用户需要估算开发工作量、评估任务时间时使用。估算开发工作量，输出故事点、时间范围（乐观/正常/悲观）、风险点

  Parameters: task_description, code_context, team_size, experience_level
  10
• check_spec

  校验已落盘的功能规格（docs/specs/<feature_name>/requirements|design|tasks.md）是否完整：检测残留 [填写] 占位、缺失章节、缺 FR/验收标准、FR 未进覆盖矩阵。写完规格后、进入实现前调用；未通过按报告补全后重跑。

  Parameters: feature_name, docs_dir, project_root
  11
• start_feature

  新功能、功能增强、大版本升级或跨模块研发的首选入口。Agent 必须把当前对话已确认的完整目标、范围、模块、阶段和约束汇总到 description；用户只说“继续/开始/往下做”时不得原样透传。默认 spec_layout=auto，复杂多模块或多阶段需求会先生成 parent-child 子规格拆分计划，再进入 add_feature→check_spec→实现。仅在规格布局和子规格已明确、且只需渲染规格模板时才直接用 add_feature。

  Parameters: feature_name, description, docs_dir, project_root, template_profile, spec_layout, subspecs, requirements_mode, loop_max_rounds, loop_question_budget, loop_assumption_cap
  12
• start_bugfix

  当用户需要找问题、修 bug、排查异常时使用。默认按 SRC-8（TBP-inspired）编排：收敛边界→真因工作表→修复→测试→记忆沉淀。

  Parameters: error_message, description, stack_trace, code_context, project_root, docs_dir, feature_name, analysis_mode, template_profile, requirements_mode, loop_max_rounds, loop_question_budget, loop_assumption_cap
  13
• start_onboard

  当用户需要快速上手新项目时使用。编排：生成上下文文档。

  Parameters: project_path, docs_dir
  14
• start_ralph

  用于需要多轮小步实现、每轮真实验证和正式收敛的长任务。返回有界 Delegated Plan、每轮 Heartbeat 证据契约和可选前台辅助脚本；不自动运行循环、不创建后台进程。安全停止不等于成功

  Parameters: goal, mode, completion_promise, test_command, cli_command, max_iterations, max_rounds, max_minutes, confirm_every, confirm_timeout, max_same_output, max_diff_lines, cooldown_seconds, project_root
  15
• interview

  当用户需求不明确、需要澄清需求时使用。需求访谈工具，在开发前通过结构化提问澄清需求，避免理解偏差和返工；生成访谈记录文件供后续 start_feature/add_feature 使用；仅支持 feature 类型

  Parameters: description, feature_name, answers
  16
• ui_design_system

  生成可执行的视觉方向，而不是风格标签拼盘。输出核心任务、信息架构、内容密度、排版与色彩策略、组件原则、明确禁用项和截图验收标准。

  Parameters: product_type, description, stack, target_audience, screen_type, visual_direction, density, brand_personality, references, avoid, target_score, keywords
  17
• ui_search

  搜索页面结构、组件、交互规范和实现参考。新 UI 流程优先使用 structure 模式按任务和页面类型选择信息架构；旧 search/catalog/template 模式继续兼容。

  Parameters: mode, query, screen_type, density, category, stack, limit, min_score
  18
• start_ui

  编排 UI 设计与实现：先锁定视觉方向和信息架构，再生成关键页面，后续通过真实截图评分与迭代完成验收。

  Parameters: description, framework, template, project_root, target_audience, screen_type, visual_direction, density, brand_personality, references, avoid, target_score, review_max_rounds, template_profile, mode, requirements_mode, loop_max_rounds, loop_question_budget, loop_assumption_cap
  19
• start_product

  产品设计完整工作流入口。返回闭环 delegated plan：Agent 生成 PRD 与原型文档，调用 ui_design_system 和 start_ui 完成设计系统及可交互 HTML 原型，并更新项目上下文；不会引用不存在的 gen_prd/gen_prototype 工具。

  Parameters: description, requirements_file, product_name, product_type, target_users, constraints, skip_design_system, docs_dir, project_root
  20
• history_session_bootstrap

  Initialize or resume a lossless project history archive (docs/history-session/). Call once near the start of a conversation with the user's verbatim first request as initial_user_input. Echo the returned session_key on later calls in this chat. Without host/explicit session_key, the server mints a new hs_<uuid> handle and opens a new archive (does not merge into a shared project-active file). Never invent a key. Returns bounded state (≤64 KiB). Disable with MCP_HISTORY_SESSION=0|false|off.

  Parameters: project_root, workspace_root, session_key, title, initial_user_input, history_dir, create_if_missing, mode
  21
• history_session_checkpoint

  Append an idempotent, redacted development checkpoint. Pass session_key and expected_path exactly as returned by history_session_bootstrap, plus the user's verbatim raw_user_input. Archives that exceed MCP_HISTORY_MAX_LINES/BYTES soft-rotate to the next N.md before append.

  Parameters: project_root, workspace_root, session_key, expected_path, history_dir, turn_id, timestamp, user_intent, raw_user_input, findings, decisions, files_changed, tests, runtime_state, remaining_issues, next_actions, notes
  22
• history_session_validate

  Validate history-session numbering, duplicates, and derived state/manifest. Optional repair rebuilds state and manifest from Markdown archives.

  Parameters: project_root, workspace_root, history_dir, repair
  23
• history_session_search

  Search lossless history archives by deterministic keywords and return a bounded page of ranked locations and snippets. Use history_session_read to retrieve exact source text.

  Parameters: project_root, workspace_root, history_dir, query, cursor, limit
  24
• history_session_read

  Read one lossless numeric Markdown archive by number or a path returned from history_session_search. Responses are UTF-8-safe pages: max_bytes defaults to 32 KiB and is capped at 64 KiB; follow next_cursor to recover the complete source.

  Parameters: project_root, workspace_root, history_dir, number, path, cursor, max_bytes, expected_hash
  25
• plan_heartbeat

  由 Agent 在 Delegated Plan 执行过程中记录轻量检查点。首次调用必须提供完整 plan；后续合并步骤、证据、产物、候选经验、验收结果、运行证据和 revision。除 requirements 外，每条用于收敛的 evidence 必须至少提供 reference 或 revision，否则 converge 会明确拒绝。只记录状态，不代替 Agent 执行。

  Parameters: plan_id, project_root, plan, status, current_step_id, completed_step_ids, skipped_steps, unresolved_items, evidence, declared_scope, artifacts, memory_candidates, architecture_candidates, acceptance_results, runtime_evidence, last_verified_revision
  26
• resume_plan

  从 .mcp-probe-kit/plans/ 读取 Delegated Plan 检查点，按依赖计算下一可执行步骤、阻塞步骤和 resumeContext。plan_id 可选；省略时自动恢复当前项目最近更新的 active/blocked Plan。本工具只读取状态，不替 Agent 执行；返回 mustContinue=true 后 Agent 必须立即执行 nextStep/nextTool，逐步调用 plan_heartbeat，禁止只汇报恢复结果后停止。

  Parameters: plan_id, project_root
  27
• converge

  按 Delegated Plan 自己声明的证据和质量闸门关闭计划。任一未完成步骤、未决事项、必需证据或验收结果缺失都会拒绝收敛；除 requirements 外，证据只有摘要但没有 reference/revision 也不算可复核证据。调用参数只能增加证据要求，不能削弱 Plan。

  Parameters: plan_id, project_root, feature_name, docs_dir, required_evidence_kinds
  28
• architecture

  独立架构领域能力，使用 ARC-8 完成架构评估、设计、校验和漂移检查。可直接调用，也可由功能、Bug 或重构流程按需组合；MCP 负责方法、门禁与结构化证据，不替 Agent 声称绝对最优架构。

  Parameters: mode, description, project_root, scope, constraints, non_goals, baseline, current_facts, structural_causes, protected_invariants, alternatives, decision, target_architecture, transition_plan, diff, runtime_evidence, observed_drift, save_to_docs, collect_evidence
  29

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Runtime verification covered one read-only tool call (ui_search); other listed tools were not individually exercised.

• MCP.Directory public profile

  Name, description, publisher identifier, categories, transport, tool inventory, and install configuration.

• Linked publisher repository

  Repository URL linked from the public profile; npm package repository metadata matched this GitHub repository.

• npm registry metadata

  Published package version 4.1.1 checked before launch. Registry repository: git+https://github.com/mybolide/mcp-probe-kit.git.

• maintainer repository documentation

  Maintainer README documents 29 MCP tools for project context, workflows, planning, memory/history sessions, and coding lifecycle.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.