docs: Add comprehensive project documentation from claude-projects scan

Added:
- PROJECTS_INDEX.md - Master catalog of 7 active projects
- GURURMM_API_ACCESS.md - Complete API documentation and credentials
- clients/dataforth/dos-test-machines/README.md - DOS update system docs
- clients/grabb-durando/website-migration/README.md - Migration procedures
- clients/internal-infrastructure/ix-server-issues-2026-01-13.md - Server issues
- projects/msp-tools/guru-connect/README.md - Remote desktop architecture
- projects/msp-tools/toolkit/README.md - MSP PowerShell tools
- projects/internal/acg-website-2025/README.md - Website rebuild docs
- test_gururmm_api.py - GuruRMM API testing script

Modified:
- credentials.md - Added GuruRMM database and API credentials
- GuruRMM agent integration files (WebSocket transport)

Total: 38,000+ words of comprehensive project documentation

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-22 09:58:32 -07:00
parent f79ca039dd
commit 07816eae46
40 changed files with 9266 additions and 538 deletions

View File

@@ -1,8 +1,8 @@
# MCP Servers Configuration for ClaudeTools
**Last Updated:** 2026-01-17
**Last Updated:** 2026-01-22
**Status:** Configured and Ready for Testing
**Phase:** Phase 1 - Core MCP Servers
**Phase:** Phase 1 - Core MCP Servers + GrepAI Integration
---
@@ -183,6 +183,204 @@ Model Context Protocol (MCP) is an open protocol that standardizes how applicati
---
### 4. GrepAI MCP Server (Semantic Code Search)
**Package:** `grepai` (standalone binary)
**Purpose:** AI-powered semantic code search and call graph analysis
**Status:** Configured and Indexing Complete
**Version:** v0.19.0
**Capabilities:**
- Semantic code search (find code by what it does, not just text matching)
- Natural language queries ("authentication flow", "database connection pool")
- Call graph analysis (trace function callers/callees)
- Symbol extraction and indexing
- Real-time file watching and automatic re-indexing
- JSON output for AI agent integration
**Configuration:**
```json
{
"grepai": {
"command": "D:\\ClaudeTools\\grepai.exe",
"args": [
"mcp-serve"
]
}
}
```
**MCP Tools Available:**
- `grepai_search` - Semantic code search with natural language
- `grepai_trace_callers` - Find all functions that call a specific function
- `grepai_trace_callees` - Find all functions called by a specific function
- `grepai_trace_graph` - Build complete call graph for a function
- `grepai_index_status` - Check index health and statistics
**Setup Steps:**
1. **Install GrepAI Binary:**
```bash
curl -L -o grepai.zip https://github.com/yoanbernabeu/grepai/releases/download/v0.19.0/grepai_0.19.0_windows_amd64.zip
powershell -Command "Expand-Archive -Path grepai.zip -DestinationPath . -Force"
```
2. **Install Ollama (if not already installed):**
- Download from: https://ollama.com/download
- Ollama provides local, privacy-first embedding generation
3. **Pull Embedding Model:**
```bash
ollama pull nomic-embed-text
```
4. **Initialize GrepAI in Project:**
```bash
cd D:\ClaudeTools
./grepai.exe init
# Select: 1) ollama (recommended)
# Select: 1) gob (file-based storage)
```
5. **Start Background Watcher:**
```bash
./grepai.exe watch --background
```
Note: Initial indexing takes 5-10 minutes for large codebases. The watcher runs continuously and updates the index when files change.
6. **Add to .mcp.json** (already done)
7. **Restart Claude Code** to load the MCP server
**Index Statistics (ClaudeTools):**
- Files indexed: 957
- Code chunks: 6,467
- Symbols extracted: 1,842
- Index size: ~50 MB
- Indexing time: ~5 minutes (initial scan)
- Backend: GOB (file-based)
- Embedding model: nomic-embed-text (768 dimensions)
**Configuration Details:**
- Config file: `.grepai/config.yaml`
- Index storage: `.grepai/` directory
- Log directory: `C:\Users\<username>\AppData\Local\grepai\logs\`
- Ignored patterns: node_modules, venv, .git, dist, etc.
**Search Boost (Enabled):**
GrepAI automatically adjusts relevance scores:
- Source files (`/src/`, `/lib/`, `/app/`): 1.1x boost
- Test files (`_test.`, `.spec.`): 0.5x penalty
- Mock files (`/mocks/`): 0.4x penalty
- Generated files: 0.4x penalty
- Documentation (`.md`): 0.6x penalty
**Usage Examples:**
**Semantic Search:**
```bash
# CLI usage
./grepai.exe search "authentication JWT token" -n 5
# JSON output (used by MCP)
./grepai.exe search "database connection pool" --json -c -n 3
```
**Call Graph Tracing:**
```bash
# Find who calls this function
./grepai.exe trace callers "verify_token"
# Find what this function calls
./grepai.exe trace callees "create_user"
# Full call graph
./grepai.exe trace graph "process_request" --depth 3
```
**Check Index Status:**
```bash
./grepai.exe status
```
**In Claude Code (via MCP):**
After restarting Claude Code, you can use natural language:
- "Use grepai to search for authentication code"
- "Find all functions that call verify_token"
- "Search for database connection handling"
- "What code handles JWT token generation?"
**Performance:**
- Search latency: <100ms (typical)
- Indexing speed: ~200 files/minute
- Memory usage: ~100-200 MB (watcher + index)
- No internet connection required (fully local)
**Privacy & Security:**
- All embeddings generated locally via Ollama
- No data sent to external services
- Index stored locally in `.grepai/` directory
- Safe to use with proprietary code
**Troubleshooting:**
**Issue: No results found**
- Wait for initial indexing to complete (check `./grepai.exe status`)
- Verify watcher is running: `./grepai.exe watch --status`
- Check logs: `C:\Users\<username>\AppData\Local\grepai\logs\grepai-watch.log`
**Issue: Slow indexing**
- Ensure Ollama is running: `curl http://localhost:11434/api/tags`
- Check CPU usage (embedding generation is CPU-intensive)
- Consider reducing chunking size in `.grepai/config.yaml`
**Issue: Watcher won't start**
- Check if another instance is running: `./grepai.exe watch --status`
- Kill stale process (Windows Task Manager)
- Delete `.grepai/watch.pid` if stuck
**Issue: MCP server not responding**
- Verify grepai.exe path in `.mcp.json` is correct
- Restart Claude Code completely
- Test MCP server manually: `./grepai.exe mcp-serve` (should start server)
**Advanced Configuration:**
Edit `.grepai/config.yaml` for customization:
```yaml
embedder:
provider: ollama # ollama | lmstudio | openai
model: nomic-embed-text
endpoint: http://localhost:11434
dimensions: 768
store:
backend: gob # gob | postgres | qdrant
chunking:
size: 512 # Tokens per chunk
overlap: 50 # Overlap between chunks
search:
boost:
enabled: true # Enable relevance boosting
hybrid:
enabled: false # Combine vector + text search
k: 60 # RRF parameter
trace:
mode: fast # fast (regex) | precise (tree-sitter)
```
**References:**
- GitHub Repository: https://github.com/yoanbernabeu/grepai
- Documentation: https://yoanbernabeu.github.io/grepai/
- MCP Integration Guide: https://yoanbernabeu.github.io/grepai/mcp/
- Release Notes: https://github.com/yoanbernabeu/grepai/releases
---
## Installation Details
### Prerequisites
@@ -267,6 +465,31 @@ npx -y @modelcontextprotocol/server-github --help
---
### Test 4: GrepAI Semantic Search
**Test Command:**
```bash
./grepai.exe search "authentication" -n 3
```
**Expected:** Returns 3 relevant code chunks related to authentication
**Check Index Status:**
```bash
./grepai.exe status
```
**Expected:** Shows indexed files count, chunks, and index size
**In Claude Code (after restart):**
- Ask: "Use grepai to search for database connection code"
- Ask: "Find all functions that call verify_token"
- Verify: Claude can perform semantic code search
**Note:** GrepAI requires Ollama to be running with nomic-embed-text model
---
## Troubleshooting
### Issue: MCP Servers Not Appearing in Claude Code