mcp-probe-kit 3.0.3 → 3.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +215 -199
- package/docs/assets/js/i18n.js +274 -0
- package/docs/assets/logo-zh.png +0 -0
- package/docs/assets/logo.png +0 -0
- package/docs/data/tools.js +416 -416
- package/docs/i18n/en.json +518 -0
- package/docs/i18n/ja.json +518 -0
- package/docs/i18n/ko.json +518 -0
- package/docs/i18n/zh-CN.json +518 -0
- package/docs/index.html +43 -32
- package/docs/pages/all-tools.html +31 -9
- package/docs/pages/examples.html +229 -213
- package/docs/pages/getting-started.html +90 -78
- package/docs/pages/migration.html +78 -63
- package/docs/project-context.md +1 -1
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -1,60 +1,75 @@
|
|
|
1
|
-
|
|
1
|
+
<div align="center">
|
|
2
|
+
<img src="docs/assets/logo.png" alt="知时MCP Logo" width="160"/>
|
|
3
|
+
<h1>知时MCP | mcp-probe-kit</h1>
|
|
4
|
+
<p><strong>Know the Context, Feed the Moment.</strong></p>
|
|
5
|
+
<p>
|
|
6
|
+
<code>Introspection</code> · <code>Context Hydration</code> · <code>Delegated Orchestration</code>
|
|
7
|
+
</p>
|
|
8
|
+
</div>
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
> **Talk is cheap, show me the Context.**
|
|
13
|
+
>
|
|
14
|
+
> mcp-probe-kit is a protocol-level toolkit designed for developers who want AI to truly understand their project's intent. It's not just a collection of 21 tools—it's a context-aware system that helps AI agents grasp what you're building.
|
|
15
|
+
|
|
16
|
+
**Languages**: [English](README.md) | [简体中文](i18n/README.zh-CN.md) | [日本語](i18n/README.ja-JP.md) | [한국어](i18n/README.ko-KR.md) | [Español](i18n/README.es-ES.md) | [Français](i18n/README.fr-FR.md) | [Deutsch](i18n/README.de-DE.md) | [Português (BR)](i18n/README.pt-BR.md)
|
|
2
17
|
|
|
3
18
|
[](https://www.npmjs.com/package/mcp-probe-kit)
|
|
4
19
|
[](https://www.npmjs.com/package/mcp-probe-kit)
|
|
5
20
|
[](https://opensource.org/licenses/MIT)
|
|
6
21
|
[](https://github.com/mybolide/mcp-probe-kit/stargazers)
|
|
7
22
|
|
|
8
|
-
> 🚀 AI
|
|
23
|
+
> 🚀 AI-Powered Complete Development Toolkit - Covering the Entire Development Lifecycle
|
|
9
24
|
|
|
10
|
-
|
|
25
|
+
A powerful MCP (Model Context Protocol) server providing **21 tools** covering the complete workflow from product analysis to final release (Requirements → Design → Development → Quality → Release), all tools support **structured output**.
|
|
11
26
|
|
|
12
|
-
**🎉 v3.0
|
|
27
|
+
**🎉 v3.0 Major Update**: Streamlined tool count, focus on core competencies, eliminate choice paralysis, let AI do more native work
|
|
13
28
|
|
|
14
|
-
|
|
29
|
+
**Supports All MCP Clients**: Cursor, Claude Desktop, Cline, Continue, and more
|
|
15
30
|
|
|
16
|
-
|
|
31
|
+
**Protocol Version**: MCP 2025-11-25 · **SDK**: @modelcontextprotocol/sdk 1.25.3
|
|
17
32
|
|
|
18
33
|
---
|
|
19
34
|
|
|
20
|
-
## 📚
|
|
35
|
+
## 📚 Complete Documentation
|
|
21
36
|
|
|
22
37
|
**👉 [https://mcp-probe-kit.bytezonex.com](https://mcp-probe-kit.bytezonex.com/)**
|
|
23
38
|
|
|
24
|
-
- [
|
|
25
|
-
- [
|
|
26
|
-
- [
|
|
27
|
-
- [v3.0
|
|
39
|
+
- [Quick Start](https://mcp-probe-kit.bytezonex.com/pages/getting-started.html) - Setup in 5 minutes
|
|
40
|
+
- [All Tools](https://mcp-probe-kit.bytezonex.com/pages/all-tools.html) - Complete list of 21 tools
|
|
41
|
+
- [Best Practices](https://mcp-probe-kit.bytezonex.com/pages/examples.html) - Full development workflow guide
|
|
42
|
+
- [v3.0 Migration Guide](https://mcp-probe-kit.bytezonex.com/pages/migration.html) - Upgrade from v2.x to v3.0
|
|
28
43
|
|
|
29
44
|
---
|
|
30
45
|
|
|
31
|
-
## ✨
|
|
46
|
+
## ✨ Core Features
|
|
32
47
|
|
|
33
|
-
### 📦 21
|
|
48
|
+
### 📦 21 Tools
|
|
34
49
|
|
|
35
|
-
- **🔄
|
|
50
|
+
- **🔄 Workflow Orchestration** (6 tools) - One-click complex development workflows
|
|
36
51
|
- `start_feature`, `start_bugfix`, `start_onboard`, `start_ui`, `start_product`, `start_ralph`
|
|
37
|
-
- **🔍
|
|
52
|
+
- **🔍 Code Analysis** (3 tools) - Code quality and refactoring
|
|
38
53
|
- `code_review`, `fix_bug`, `refactor`
|
|
39
|
-
- **📝 Git
|
|
54
|
+
- **📝 Git Tools** (2 tools) - Git commits and work reports
|
|
40
55
|
- `gencommit`, `git_work_report`
|
|
41
|
-
- **⚡
|
|
56
|
+
- **⚡ Code Generation** (1 tool) - Test generation
|
|
42
57
|
- `gentest`
|
|
43
|
-
- **📦
|
|
58
|
+
- **📦 Project Management** (7 tools) - Project initialization and requirements management
|
|
44
59
|
- `init_project`, `init_project_context`, `add_feature`, `estimate`, `interview`, `ask_user`
|
|
45
|
-
- **🎨 UI/UX
|
|
60
|
+
- **🎨 UI/UX Tools** (3 tools) - Design systems and data synchronization
|
|
46
61
|
- `ui_design_system`, `ui_search`, `sync_ui_data`
|
|
47
62
|
|
|
48
|
-
### 🎯
|
|
63
|
+
### 🎯 Structured Output
|
|
49
64
|
|
|
50
|
-
|
|
65
|
+
Core and orchestration tools support **structured output**, returning machine-readable JSON data, improving AI parsing accuracy, supporting tool chaining and state tracking.
|
|
51
66
|
|
|
52
|
-
### 🧭
|
|
67
|
+
### 🧭 Delegated Orchestration Protocol
|
|
53
68
|
|
|
54
|
-
|
|
55
|
-
AI
|
|
69
|
+
All `start_*` orchestration tools return an **execution plan** in `structuredContent.metadata.plan`.
|
|
70
|
+
AI needs to **call tools step by step and persist files**, rather than the tool executing internally.
|
|
56
71
|
|
|
57
|
-
**Plan Schema
|
|
72
|
+
**Plan Schema (Core Fields)**:
|
|
58
73
|
```json
|
|
59
74
|
{
|
|
60
75
|
"mode": "delegated",
|
|
@@ -62,177 +77,177 @@ AI 需要**按步骤调用工具并落盘文件**,而不是由工具内部直
|
|
|
62
77
|
{
|
|
63
78
|
"id": "spec",
|
|
64
79
|
"tool": "add_feature",
|
|
65
|
-
"args": { "feature_name": "user-auth", "description": "
|
|
80
|
+
"args": { "feature_name": "user-auth", "description": "User authentication feature" },
|
|
66
81
|
"outputs": ["docs/specs/user-auth/requirements.md"]
|
|
67
82
|
}
|
|
68
83
|
]
|
|
69
84
|
}
|
|
70
85
|
```
|
|
71
86
|
|
|
72
|
-
|
|
73
|
-
- `mode`:
|
|
74
|
-
- `steps`:
|
|
75
|
-
- `tool`:
|
|
76
|
-
- `action`:
|
|
77
|
-
- `args`:
|
|
78
|
-
- `outputs`:
|
|
79
|
-
- `when/dependsOn/note`:
|
|
87
|
+
**Field Description**:
|
|
88
|
+
- `mode`: Fixed as `delegated`
|
|
89
|
+
- `steps`: Array of execution steps
|
|
90
|
+
- `tool`: Tool name (e.g. `add_feature`)
|
|
91
|
+
- `action`: Manual action description when no tool (e.g. `update_project_context`)
|
|
92
|
+
- `args`: Tool parameters
|
|
93
|
+
- `outputs`: Expected artifacts
|
|
94
|
+
- `when/dependsOn/note`: Optional conditions and notes
|
|
80
95
|
|
|
81
|
-
### 🧩
|
|
96
|
+
### 🧩 Structured Output Field Specification (Key Fields)
|
|
82
97
|
|
|
83
|
-
|
|
84
|
-
- `summary`:
|
|
85
|
-
- `status`:
|
|
86
|
-
- `steps`:
|
|
87
|
-
- `artifacts`:
|
|
88
|
-
- `metadata.plan`:
|
|
89
|
-
- `specArtifacts`:
|
|
90
|
-
- `estimate`:
|
|
98
|
+
Both orchestration and atomic tools return `structuredContent`, common fields:
|
|
99
|
+
- `summary`: One-line summary
|
|
100
|
+
- `status`: Status (pending/success/failed/partial)
|
|
101
|
+
- `steps`: Execution steps (orchestration tools)
|
|
102
|
+
- `artifacts`: Artifact list (path + purpose)
|
|
103
|
+
- `metadata.plan`: Delegated execution plan (only start_*)
|
|
104
|
+
- `specArtifacts`: Specification artifacts (start_feature)
|
|
105
|
+
- `estimate`: Estimation results (start_feature / estimate)
|
|
91
106
|
|
|
92
|
-
### 🧠
|
|
107
|
+
### 🧠 Requirements Clarification Mode (Requirements Loop)
|
|
93
108
|
|
|
94
|
-
|
|
95
|
-
|
|
109
|
+
When requirements are unclear, use `requirements_mode=loop` in `start_feature / start_bugfix / start_ui`.
|
|
110
|
+
This mode performs 1-2 rounds of structured clarification before entering spec/fix/UI execution.
|
|
96
111
|
|
|
97
|
-
|
|
112
|
+
**Example:**
|
|
98
113
|
```json
|
|
99
114
|
{
|
|
100
115
|
"feature_name": "user-auth",
|
|
101
|
-
"description": "
|
|
116
|
+
"description": "User authentication feature",
|
|
102
117
|
"requirements_mode": "loop",
|
|
103
118
|
"loop_max_rounds": 2,
|
|
104
119
|
"loop_question_budget": 5
|
|
105
120
|
}
|
|
106
121
|
```
|
|
107
122
|
|
|
108
|
-
### 🧩
|
|
123
|
+
### 🧩 Template System (Regular Model Friendly)
|
|
109
124
|
|
|
110
|
-
`add_feature`
|
|
125
|
+
`add_feature` supports template profiles, default `auto` auto-selects: prefers `guided` when requirements are incomplete (includes detailed filling rules and checklists), selects `strict` when requirements are complete (more compact structure, suitable for high-capability models or archival scenarios).
|
|
111
126
|
|
|
112
|
-
|
|
127
|
+
**Example:**
|
|
113
128
|
```json
|
|
114
129
|
{
|
|
115
|
-
"description": "
|
|
130
|
+
"description": "Add user authentication feature",
|
|
116
131
|
"template_profile": "auto"
|
|
117
132
|
}
|
|
118
133
|
```
|
|
119
134
|
|
|
120
|
-
|
|
121
|
-
- `start_feature`
|
|
122
|
-
- `start_bugfix` / `start_ui`
|
|
135
|
+
**Applicable Tools**:
|
|
136
|
+
- `start_feature` passes `template_profile` to `add_feature`
|
|
137
|
+
- `start_bugfix` / `start_ui` also support `template_profile` for controlling guidance strength (auto/guided/strict)
|
|
123
138
|
|
|
124
|
-
|
|
125
|
-
- `guided
|
|
126
|
-
- `strict
|
|
127
|
-
- `auto
|
|
139
|
+
**Template Profile Strategy**:
|
|
140
|
+
- `guided`: Less/incomplete requirements info, regular model priority
|
|
141
|
+
- `strict`: Requirements structured, prefer more compact guidance
|
|
142
|
+
- `auto`: Default recommendation, auto-selects guided/strict
|
|
128
143
|
|
|
129
|
-
### 🔄
|
|
144
|
+
### 🔄 Workflow Orchestration
|
|
130
145
|
|
|
131
|
-
6
|
|
132
|
-
- `start_feature` -
|
|
133
|
-
- `start_bugfix` - Bug
|
|
134
|
-
- `start_onboard` -
|
|
135
|
-
- `start_ui` - UI
|
|
136
|
-
- `start_product` -
|
|
137
|
-
- `start_ralph` - Ralph Loop
|
|
146
|
+
6 intelligent orchestration tools that automatically combine multiple basic tools for one-click complex development workflows:
|
|
147
|
+
- `start_feature` - New feature development (Requirements → Design → Estimation)
|
|
148
|
+
- `start_bugfix` - Bug fixing (Analysis → Fix → Testing)
|
|
149
|
+
- `start_onboard` - Project onboarding (Generate project context docs)
|
|
150
|
+
- `start_ui` - UI development (Design system → Components → Code)
|
|
151
|
+
- `start_product` - Product design (PRD → Prototype → Design system → HTML)
|
|
152
|
+
- `start_ralph` - Ralph Loop (Iterative development until goal completion)
|
|
138
153
|
|
|
139
|
-
### 🚀
|
|
154
|
+
### 🚀 Product Design Workflow
|
|
140
155
|
|
|
141
|
-
`start_product`
|
|
156
|
+
`start_product` is a complete product design orchestration tool, from requirements to interactive prototype:
|
|
142
157
|
|
|
143
|
-
|
|
144
|
-
1.
|
|
145
|
-
2.
|
|
146
|
-
3.
|
|
147
|
-
4. **HTML
|
|
148
|
-
5.
|
|
158
|
+
**Workflow:**
|
|
159
|
+
1. **Requirements Analysis** - Generate standard PRD (product overview, feature requirements, page list)
|
|
160
|
+
2. **Prototype Design** - Generate detailed prototype docs for each page
|
|
161
|
+
3. **Design System** - Generate design specifications based on product type
|
|
162
|
+
4. **HTML Prototype** - Generate interactive prototype viewable in browser
|
|
163
|
+
5. **Project Context** - Auto-update project documentation
|
|
149
164
|
|
|
150
|
-
|
|
151
|
-
- `start_product.structuredContent.artifacts
|
|
152
|
-
- `interview.structuredContent.mode
|
|
165
|
+
**Structured Output Additions**:
|
|
166
|
+
- `start_product.structuredContent.artifacts`: Artifact list (PRD, prototypes, design system, etc.)
|
|
167
|
+
- `interview.structuredContent.mode`: `usage` / `questions` / `record`
|
|
153
168
|
|
|
154
169
|
### 🎨 UI/UX Pro Max
|
|
155
170
|
|
|
156
|
-
3
|
|
157
|
-
- `start_ui` -
|
|
158
|
-
- `ui_design_system` -
|
|
159
|
-
- `ui_search` - UI/UX
|
|
160
|
-
- `sync_ui_data` -
|
|
171
|
+
3 UI/UX tools with `start_ui` as the unified entry point:
|
|
172
|
+
- `start_ui` - One-click UI development (supports intelligent mode) (orchestration tool)
|
|
173
|
+
- `ui_design_system` - Intelligent design system generation
|
|
174
|
+
- `ui_search` - UI/UX data search (BM25 algorithm)
|
|
175
|
+
- `sync_ui_data` - Sync latest UI/UX data locally
|
|
161
176
|
|
|
162
|
-
|
|
177
|
+
**Note**: `start_ui` automatically calls `ui_design_system` and `ui_search`, you don't need to call them separately.
|
|
163
178
|
|
|
164
|
-
|
|
165
|
-
- [ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) - UI/UX
|
|
166
|
-
- [json-render](https://github.com/vercel-labs/json-render) - JSON
|
|
179
|
+
**Inspiration:**
|
|
180
|
+
- [ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) - UI/UX design system philosophy
|
|
181
|
+
- [json-render](https://github.com/vercel-labs/json-render) - JSON template rendering engine
|
|
167
182
|
|
|
168
|
-
|
|
183
|
+
**Why use `sync_ui_data`?**
|
|
169
184
|
|
|
170
|
-
|
|
171
|
-
- 🎨
|
|
172
|
-
- 🔣
|
|
173
|
-
- 📊
|
|
174
|
-
- 🎯
|
|
175
|
-
- 📐
|
|
185
|
+
Our `start_ui` tool relies on a rich UI/UX database (colors, icons, charts, components, design patterns, etc.) to generate high-quality design systems and code. This data comes from npm package [uipro-cli](https://www.npmjs.com/package/uipro-cli), including:
|
|
186
|
+
- 🎨 Color schemes (mainstream brand colors, color palettes)
|
|
187
|
+
- 🔣 Icon libraries (React Icons, Heroicons, etc.)
|
|
188
|
+
- 📊 Chart components (Recharts, Chart.js, etc.)
|
|
189
|
+
- 🎯 Landing page templates (SaaS, e-commerce, government, etc.)
|
|
190
|
+
- 📐 Design specifications (spacing, fonts, shadows, etc.)
|
|
176
191
|
|
|
177
|
-
|
|
178
|
-
1.
|
|
179
|
-
2.
|
|
180
|
-
3.
|
|
192
|
+
**Data Sync Strategy:**
|
|
193
|
+
1. **Embedded Data**: Synced at build time, works offline
|
|
194
|
+
2. **Cached Data**: Runtime updates to `~/.mcp-probe-kit/ui-ux-data/`
|
|
195
|
+
3. **Manual Sync**: Use `sync_ui_data` to force update latest data
|
|
181
196
|
|
|
182
|
-
|
|
197
|
+
This ensures `start_ui` can generate professional-grade UI code even offline.
|
|
183
198
|
|
|
184
|
-
### 🎤
|
|
199
|
+
### 🎤 Requirements Interview
|
|
185
200
|
|
|
186
|
-
2
|
|
187
|
-
- `interview` -
|
|
188
|
-
- `ask_user` - AI
|
|
201
|
+
2 interview tools to clarify requirements before development:
|
|
202
|
+
- `interview` - Structured requirements interview
|
|
203
|
+
- `ask_user` - AI proactive questioning
|
|
189
204
|
|
|
190
205
|
---
|
|
191
206
|
|
|
192
|
-
## 🧭
|
|
207
|
+
## 🧭 Tool Selection Guide
|
|
193
208
|
|
|
194
|
-
###
|
|
209
|
+
### When to use orchestration tools vs individual tools?
|
|
195
210
|
|
|
196
|
-
|
|
197
|
-
- ✅
|
|
198
|
-
- ✅
|
|
199
|
-
- ✅
|
|
211
|
+
**Use orchestration tools (start_*) when:**
|
|
212
|
+
- ✅ Need complete workflow (multiple steps)
|
|
213
|
+
- ✅ Want to automate multiple tasks
|
|
214
|
+
- ✅ Need to generate multiple artifacts (docs, code, tests, etc.)
|
|
200
215
|
|
|
201
|
-
|
|
202
|
-
- ✅
|
|
203
|
-
- ✅
|
|
204
|
-
- ✅
|
|
216
|
+
**Use individual tools when:**
|
|
217
|
+
- ✅ Only need specific functionality
|
|
218
|
+
- ✅ Already have project context docs
|
|
219
|
+
- ✅ Need more fine-grained control
|
|
205
220
|
|
|
206
|
-
###
|
|
221
|
+
### Common Scenario Selection
|
|
207
222
|
|
|
208
|
-
|
|
|
209
|
-
|
|
210
|
-
|
|
|
211
|
-
|
|
|
212
|
-
|
|
|
213
|
-
|
|
|
214
|
-
|
|
|
215
|
-
|
|
|
216
|
-
|
|
|
217
|
-
|
|
|
218
|
-
|
|
|
223
|
+
| Scenario | Recommended Tool | Reason |
|
|
224
|
+
|---------|-----------------|--------|
|
|
225
|
+
| Develop new feature (complete flow) | `start_feature` | Auto-complete: spec→estimation |
|
|
226
|
+
| Only need feature spec docs | `add_feature` | More lightweight, only generates docs |
|
|
227
|
+
| Fix bug (complete flow) | `start_bugfix` | Auto-complete: analysis→fix→test |
|
|
228
|
+
| Only need bug analysis | `fix_bug` | Faster, only analyzes problem |
|
|
229
|
+
| Generate design system | `ui_design_system` | Directly generate design specs |
|
|
230
|
+
| Develop UI components | `start_ui` | Complete flow: design→components→code |
|
|
231
|
+
| Product design (requirements to prototype) | `start_product` | One-click: PRD→prototype→HTML |
|
|
232
|
+
| One-sentence requirement analysis | `init_project` | Generate complete project spec docs |
|
|
233
|
+
| Project onboarding docs | `init_project_context` | Generate tech stack/architecture/conventions |
|
|
219
234
|
|
|
220
235
|
---
|
|
221
236
|
|
|
222
|
-
## 🚀
|
|
237
|
+
## 🚀 Quick Start
|
|
223
238
|
|
|
224
|
-
###
|
|
239
|
+
### Method 1: Use directly with npx (Recommended)
|
|
225
240
|
|
|
226
|
-
|
|
241
|
+
No installation needed, use the latest version directly.
|
|
227
242
|
|
|
228
|
-
#### Cursor / Cline
|
|
243
|
+
#### Cursor / Cline Configuration
|
|
229
244
|
|
|
230
|
-
|
|
245
|
+
**Config file location:**
|
|
231
246
|
- Windows: `%APPDATA%\Cursor\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json`
|
|
232
247
|
- macOS: `~/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
|
|
233
248
|
- Linux: `~/.config/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
|
|
234
249
|
|
|
235
|
-
|
|
250
|
+
**Config content:**
|
|
236
251
|
```json
|
|
237
252
|
{
|
|
238
253
|
"mcpServers": {
|
|
@@ -244,14 +259,14 @@ AI 需要**按步骤调用工具并落盘文件**,而不是由工具内部直
|
|
|
244
259
|
}
|
|
245
260
|
```
|
|
246
261
|
|
|
247
|
-
#### Claude Desktop
|
|
262
|
+
#### Claude Desktop Configuration
|
|
248
263
|
|
|
249
|
-
|
|
264
|
+
**Config file location:**
|
|
250
265
|
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
|
|
251
266
|
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
|
|
252
267
|
- Linux: `~/.config/Claude/claude_desktop_config.json`
|
|
253
268
|
|
|
254
|
-
|
|
269
|
+
**Config content:**
|
|
255
270
|
```json
|
|
256
271
|
{
|
|
257
272
|
"mcpServers": {
|
|
@@ -263,13 +278,13 @@ AI 需要**按步骤调用工具并落盘文件**,而不是由工具内部直
|
|
|
263
278
|
}
|
|
264
279
|
```
|
|
265
280
|
|
|
266
|
-
###
|
|
281
|
+
### Method 2: Global Installation
|
|
267
282
|
|
|
268
283
|
```bash
|
|
269
284
|
npm install -g mcp-probe-kit
|
|
270
285
|
```
|
|
271
286
|
|
|
272
|
-
|
|
287
|
+
Use in config file:
|
|
273
288
|
```json
|
|
274
289
|
{
|
|
275
290
|
"mcpServers": {
|
|
@@ -280,80 +295,81 @@ npm install -g mcp-probe-kit
|
|
|
280
295
|
}
|
|
281
296
|
```
|
|
282
297
|
|
|
283
|
-
###
|
|
298
|
+
### Restart Client
|
|
284
299
|
|
|
285
|
-
|
|
300
|
+
After configuration, **completely quit and reopen** your MCP client.
|
|
286
301
|
|
|
287
|
-
**👉 [
|
|
302
|
+
**👉 [Detailed Installation Guide](https://mcp-probe-kit.bytezonex.com/pages/getting-started.html)**
|
|
288
303
|
|
|
289
304
|
---
|
|
290
305
|
|
|
291
|
-
## 💡
|
|
306
|
+
## 💡 Usage Examples
|
|
292
307
|
|
|
293
|
-
###
|
|
308
|
+
### Daily Development
|
|
294
309
|
```bash
|
|
295
|
-
code_review @feature.ts #
|
|
296
|
-
gentest @feature.ts #
|
|
297
|
-
gencommit #
|
|
310
|
+
code_review @feature.ts # Code review
|
|
311
|
+
gentest @feature.ts # Generate tests
|
|
312
|
+
gencommit # Generate commit message
|
|
298
313
|
```
|
|
299
314
|
|
|
300
|
-
###
|
|
315
|
+
### New Feature Development
|
|
301
316
|
```bash
|
|
302
|
-
start_feature user-auth "
|
|
303
|
-
#
|
|
317
|
+
start_feature user-auth "User authentication feature"
|
|
318
|
+
# Auto-complete: Requirements analysis → Design → Effort estimation
|
|
304
319
|
```
|
|
305
320
|
|
|
306
|
-
### Bug
|
|
321
|
+
### Bug Fixing
|
|
307
322
|
```bash
|
|
308
323
|
start_bugfix
|
|
309
|
-
#
|
|
310
|
-
#
|
|
324
|
+
# Then paste error message
|
|
325
|
+
# Auto-complete: Problem location → Fix solution → Test code
|
|
311
326
|
```
|
|
312
327
|
|
|
313
|
-
###
|
|
328
|
+
### Product Design
|
|
314
329
|
```bash
|
|
315
|
-
start_product "
|
|
316
|
-
#
|
|
330
|
+
start_product "Online Education Platform" --product_type=SaaS
|
|
331
|
+
# Auto-complete: PRD → Prototype → Design system → HTML prototype
|
|
317
332
|
```
|
|
318
333
|
|
|
319
|
-
### UI
|
|
334
|
+
### UI Development
|
|
320
335
|
```bash
|
|
321
|
-
start_ui "
|
|
322
|
-
#
|
|
336
|
+
start_ui "Login Page" --mode=auto
|
|
337
|
+
# Auto-complete: Design system → Component generation → Code output
|
|
323
338
|
```
|
|
324
339
|
|
|
325
|
-
###
|
|
340
|
+
### Project Context Documentation
|
|
326
341
|
```bash
|
|
327
|
-
#
|
|
342
|
+
# Single file mode (default) - Generate a complete project-context.md
|
|
328
343
|
init_project_context
|
|
329
344
|
|
|
330
|
-
#
|
|
345
|
+
# Modular mode - Generate 6 category docs (suitable for large projects)
|
|
331
346
|
init_project_context --mode=modular
|
|
332
|
-
#
|
|
347
|
+
# Generates: project-context.md (index) + 5 category docs
|
|
333
348
|
```
|
|
334
349
|
|
|
335
|
-
### Git
|
|
350
|
+
### Git Work Report
|
|
336
351
|
```bash
|
|
337
|
-
#
|
|
338
|
-
git_work_report --date 2026-
|
|
352
|
+
# Generate daily report
|
|
353
|
+
git_work_report --date 2026-02-03
|
|
339
354
|
|
|
340
|
-
#
|
|
341
|
-
git_work_report --start_date 2026-
|
|
355
|
+
# Generate weekly report
|
|
356
|
+
git_work_report --start_date 2026-02-01 --end_date 2026-02-07
|
|
342
357
|
|
|
343
|
-
#
|
|
344
|
-
git_work_report --date 2026-
|
|
345
|
-
#
|
|
358
|
+
# Save to file
|
|
359
|
+
git_work_report --date 2026-02-03 --output_file daily-report.md
|
|
360
|
+
# Auto-analyze Git diff, generate concise professional report
|
|
361
|
+
# If direct command fails, auto-provides temp script solution (auto-deletes after execution)
|
|
346
362
|
```
|
|
347
363
|
|
|
348
|
-
**👉 [
|
|
364
|
+
**👉 [More Usage Examples](https://mcp-probe-kit.bytezonex.com/pages/examples.html)**
|
|
349
365
|
|
|
350
366
|
---
|
|
351
367
|
|
|
352
|
-
## ❓
|
|
368
|
+
## ❓ FAQ
|
|
353
369
|
|
|
354
|
-
### Q1:
|
|
370
|
+
### Q1: Tool not working or errors?
|
|
355
371
|
|
|
356
|
-
|
|
372
|
+
Check detailed logs:
|
|
357
373
|
|
|
358
374
|
**Windows (PowerShell):**
|
|
359
375
|
```powershell
|
|
@@ -365,36 +381,36 @@ npx -y mcp-probe-kit@latest 2>&1 | Tee-Object -FilePath .\mcp-probe-kit.log
|
|
|
365
381
|
npx -y mcp-probe-kit@latest 2>&1 | tee ./mcp-probe-kit.log
|
|
366
382
|
```
|
|
367
383
|
|
|
368
|
-
### Q2:
|
|
384
|
+
### Q2: Client not recognizing tools after configuration?
|
|
369
385
|
|
|
370
|
-
1.
|
|
371
|
-
2.
|
|
372
|
-
3.
|
|
373
|
-
4.
|
|
386
|
+
1. **Restart client** (completely quit then reopen)
|
|
387
|
+
2. Check config file path is correct
|
|
388
|
+
3. Confirm JSON format is correct, no syntax errors
|
|
389
|
+
4. Check client developer tools or logs for error messages
|
|
374
390
|
|
|
375
|
-
### Q3:
|
|
391
|
+
### Q3: How to update to latest version?
|
|
376
392
|
|
|
377
|
-
**npx
|
|
378
|
-
|
|
393
|
+
**npx method (Recommended):**
|
|
394
|
+
Use `@latest` tag in config, automatically uses latest version.
|
|
379
395
|
|
|
380
|
-
|
|
396
|
+
**Global installation method:**
|
|
381
397
|
```bash
|
|
382
398
|
npm update -g mcp-probe-kit
|
|
383
399
|
```
|
|
384
400
|
|
|
385
|
-
**👉 [
|
|
401
|
+
**👉 [More FAQ](https://mcp-probe-kit.bytezonex.com/pages/getting-started.html)**
|
|
386
402
|
|
|
387
403
|
---
|
|
388
404
|
|
|
389
|
-
## 🤝
|
|
405
|
+
## 🤝 Contributing
|
|
390
406
|
|
|
391
|
-
|
|
407
|
+
Issues and Pull Requests welcome!
|
|
392
408
|
|
|
393
|
-
|
|
394
|
-
-
|
|
395
|
-
-
|
|
396
|
-
-
|
|
397
|
-
-
|
|
409
|
+
**Improvement suggestions:**
|
|
410
|
+
- Add useful tools
|
|
411
|
+
- Optimize existing tool prompts
|
|
412
|
+
- Improve documentation and examples
|
|
413
|
+
- Fix bugs
|
|
398
414
|
|
|
399
415
|
---
|
|
400
416
|
|
|
@@ -404,19 +420,19 @@ MIT License
|
|
|
404
420
|
|
|
405
421
|
---
|
|
406
422
|
|
|
407
|
-
## 🔗
|
|
423
|
+
## 🔗 Related Links
|
|
408
424
|
|
|
409
|
-
-
|
|
425
|
+
- **Author**: [Kyle (小墨)](https://www.bytezonex.com/)
|
|
410
426
|
- **GitHub**: [mcp-probe-kit](https://github.com/mybolide/mcp-probe-kit)
|
|
411
427
|
- **npm**: [mcp-probe-kit](https://www.npmjs.com/package/mcp-probe-kit)
|
|
412
|
-
-
|
|
413
|
-
|
|
414
|
-
|
|
415
|
-
- [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) - MCP
|
|
416
|
-
- [GitHub Spec-Kit](https://github.com/github/spec-kit) - GitHub
|
|
417
|
-
- [ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) - UI/UX
|
|
418
|
-
- [json-render](https://github.com/vercel-labs/json-render) - JSON
|
|
419
|
-
- [uipro-cli](https://www.npmjs.com/package/uipro-cli) - UI/UX
|
|
428
|
+
- **Documentation**: [https://mcp-probe-kit.bytezonex.com](https://mcp-probe-kit.bytezonex.com/)
|
|
429
|
+
|
|
430
|
+
**Related Projects:**
|
|
431
|
+
- [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) - Official MCP protocol docs
|
|
432
|
+
- [GitHub Spec-Kit](https://github.com/github/spec-kit) - GitHub spec-driven development toolkit
|
|
433
|
+
- [ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) - UI/UX design system philosophy source
|
|
434
|
+
- [json-render](https://github.com/vercel-labs/json-render) - JSON template rendering engine inspiration
|
|
435
|
+
- [uipro-cli](https://www.npmjs.com/package/uipro-cli) - UI/UX data source
|
|
420
436
|
|
|
421
437
|
---
|
|
422
438
|
|