Skip to content

Latest commit

 

History

History
432 lines (346 loc) · 12 KB

File metadata and controls

432 lines (346 loc) · 12 KB

Context7 MCP Guide for Android Documentation

Version: 2.0 - Unified Documentation System Last Updated: 2025-09-06 Purpose: Optimize Context7 usage for Android development documentation


🎯 Context7 Overview

Context7 MCP server provides access to up-to-date documentation and code examples for various programming languages and frameworks. For Android development, it's particularly valuable for accessing current API documentation, best practices, and implementation examples.

Current Usage Statistics

  • Current Usage: 2 tool uses (severely underutilized)
  • Target Usage: 15-20 tool uses per week
  • Primary Value: Android API documentation and examples

🔍 Context7 for Android Development

When to Use Context7

Primary Use Cases

  • Android API Documentation: Get current Android API documentation
  • Implementation Examples: Find code examples for Android patterns
  • Best Practices: Access current Android development best practices
  • Framework Integration: Documentation for Android libraries and frameworks
  • Migration Guidance: Modern Android development patterns

Research Integration

  • Use Context7 after Brave Search for implementation details
  • Combine with Brave Search for comprehensive research
  • Use for validation of research findings
  • Access up-to-date documentation for current Android versions

Android Libraries Available in Context7

Core Android Frameworks

// Android Core APIs
context7_get_docs({
  context7CompatibleLibraryID: "/android/core",
  topic: "modern Android development patterns"
})

// Jetpack Components
context7_get_docs({
  context7CompatibleLibraryID: "/android/jetpack",
  topic: "ViewModel and LiveData best practices"
})

// Material Design
context7_get_docs({
  context7CompatibleLibraryID: "/android/material",
  topic: "Material You implementation"
})

Development Tools

// Kotlin for Android
context7_get_docs({
  context7CompatibleLibraryID: "/android/kotlin",
  topic: "coroutines and flow patterns"
})

// Gradle Build System
context7_get_docs({
  context7CompatibleLibraryID: "/android/gradle",
  topic: "modern Gradle configuration"
})

// Testing Frameworks
context7_get_docs({
  context7CompatibleLibraryID: "/android/testing",
  topic: "unit testing best practices"
})

🛠️ Context7 Usage Patterns

Research Workflow Integration

Step 1: Initial Research (Brave Search)

// Start with broad research
brave_search({
  query: "Android ViewModel best practices 2024",
  summary: true
})

Step 2: Implementation Details (Context7)

// Get specific implementation guidance
context7_get_docs({
  context7CompatibleLibraryID: "/android/architecture",
  topic: "ViewModel lifecycle and state management",
  tokens: 15000
})

Step 3: Code Examples (Context7)

// Find practical examples
context7_get_docs({
  context7CompatibleLibraryID: "/android/kotlin",
  topic: "ViewModel with coroutines example",
  tokens: 10000
})

Kotlin Migration Support

Java to Kotlin Conversion

// Research Kotlin patterns
context7_get_docs({
  context7CompatibleLibraryID: "/android/kotlin",
  topic: "Java to Kotlin conversion patterns",
  tokens: 12000
})

// Modern Kotlin features
context7_get_docs({
  context7CompatibleLibraryID: "/android/kotlin",
  topic: "sealed classes and data classes",
  tokens: 10000
})

Android-Specific Kotlin

// Android Kotlin extensions
context7_get_docs({
  context7CompatibleLibraryID: "/android/ktx",
  topic: "KTX extensions usage",
  tokens: 8000
})

// Coroutines in Android
context7_get_docs({
  context7CompatibleLibraryID: "/android/coroutines",
  topic: "Android coroutine patterns",
  tokens: 15000
})

📊 Context7 Effectiveness Optimization

Usage Tracking and Metrics

Current Usage Analysis

  • Documentation Quality: Rate each query's usefulness (1-10)
  • Time Saved: Estimate time saved vs. manual research
  • Implementation Success: Track if Context7 guidance led to successful implementation
  • Query Success Rate: Percentage of useful results

Optimization Targets

  • Weekly Usage: Increase from 2 to 15-20 tool uses
  • Success Rate: Achieve 80%+ useful results
  • Time Savings: 50%+ reduction in documentation research time
  • Integration Rate: Use Context7 in 90%+ of Android implementation tasks

Query Optimization

Effective Query Patterns

// ✅ Good: Specific and actionable
context7_get_docs({
  context7CompatibleLibraryID: "/android/recyclerview",
  topic: "efficient RecyclerView implementation with DiffUtil",
  tokens: 12000
})

// ✅ Good: Problem-specific
context7_get_docs({
  context7CompatibleLibraryID: "/android/lifecycle",
  topic: "handling configuration changes in ViewModel",
  tokens: 10000
})

// ❌ Avoid: Too broad
context7_get_docs({
  context7CompatibleLibraryID: "/android",
  topic: "everything about Android development"
})

Token Management

  • Small Queries: 5,000-8,000 tokens for specific questions
  • Medium Queries: 10,000-15,000 tokens for implementation guidance
  • Large Queries: 20,000+ tokens for comprehensive documentation
  • Iterative Approach: Start small, expand if needed

🔄 Integration with Development Workflow

Research Phase Integration

Pre-Implementation Research

  1. Brave Search: Identify SOTA approaches and research
  2. Context7: Get current implementation documentation
  3. GitHub MCP: Check existing implementations in codebase
  4. Apply Findings: Implement with research-backed approach

Example: Audio Processing Implementation

// Step 1: Research SOTA approaches
brave_search({
  query: "Android real-time audio processing best practices 2024"
})

