Version: 2.0 - Unified Documentation System Last Updated: 2025-09-06 Purpose: Optimize Context7 usage for Android development documentation
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: 2 tool uses (severely underutilized)
- Target Usage: 15-20 tool uses per week
- Primary Value: Android API documentation and examples
- ✅ 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
- 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 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"
})// 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"
})// Start with broad research
brave_search({
query: "Android ViewModel best practices 2024",
summary: true
})// Get specific implementation guidance
context7_get_docs({
context7CompatibleLibraryID: "/android/architecture",
topic: "ViewModel lifecycle and state management",
tokens: 15000
})// Find practical examples
context7_get_docs({
context7CompatibleLibraryID: "/android/kotlin",
topic: "ViewModel with coroutines example",
tokens: 10000
})// 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 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
})- 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
- 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
// ✅ 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"
})- 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
- Brave Search: Identify SOTA approaches and research
- Context7: Get current implementation documentation
- GitHub MCP: Check existing implementations in codebase
- Apply Findings: Implement with research-backed approach
// 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// 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- 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
- 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
- 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
## 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]- Review Usage Logs: Analyze past week's Context7 usage
- Calculate Metrics: Track success rates and time savings
- Identify Patterns: Find most effective usage patterns
- Optimize Queries: Refine query strategies based on results
- Update Guidelines: Improve usage guidelines based on experience
// 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// Find available Android libraries
context7_resolve_library({
libraryName: "Android Jetpack Compose"
})
// Returns: /android/compose
context7_resolve_library({
libraryName: "Android ML Kit"
})
// Returns: /android/mlkit// Get version-specific guidance
context7_get_docs({
context7CompatibleLibraryID: "/android/api/34",
topic: "Android 14 new features and APIs",
tokens: 15000
})// Try alternative library names
context7_resolve_library({
libraryName: "AndroidX Core"
})
// Try: "Android Core", "AndroidX Core KTX"- 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
- 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
- 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
- Be Specific: Use precise technical terms
- Include Context: Mention Android version or use case
- Specify Format: Request code examples when needed
- Limit Scope: Focus on one specific topic per query
- Check Recency: Ensure information is current
- Validate Accuracy: Cross-reference with known best practices
- Assess Completeness: Determine if result fully answers the question
- Note Gaps: Identify areas where additional research is needed
- Combine with Brave Search: Use for research + implementation
- Document Usage: Track effectiveness for continuous improvement
- Share Findings: Make successful patterns available to team
- Update Guidelines: Refine usage based on experience
- 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
- Achieve 80%+ success rate on queries
- Integrate Context7 into standard development workflow
- Build library of successful query patterns
- Automate usage tracking and reporting
- 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.