M
mybolide/mcp-probe-kit
Spec-driven development workflow MCP with resumable plans and a converge gate
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"mybolide-mcp-probe-kit": {
"command": "npx",
"args": ["-y", "mcp-probe-kit@4.1.1"]
}
}
}Parsed from the README we fetched on 2026-10-29; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"mybolide-mcp-probe-kit": {
"command": "npx",
"args": ["-y", "mcp-probe-kit@4.1.1"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio mybolide-mcp-probe-kit -- npx -y mcp-probe-kit@4.1.1
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-10-30 · last seen 2026-11-14 · seen 16× · listed by 16 sources
- Score
- score 1,603 · 16 sources · mcp
- Install
npx -y mcp-probe-kit@4.1.1
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y mcp-probe-kit@4.1.1. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-30；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# mcp-probe-kit — Know the Context, Feed the Moment
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
知时MCP | mcp-probe-kit
Know the Context, Feed the Moment.
Introspection · Context Hydration · Delegated Orchestration
> Talk is cheap, show me the Context.
> mcp-probe-kit is a protocol-level toolkit designed for developers who want AI to understand project intent, choose a precise workflow, and retain validated experience without flooding the model with internal actions.
Languages: English | 简体中文 | 日本語 | 한국어 | Español | Français | Deutsch | Português (BR)
> 🚀 AI-Powered Complete Development Toolkit - Covering the Entire Development Lifecycle
A powerful MCP (Model Context Protocol) server with 29 model-visible tools by default (24 base + 5 History Session; disable History with MCPHISTORYSESSION=0), 35 when Memory is also configured, and a 39-tool compatibility surface available through MCPTOOLSET=full. It covers the complete workflow from product analysis to final release and supports structured output.
🎉 v4 stable release: native MCP Apps, resumable plans, evidence convergence, managed GitNexus Sidecar, parent-child specs, and a version-locked CLI fallback.
Supports All MCP Clients: Cursor, Claude Desktop, Cline, Continue, and more
Protocol Support: Legacy MCP (2025-era) + Modern MCP 2026-07-28 · SDK: split TypeScript SDK v2 packages
Runtime: Node.js 20 or newer. MCPPROTOCOLMODE=auto is the default; use legacy or modern only for compatibility diagnosis.
## 🎬 v4 in action
v4 turns delegated Agent work into an observable and verifiable delivery loop. The animations below are rendered from the same MCP App source shipped in the npm package—not separate marketing mockups.
Feature Workbench — parent-child specs, active step, outputs, evidence, and cross-session recovery.
Memory Center — semantic search, full-content inspection, lifecycle state, evidence, stale marking, and confirmed deletion.
Convergence Gate — blocks closure when steps or requirements/spec/implementation/test/review evidence are incomplete.
Five native MCP Apps: Memory Center, Feature Workbench, Bug Workbench, Product Workbench, and Convergence Gate.
History Session (default ON): lossless local chat handoff under docs/history-session/ — bootstrap → checkpoint → search/read, no vector DB required.
Resumable delegated plans: planheartbeat persists real progress; resumeplan restores the next executable step.
Evidence-based convergence: converge gates delivery and long-term Memory writes.
Managed GitNexus Sidecar: version/platform/architecture/Node isolation, integrity verification, real FTS probe, and safe degradation.
Version-locked CLI fallback: project-local probe wrappers reach the same Tool Registry when a host drops the MCP tool lease.
Parent-child specifications: complex releases are decomposed and recursively validated instead of being flattened into one oversized spec.
Open the five live, read-only MCP App demos
> v4 stable: mcp-probe-kit@4.1.1 is the current stable release and npm latest channel.
## 📚 Complete Documentation
👉 https://mcp-probe-kit.bytezonex.com
Quick Start - Setup in 5 minutes
Local Memory Stack (Qdrant + Nomic Embed) - Docker Compose, ports 50008 / 50012, MCP env
All Tools - Default (+ History), conditional Memory, App-only, and full compatibility surfaces
Know the Context, Feed the Moment.
Introspection · Context Hydration · Delegated Orchestration
> Talk is cheap, show me the Context.
> mcp-probe-kit is a protocol-level toolkit designed for developers who want AI to understand project intent, choose a precise workflow, and retain validated experience without flooding the model with internal actions.
Languages: English | 简体中文 | 日本語 | 한국어 | Español | Français | Deutsch | Português (BR)
> 🚀 AI-Powered Complete Development Toolkit - Covering the Entire Development Lifecycle
A powerful MCP (Model Context Protocol) server with 29 model-visible tools by default (24 base + 5 History Session; disable History with MCPHISTORYSESSION=0), 35 when Memory is also configured, and a 39-tool compatibility surface available through MCPTOOLSET=full. It covers the complete workflow from product analysis to final release and supports structured output.
🎉 v4 stable release: native MCP Apps, resumable plans, evidence convergence, managed GitNexus Sidecar, parent-child specs, and a version-locked CLI fallback.
Supports All MCP Clients: Cursor, Claude Desktop, Cline, Continue, and more
Protocol Support: Legacy MCP (2025-era) + Modern MCP 2026-07-28 · SDK: split TypeScript SDK v2 packages
Runtime: Node.js 20 or newer. MCPPROTOCOLMODE=auto is the default; use legacy or modern only for compatibility diagnosis.
## 🎬 v4 in action
v4 turns delegated Agent work into an observable and verifiable delivery loop. The animations below are rendered from the same MCP App source shipped in the npm package—not separate marketing mockups.
Feature Workbench — parent-child specs, active step, outputs, evidence, and cross-session recovery.
Memory Center — semantic search, full-content inspection, lifecycle state, evidence, stale marking, and confirmed deletion.
Convergence Gate — blocks closure when steps or requirements/spec/implementation/test/review evidence are incomplete.
Five native MCP Apps: Memory Center, Feature Workbench, Bug Workbench, Product Workbench, and Convergence Gate.
History Session (default ON): lossless local chat handoff under docs/history-session/ — bootstrap → checkpoint → search/read, no vector DB required.
Resumable delegated plans: planheartbeat persists real progress; resumeplan restores the next executable step.
Evidence-based convergence: converge gates delivery and long-term Memory writes.
Managed GitNexus Sidecar: version/platform/architecture/Node isolation, integrity verification, real FTS probe, and safe degradation.
Version-locked CLI fallback: project-local probe wrappers reach the same Tool Registry when a host drops the MCP tool lease.
Parent-child specifications: complex releases are decomposed and recursively validated instead of being flattened into one oversized spec.
Open the five live, read-only MCP App demos
> v4 stable: mcp-probe-kit@4.1.1 is the current stable release and npm latest channel.
## 📚 Complete Documentation
👉 https://mcp-probe-kit.bytezonex.com
Quick Start - Setup in 5 minutes
Local Memory Stack (Qdrant + Nomic Embed) - Docker Compose, ports 50008 / 50012, MCP env
All Tools - Default (+ History), conditional Memory, App-only, and full compatibility surfaces
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mybolide-mcp-probe-kit/)
- Source
- awesome · https://github.com/mybolide/mcp-probe-kit
- Browse by field
- MCP servers
- Listed by
- 16 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.