rrce-workflow 0.2.21 → 0.2.23
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 +144 -0
- package/dist/index.js +1103 -259
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -164,6 +164,141 @@ storage:
|
|
|
164
164
|
|
|
165
165
|
---
|
|
166
166
|
|
|
167
|
+
## MCP Hub (Cross-Project AI Access)
|
|
168
|
+
|
|
169
|
+
RRCE-Workflow includes an **MCP (Model Context Protocol) Hub** that exposes your project knowledge to AI assistants like **VSCode Copilot** and **Claude Desktop**.
|
|
170
|
+
|
|
171
|
+
### Quick Start
|
|
172
|
+
|
|
173
|
+
```bash
|
|
174
|
+
# Start the MCP Hub
|
|
175
|
+
npx rrce-workflow mcp
|
|
176
|
+
|
|
177
|
+
# Or run directly
|
|
178
|
+
npx rrce-workflow mcp start
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### MCP Features
|
|
182
|
+
|
|
183
|
+
| Feature | Description |
|
|
184
|
+
|---------|-------------|
|
|
185
|
+
| **Cross-project knowledge** | AI can access context from multiple projects simultaneously |
|
|
186
|
+
| **Agent prompts** | All 6 agents (init, research, plan, execute, docs, sync) exposed as MCP prompts |
|
|
187
|
+
| **Search across projects** | Search knowledge bases across all exposed projects |
|
|
188
|
+
| **Selective exposure** | Choose which projects to expose via interactive TUI |
|
|
189
|
+
|
|
190
|
+
### VSCode Copilot Setup
|
|
191
|
+
|
|
192
|
+
1. Create `.vscode/mcp.json` in your workspace:
|
|
193
|
+
|
|
194
|
+
```json
|
|
195
|
+
{
|
|
196
|
+
"servers": {
|
|
197
|
+
"rrce": {
|
|
198
|
+
"type": "stdio",
|
|
199
|
+
"command": "npx",
|
|
200
|
+
"args": ["rrce-workflow", "mcp", "start"]
|
|
201
|
+
}
|
|
202
|
+
}
|
|
203
|
+
}
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
2. In Copilot Chat, switch to **Agent** mode
|
|
207
|
+
3. Click the 🔧 tools icon to see RRCE resources, tools, and prompts
|
|
208
|
+
|
|
209
|
+
### Claude Desktop Setup
|
|
210
|
+
|
|
211
|
+
Add to `~/.config/claude/claude_desktop_config.json`:
|
|
212
|
+
|
|
213
|
+
```json
|
|
214
|
+
{
|
|
215
|
+
"mcpServers": {
|
|
216
|
+
"rrce": {
|
|
217
|
+
"command": "npx",
|
|
218
|
+
"args": ["rrce-workflow", "mcp", "start"]
|
|
219
|
+
}
|
|
220
|
+
}
|
|
221
|
+
}
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
### MCP Resources & Tools
|
|
225
|
+
|
|
226
|
+
**Resources:**
|
|
227
|
+
- `rrce://projects` — List all exposed projects
|
|
228
|
+
- `rrce://projects/{name}/context` — Get project context
|
|
229
|
+
- `rrce://projects/{name}/tasks` — Get task list
|
|
230
|
+
|
|
231
|
+
**Tools:**
|
|
232
|
+
- `search_knowledge` — Search across all project knowledge bases
|
|
233
|
+
- `list_projects` — List exposed projects
|
|
234
|
+
- `get_project_context` — Get specific project context
|
|
235
|
+
|
|
236
|
+
**Prompts:**
|
|
237
|
+
- `init`, `research`, `plan`, `execute`, `docs`, `sync` — Full RRCE pipeline
|
|
238
|
+
|
|
239
|
+
### Using Agent Prompts via MCP
|
|
240
|
+
|
|
241
|
+
Once the MCP server is connected, you can invoke RRCE agent prompts directly:
|
|
242
|
+
|
|
243
|
+
#### In VSCode Copilot (Agent Mode)
|
|
244
|
+
|
|
245
|
+
```
|
|
246
|
+
# Initialize project context
|
|
247
|
+
@rrce Use the init prompt to analyze this codebase
|
|
248
|
+
|
|
249
|
+
# Start a new task
|
|
250
|
+
@rrce Use the research prompt with REQUEST="add user authentication" and TASK_SLUG="auth-feature"
|
|
251
|
+
|
|
252
|
+
# Create execution plan
|
|
253
|
+
@rrce Use the plan prompt for TASK_SLUG="auth-feature"
|
|
254
|
+
|
|
255
|
+
# Execute the plan
|
|
256
|
+
@rrce Use the execute prompt for TASK_SLUG="auth-feature"
|
|
257
|
+
```
|
|
258
|
+
|
|
259
|
+
#### In Claude Desktop
|
|
260
|
+
|
|
261
|
+
```
|
|
262
|
+
Use the RRCE init prompt to analyze the current project
|
|
263
|
+
|
|
264
|
+
Search my RRCE projects for "authentication"
|
|
265
|
+
|
|
266
|
+
Use the research prompt with these arguments:
|
|
267
|
+
- REQUEST: "Add OAuth2 login"
|
|
268
|
+
- TASK_SLUG: "oauth-login"
|
|
269
|
+
```
|
|
270
|
+
|
|
271
|
+
#### In Other MCP-Compatible Tools (Cursor, etc.)
|
|
272
|
+
|
|
273
|
+
Most MCP clients follow similar patterns:
|
|
274
|
+
1. Connect to the RRCE MCP server via stdio
|
|
275
|
+
2. Use `list_prompts` to see available prompts
|
|
276
|
+
3. Call prompts with required arguments
|
|
277
|
+
|
|
278
|
+
**Example prompt arguments:**
|
|
279
|
+
|
|
280
|
+
| Prompt | Required Args | Optional Args |
|
|
281
|
+
|--------|---------------|---------------|
|
|
282
|
+
| `init` | — | `PROJECT_NAME` |
|
|
283
|
+
| `research` | `REQUEST`, `TASK_SLUG` | `TITLE` |
|
|
284
|
+
| `plan` | `TASK_SLUG` | — |
|
|
285
|
+
| `execute` | `TASK_SLUG` | `BRANCH` |
|
|
286
|
+
| `docs` | `DOC_TYPE` | `TASK_SLUG` |
|
|
287
|
+
| `sync` | — | `SCOPE` |
|
|
288
|
+
|
|
289
|
+
### MCP Configuration
|
|
290
|
+
|
|
291
|
+
Configure which projects to expose:
|
|
292
|
+
|
|
293
|
+
```bash
|
|
294
|
+
npx rrce-workflow mcp # Interactive TUI
|
|
295
|
+
npx rrce-workflow mcp status # View current status
|
|
296
|
+
```
|
|
297
|
+
|
|
298
|
+
Config stored at `~/.rrce-workflow/mcp.yaml`
|
|
299
|
+
|
|
300
|
+
---
|
|
301
|
+
|
|
167
302
|
## Requirements
|
|
168
303
|
|
|
169
304
|
- **Node.js 18+**
|
|
@@ -193,6 +328,15 @@ npx rrce-workflow
|
|
|
193
328
|
# Select "Update from package"
|
|
194
329
|
```
|
|
195
330
|
|
|
331
|
+
### MCP server not connecting
|
|
332
|
+
|
|
333
|
+
Ensure the server starts successfully:
|
|
334
|
+
```bash
|
|
335
|
+
npx rrce-workflow mcp start
|
|
336
|
+
```
|
|
337
|
+
|
|
338
|
+
Check that your IDE is configured to use stdio transport.
|
|
339
|
+
|
|
196
340
|
---
|
|
197
341
|
|
|
198
342
|
## License
|