Search Capabilities Guide

Query: "How do I implement OAuth authentication?"
🔍 Search Intelligence:
- Understands this is a technical implementation question
- Prioritizes code examples and implementation guides
- Includes configuration and testing information

Results:
1. [Implementation Guide] OAuth 2.0 Setup with Step-by-Step Code
2. [Security Best Practices] OAuth Security Considerations  
3. [Code Examples] OAuth Implementation in Node.js/Python
4. [Configuration] OAuth Service Configuration

Query: "What are our deployment approval procedures?"
🔍 Search Intelligence:
- Recognizes this as a process/policy question
- Focuses on procedure documentation and workflows
- Includes governance and compliance information

Results:
1. [Policy Document] Deployment Approval Workflow
2. [Procedures] Production Deployment Checklist
3. [Governance] Change Management Requirements
4. [Compliance] Security Review Process

Query: "Users getting timeout errors on login"
🔍 Search Intelligence:
- Identifies this as a troubleshooting scenario
- Prioritizes error resolution and diagnostic content
- Includes monitoring and performance information

Results:
1. [Troubleshooting] Login Timeout Error Solutions
2. [Monitoring] Authentication Performance Metrics
3. [Diagnostics] Database Connection Issues
4. [Resolution] Quick Fix for Common Login Problems

{
  "name": "search",
  "parameters": {
    "query": "string",              // Natural language query - be conversational!
    "limit": 10,                    // Results to return (default: 5)
    "source_types": ["git", "confluence", "jira", "documentation", "localfile"],
    "project_ids": ["project1", "project2"]
  }
}

Query: "Show me the structure of our API documentation"
Hierarchy Analysis:
📁 API Documentation (Root)
├── 📄 Getting Started (3 children)
├── 📁 Authentication (5 children)
│   ├── 📄 JWT Implementation
│   ├── 📄 OAuth Setup
│   └── 📄 API Keys
├── 📁 Endpoints (8 children)
│   ├── 📁 User Management
│   └── 📁 Data Operations
└── 📁 Examples (4 children)

💡 Completeness Score: 85% - Missing error handling section

Query: "Where should I add webhook security documentation?"
Hierarchy Suggestions:
1. **Primary Location**: API Documentation > Security > Webhooks
   - Path: Consistent with existing security structure
   - Related: Authentication, Authorization content

2. **Alternative**: API Documentation > Webhooks > Security
   - Path: Groups all webhook content together
   - Context: If you have a dedicated Webhooks section

Recommendation: Create under Security section for consistency

{
  "name": "hierarchy_search",
  "parameters": {
    "query": "string",              // Search query
    "limit": 10,                    // Number of results (default: 10)
    "organize_by_hierarchy": false, // Group results by structure
    "hierarchy_filter": {           // Hierarchy-specific filters
      "depth": 3,                   // Filter by hierarchy depth
      "has_children": true,         // Filter by whether pages have children
      "parent_title": "API Documentation", // Filter by parent page
      "root_only": false            // Show only root pages
    }
  }
}

Query: "architecture diagrams with security components"
Content Analysis Results:

1. 📄 system-architecture-v3.pdf (2.3 MB)
   🧠 Content Analysis: "API gateway, authentication services, encrypted databases"
   🏗️ Components: Security controls, data encryption, access management
   📊 Security Coverage: 85% - Comprehensive security architecture

2. 🖼️ security-flow-diagram.png (1.1 MB)  
   🧠 OCR Analysis: "User authentication flow with multi-factor authentication"
   🏗️ Components: MFA, token validation, secure sessions
   📊 Security Coverage: 92% - Detailed security implementation

Query: "deployment configuration scripts"
Content Analysis Results:

1. 📋 deploy-production.yml (45 KB)
   📁 Parent: Deployment Documentation
   🧠 Content: "Production deployment configuration with security settings"
   ⚠️ Risk Assessment: Medium - contains sensitive configuration

2. 🔧 setup-environment.sh (12 KB)
   📁 Parent: Environment Setup Guide
   🧠 Content: "Environment initialization and dependency installation"
   ✅ Risk Assessment: Low - standard setup procedures

{
  "name": "attachment_search",
  "parameters": {
    "query": "string",              // Search query
    "limit": 10,                    // Number of results
    "include_parent_context": true, // Include parent document info
    "attachment_filter": {          // Attachment-specific filters
      "file_type": "pdf",           // Filter by file type
      "file_size_min": 1024,        // Minimum file size in bytes
      "file_size_max": 10485760,    // Maximum file size in bytes
      "attachments_only": true,     // Show only attachments
      "author": "john.doe",         // Filter by author
      "parent_document_title": "API Documentation"
    }
  }
}

{
  "name": "analyze_document_relationships",
  "parameters": {
    "query": "search query to get documents for analysis",
    "limit": 15,                    // Maximum documents to analyze
    "source_types": ["confluence", "git"],
    "project_ids": ["project1"]
  }
}

Query: "API authentication documentation"
Relationship Analysis:

📊 Document Network Analysis:
├── Central Documents: 3 high-connectivity hubs
├── Related Clusters: 4 topic-based groups
├── Cross-References: 12 external links
└── Dependency Chain: 5-level hierarchy

🔗 Key Relationships Discovered:
1. Authentication Guide → Implementation Examples (implements)
2. Security Policy → Authentication Requirements (defines)
3. API Reference → Authentication Endpoints (documents)
4. Troubleshooting → Common Auth Issues (resolves)

💡 Insights:
- Strong documentation coverage for authentication
- Clear implementation pathway from theory to practice
- Good troubleshooting support available

