Purpose: This document tracks the deployment and maintenance of the MCP Local RAG standard across repositories.
| Repository | Bootstrap Date | Last Updated | Status | Notes |
|---|---|---|---|---|
| finix-docs-redocly | 2026-02-02 | 2026-02-02 | Active | Documentation source repo |
Status Key:
- Active: Fully configured and in use
- In Progress: Being set up
- Outdated: Needs update from canonical source
- Deprecated: No longer maintained
All repositories using MCP Local RAG should have these files:
MCP_STANDARD_RULES.md
- Universal MCP workflow documentation
- Referenced by all context files
- Should be identical across all repos
ROOT_CONTEXT_TEMPLATE.md
- Template for repository root CLAUDE_CONTEXT.md
- Contains bootstrap instructions
- Generic with auto-detection logic
CLAUDE_CONTEXT_TEMPLATE.md
- Template for module-specific contexts
- Auto-detection instructions
- Generic across all codebases
setup.sh
- Generic MCP Local RAG setup script
- Installs Node.js, mcp-local-rag
- Configures ~/.claude.json
ingest-docs.sh
- Helper for generating ingestion commands
- Generic across all repos
BOOTSTRAP_EXAMPLE.md
- Shows complete bootstrap process
- Useful for onboarding
- Generic example
MCP_MAINTENANCE.md (this file)
- Tracks standard deployment
- Update propagation workflow
- Can be customized per organization
When standards are updated in your canonical source repository:
cd canonical-source-repo/mcp-docs/claude-code
git log --since="YYYY-MM-DD" -- .Review what changed in:
- MCP_STANDARD_RULES.md
- Templates (ROOT_CONTEXT_TEMPLATE.md, CLAUDE_CONTEXT_TEMPLATE.md)
- Scripts (setup.sh, ingest-docs.sh)
Types of changes:
Critical (propagate immediately):
- MCP workflow changes
- Security fixes in setup scripts
- Breaking changes in templates
Enhancement (propagate when convenient):
- Documentation improvements
- New optional features
- Example updates
Repository-specific (do not propagate):
- Customizations in CLAUDE_CONTEXT.md files
- Repository-specific documentation
For each target repository:
# Option A: Copy updated files directly
cd target-repo
cp ~/canonical-source-repo/mcp-docs/claude-code/MCP_STANDARD_RULES.md \
mcp-docs/claude-code/MCP_STANDARD_RULES.md
# Option B: Use the bootstrap package
# (If major version update or full refresh needed)
cp ~/canonical-source-repo/MCP_BOOTSTRAP_PACKAGE.md .
# Then in Claude Code: "Please extract all files from MCP_BOOTSTRAP_PACKAGE.md"# Check file existence
ls -la mcp-docs/claude-code/
# Verify MCP configuration
cat ~/.claude.json | grep "local-rag"
# Test a documentation query
# (In Claude Code): "Query the documentation for [topic]"Update the "Repository Tracking" table above with:
- Last Updated date
- Status
- Any issues encountered
When adding MCP Local RAG to a new repository:
# Copy to new repo root
cp ~/canonical-source-repo/MCP_BOOTSTRAP_PACKAGE.md /path/to/new-repo/
cd /path/to/new-repo# Add your documentation files
mkdir -p mcp-docs
cp /path/to/docs/* mcp-docs/
# Supports: PDF, DOCX, TXT, Markdown, HTMLIn Claude Code:
Please bootstrap from MCP_BOOTSTRAP_PACKAGE.mdClaude will:
- Extract all 7 files
- Run setup.sh
- Auto-detect repository structure
- Create root CLAUDE_CONTEXT.md
- Create 3-5 module contexts
- Ingest documentation files
- Report completion
- Restart Claude Code
- Test documentation query
- Verify contexts are correct
- Update tracking table in this file
Per-Repository (in CLAUDE_CONTEXT.md files):
- Repository name and purpose
- Module structure
- Technology stack
- Documentation type ({{DOC_TYPE}})
- Specific documentation files
Per-Organization (in MCP_MAINTENANCE.md):
- Repository tracking table
- Organization-specific workflows
- Custom deployment procedures
Keep Generic (in templates and rules):
- MCP_STANDARD_RULES.md (universal workflow)
- ROOT_CONTEXT_TEMPLATE.md (auto-detection logic)
- CLAUDE_CONTEXT_TEMPLATE.md (module template)
- setup.sh (generic setup script)
- ingest-docs.sh (generic helper)
Reason: These files should remain identical across repos for consistent behavior.
The bootstrap system can auto-detect:
| Item | Detection Method | Confidence |
|---|---|---|
| Repository name | Working directory basename | 100% |
| Main modules | ls -la + heuristics | 95% |
| Programming language | Build files (build.gradle, package.json, etc.) | 95% |
| Build tool | Build files presence | 95% |
| Framework | Annotations, imports | 90% |
| Purpose | README.md extraction | 80% |
| Documentation type | File patterns, directory names | 70% |
| Package structure | find + directory analysis | 90% |
| Key classes | File listing + grep | 85% |
| Configuration | Config file detection | 90% |
Items that may need user input:
- Purpose (if no README)
- Documentation type (if ambiguous from filenames)
- Complex processing flows
- Non-standard build processes
Symptoms: "MCP server not found" error in Claude Code
Solution:
- Check
~/.claude.jsonhaslocal-ragconfiguration - Verify
mcp-local-ragis installed:npm list -g mcp-local-rag - Re-run setup:
cd mcp-docs && ./claude-code/setup.sh - Restart Claude Code
Symptoms: mcp__local-rag__query_documents returns empty results
Solution:
- Check if files are ingested:
mcp__local-rag__list_files - If not ingested, ingest files:
mcp__local-rag__ingest_file("/absolute/path/to/file.pdf") - Verify documentation files exist:
ls -la mcp-docs/ - Try alternate query phrasing
Symptoms: Claude creates contexts for wrong directories
Solution:
- Delete incorrect contexts
- Update exclusion list in ROOT_CONTEXT_TEMPLATE.md
- Re-run bootstrap
- Or manually specify modules: "Create context for api/ module only"
Symptoms: Final CLAUDE_CONTEXT.md contains {{PLACEHOLDER}} text
Solution:
- This indicates auto-detection failed
- Manually edit the file to fill in placeholders
- Report the detection failure for template improvement
| Version | Date | Changes | Repositories Updated |
|---|---|---|---|
| 1.0 | 2026-02-02 | Initial release | finix-docs-redocly |
For questions or issues with the MCP Local RAG standard:
- Documentation: See
MCP_STANDARD_RULES.md - Issues: Report via repository issues
- Updates: Pull from canonical source repository