// Step 2: Get Android-specific documentation
context7_get_docs({
  context7CompatibleLibraryID: "/android/media",
  topic: "AudioRecord real-time processing patterns"
})

// Step 3: Find Kotlin coroutine patterns
context7_get_docs({
  context7CompatibleLibraryID: "/android/coroutines",
  topic: "coroutine patterns for audio processing"
})

// Step 4: Implement with research-backed approach
// Apply findings in Kotlin with proper coroutine usage

Testing Integration

Documentation-Driven Testing

// Get testing best practices
context7_get_docs({
  context7CompatibleLibraryID: "/android/testing",
  topic: "unit testing ViewModel with coroutines"
})

// Apply testing patterns from documentation
// Implement comprehensive test coverage

CI/CD Integration

Validation Through CI

  • Use GitHub MCP to monitor implementation success
  • Validate Context7-recommended patterns work in CI
  • Track performance impact of implemented solutions
  • Ensure documentation accuracy through testing

📈 Measuring Context7 Effectiveness

Success Metrics

Quantitative Metrics

  • Usage Rate: Tool uses per week (target: 15-20)
  • Success Rate: Percentage of useful results (target: 80%+)
  • Time Savings: Hours saved vs. manual research (target: 50%+)
  • Implementation Rate: Successful implementations from Context7 guidance

Qualitative Metrics

  • Documentation Quality: Accuracy and recency of information
  • Implementation Ease: How easily guidance can be applied
  • Learning Value: New patterns and best practices discovered
  • Problem Resolution: Effectiveness in solving development issues

Effectiveness Tracking

Usage Log Template

## Context7 Usage Log

**Date**: YYYY-MM-DD
**Library**: /android/[component]
**Topic**: [Specific topic]
**Tokens Used**: [Number]
**Usefulness Rating**: [1-10]
**Time Saved**: [Hours]
**Implementation Success**: [Yes/No]
**Key Insights**: [Important findings]
**Recommendations**: [How to improve usage]

Weekly Review Process

  1. Review Usage Logs: Analyze past week's Context7 usage
  2. Calculate Metrics: Track success rates and time savings
  3. Identify Patterns: Find most effective usage patterns
  4. Optimize Queries: Refine query strategies based on results
  5. Update Guidelines: Improve usage guidelines based on experience

🚀 Advanced Context7 Techniques

Multi-Query Research

// Research complex topics with multiple queries
const queries = [
  {
    libraryId: "/android/architecture",
    topic: "Clean Architecture implementation",
    tokens: 15000
  },
  {
    libraryId: "/android/dependency-injection",
    topic: "Hilt integration patterns",
    tokens: 12000
  },
  {
    libraryId: "/android/testing",
    topic: "testing Clean Architecture components",
    tokens: 10000
  }
];

// Execute queries and combine findings
// Apply comprehensive research to implementation

Library Discovery

// Find available Android libraries
context7_resolve_library({
  libraryName: "Android Jetpack Compose"
})
// Returns: /android/compose

context7_resolve_library({
  libraryName: "Android ML Kit"
})
// Returns: /android/mlkit

Version-Specific Documentation

// Get version-specific guidance
context7_get_docs({
  context7CompatibleLibraryID: "/android/api/34",
  topic: "Android 14 new features and APIs",
  tokens: 15000
})

🔧 Troubleshooting Context7 Issues

Common Issues and Solutions

Library ID Not Found

// Try alternative library names
context7_resolve_library({
  libraryName: "AndroidX Core"
})
// Try: "Android Core", "AndroidX Core KTX"

No Results for Query

  • Refine Topic: Make topic more specific
  • Check Spelling: Ensure correct technical terms
  • Try Alternative Libraries: Use broader or related library IDs
  • Reduce Token Count: Sometimes smaller queries work better

Outdated Information

  • Specify Version: Include Android API version in queries
  • Check Recency: Note when documentation was accessed
  • Cross-Reference: Validate with official Android documentation
  • Report Issues: Document any outdated information found

Performance Optimization

  • Token Efficiency: Use appropriate token counts for query size
  • Query Specificity: More specific queries often return better results
  • Batch Queries: Group related queries to reduce overhead
  • Cache Results: Reuse successful queries for similar tasks

📚 Context7 Best Practices

Query Construction

  1. Be Specific: Use precise technical terms
  2. Include Context: Mention Android version or use case
  3. Specify Format: Request code examples when needed
  4. Limit Scope: Focus on one specific topic per query

Result Evaluation

  1. Check Recency: Ensure information is current
  2. Validate Accuracy: Cross-reference with known best practices
  3. Assess Completeness: Determine if result fully answers the question
  4. Note Gaps: Identify areas where additional research is needed

Integration Practices

  1. Combine with Brave Search: Use for research + implementation
  2. Document Usage: Track effectiveness for continuous improvement
  3. Share Findings: Make successful patterns available to team
  4. Update Guidelines: Refine usage based on experience

🎯 Context7 Integration Roadmap

Immediate Actions (Week 1-2)

  • Increase weekly usage to 15-20 tool uses
  • Establish query templates for common Android tasks
  • Create usage tracking system
  • Train team on effective Context7 usage

Medium-term Goals (Month 1-3)

  • Achieve 80%+ success rate on queries
  • Integrate Context7 into standard development workflow
  • Build library of successful query patterns
  • Automate usage tracking and reporting

Long-term Vision (Month 3+)

  • Context7 as primary Android documentation source
  • Comprehensive Android library coverage
  • Automated integration with development tools
  • Community contribution of successful patterns

This guide optimizes Context7 usage for Android development. For general MCP integration, see docs/mcp-integration/mcp-optimization.md. For current project status, see docs/project-state/current-status.md.