{
  "name": "find_similar_documents",
  "parameters": {
    "target_query": "target document to find similarities for",
    "comparison_query": "documents to compare against",
    "similarity_metrics": ["entity_overlap", "semantic_similarity"],
    "max_similar": 5
  }
}

Target: "API Rate Limiting Guide"
Similar Documents Found:

1. "Rate Limiting Implementation" (Similarity: 0.92)
   📊 Overlap: Same concepts, different implementation approach
   🔄 Relationship: Alternative implementation strategy

2. "API Throttling Configuration" (Similarity: 0.87)
   📊 Overlap: Similar technical solution, different focus
   🔄 Relationship: Configuration vs. implementation guide

3. "API Performance Optimization" (Similarity: 0.75)
   📊 Overlap: Rate limiting as part of broader strategy
   🔄 Relationship: Specific technique within broader approach

{
  "name": "detect_document_conflicts",
  "parameters": {
    "query": "search query to get documents for conflict analysis",
    "limit": 15,
    "source_types": ["confluence", "git"],
    "project_ids": ["project1"]
  }
}

Query: "API authentication policies"
Conflicts Detected:

🚨 Conflict 1: Authentication Token Expiration
├── Document A: "API Security Guidelines" → 1 hour expiration
├── Document B: "Mobile App Configuration" → 24 hour expiration
└── 💡 Suggestion: Standardize token expiration policies

🚨 Conflict 2: Rate Limiting Configuration
├── Document A: "Production Setup Guide" → 100 requests/minute
├── Document B: "API Documentation" → 500 requests/minute  
└── 💡 Suggestion: Update documentation to match production

📋 Resolution Recommendations:
1. Create unified authentication policy document
2. Establish single source of truth for configuration values
3. Add cross-references between related documents

{
  "name": "find_complementary_content",
  "parameters": {
    "target_query": "target document to analyze",
    "context_query": "context for finding complements",
    "max_recommendations": 5,
    "source_types": ["confluence", "git"],
    "project_ids": ["project1"]
  }
}

Target Document: "User Authentication API Specification"
Complementary Content Found:

1. Implementation Guide (Relevance: 0.89)
   📋 Reason: Provides implementation details for the API specification
   🎯 Strategy: Requirements → Implementation relationship

2. Security Testing Procedures (Relevance: 0.85)
   📋 Reason: Covers security validation for authentication systems
   🎯 Strategy: Specification → Validation relationship

3. Authentication Troubleshooting Guide (Relevance: 0.82)
   📋 Reason: Addresses common issues with authentication
   🎯 Strategy: Implementation → Support relationship

4. User Database Schema (Relevance: 0.78)
   📋 Reason: Defines data structure supporting authentication
   🎯 Strategy: API → Data Model relationship

{
  "name": "cluster_documents",
  "parameters": {
    "query": "search query to get documents for clustering",
    "strategy": "mixed_features",  // clustering strategy
    "max_clusters": 10,
    "min_cluster_size": 2,
    "limit": 25,
    "source_types": ["confluence"],
    "project_ids": ["project1"]
  }
}

Query: "API documentation"
Document Clusters Created:

📊 Cluster 1: Authentication & Security (5 documents)
├── Coherence Score: 0.91
├── Shared Topics: authentication, security, tokens
└── Documents: JWT Guide, OAuth Setup, Security Policy, etc.

📊 Cluster 2: API Implementation (7 documents)  
├── Coherence Score: 0.87
├── Shared Topics: endpoints, implementation, code
└── Documents: API Reference, Code Examples, Integration Guide, etc.

📊 Cluster 3: Troubleshooting & Support (4 documents)
├── Coherence Score: 0.83
├── Shared Topics: errors, debugging, troubleshooting
└── Documents: Error Guide, FAQ, Common Issues, etc.

💡 Insights:
- Well-organized documentation with clear topic separation
- Strong coherence within each cluster
- Good coverage across implementation lifecycle

1. Semantic Search: "user authentication implementation"
   → Understand current authentication approach

2. Hierarchy Search: "authentication system structure"  
   → Explore documentation organization

3. Cross-Document Analysis: Find relationships for "authentication API guide"
   → Get implementation guides, testing procedures, troubleshooting

4. Conflict Detection: "authentication policies"
   → Identify inconsistencies across documents

Result: Complete understanding with identified gaps and conflicts

1. Hierarchy Search: "API documentation structure analysis"
   → Understand current organization and find gaps

2. Conflict Detection: "API versioning policies"
   → Identify inconsistencies across documents

3. Similarity Detection: Find similar documents to "API guide"
   → Review for potential duplication

4. Complementary Content: Find complements to "API reference"
   → Discover missing supporting documentation

Result: Comprehensive audit with actionable improvement plan

# Quick answers
limit: 3-5           # Fast, focused results

# Comprehensive search
limit: 10-15         # Good coverage (recommended)

# Analysis operations
limit: 20-30         # For cross-document intelligence

# Search specific sources
source_types: ["git"]           # Only Git repositories
source_types: ["confluence"]    # Only Confluence pages
source_types: ["jira"]          # Only JIRA issues
source_types: ["localfile"]     # Only local files

# Cross-document analysis
source_types: ["confluence", "git"]  # Documentation and code

# Required Configuration
QDRANT_URL=http://localhost:6333
OPENAI_API_KEY=your-openai-api-key

# Optional Configuration
QDRANT_COLLECTION_NAME=documents        # Default: "documents"
QDRANT_API_KEY=your-qdrant-cloud-key   # For QDrant Cloud
MCP_DISABLE_CONSOLE_LOGGING=true       # Recommended for development tools