René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[FR] Add timeframe/temporal query parameters to MCP tools for trend analysis","articleBody":"## Problem Statement\n\nCurrently, Sourcebot's MCP tools (`search_code`, `list_repos`, `get_file_source`) only provide access to the current state of the codebase. This limitation prevents AI language models from performing meaningful temporal analysis, trend reporting, or historical insights when using the Sourcebot MCP server.\n\n## Use Case\n\nWhen LLMs attempt to analyze code evolution, track changes over time, or provide trend analysis, they are unable to do so effectively because the MCP tools lack timeframe filtering capabilities. This results in responses like \"I cannot analyze trends over time with the available tools\" or incomplete analysis based only on current code state.\n\n### Real-World Examples:\n- **Trend Analysis**: \"Show me how the usage of async/await has evolved in our codebase over the last year\"\n- **Historical Search**: \"Find all instances where deprecated function X was removed between March and June\"\n- **Evolution Tracking**: \"Compare the error handling patterns used 6 months ago vs today\"\n- **Regression Analysis**: \"Identify when specific security patterns were introduced across repositories\"\n\n## Proposed Solution\n\nAdd temporal/timeframe parameters to existing MCP tools to enable time-based querying:\n\n### Enhanced `search_code` Tool\nAdd optional parameters:\n```typescript\n{\n  since?: string;          // ISO date string (e.g., \"2024-01-01\")\n  until?: string;          // ISO date string (e.g., \"2024-12-31\")\n  dateRange?: string;      // Relative range (e.g., \"last-3-months\", \"last-year\")\n  gitRevision?: string;    // Specific commit/tag/branch\n  compareRevisions?: {     // Compare between two points in time\n    from: string;\n    to: string;\n  };\n  includeDeletedFiles?: boolean; // Include files that were deleted in timeframe\n}\n```\n\n### Enhanced `list_repos` Tool\nAdd repository filtering by activity timeframe:\n```typescript\n{\n  activeAfter?: string;    // Only repos with commits after this date\n  activeBefore?: string;   // Only repos with commits before this date\n}\n```\n\n### New `search_commits` Tool\n```typescript\n{\n  query: string;           // Search in commit messages, authors, changes\n  since?: string;\n  until?: string;\n  author?: string;\n  repository?: string[];\n}\n```\n\n## Technical Implementation Considerations\n\n1. **Git Integration**: Leverage git log with `--since`, `--until`, `--author` flags\n2. **Zoekt Enhancement**: Extend Zoekt indexing to include commit metadata and timestamps\n3. **API Compatibility**: Maintain backward compatibility by making all new parameters optional\n4. **Performance**: Consider caching mechanisms for frequently requested time ranges\n5. **Date Formats**: Support both absolute (ISO 8601) and relative dates (\"1 week ago\", \"last month\")\n\n## Benefits\n\n- **Enhanced AI Analysis**: Enable LLMs to provide comprehensive temporal insights and trend analysis\n- **Historical Context**: Allow developers to understand code evolution and decision history\n- **Compliance \u0026 Auditing**: Support regulatory requirements for tracking code changes over time\n- **Research Capabilities**: Enable academic and organizational research on codebase evolution\n- **Debugging**: Help identify when bugs or issues were introduced\n\n## Related Issues\n\nThis request complements issue #22 \"FR: Ability to query for configuration in repositories over time\" but focuses specifically on enhancing the MCP interface for broader temporal querying capabilities.\n\n## Community Impact\n\nThis feature would make Sourcebot's MCP integration significantly more powerful for AI-assisted development workflows, positioning it as a leader in temporal code analysis capabilities. Many organizations need this functionality for compliance, research, and advanced AI-powered insights.\n\n## Alternative Approaches Considered\n\n1. **Client-side Git Integration**: Less efficient and requires additional tooling\n2. **Separate Temporal API**: Would fragment the interface and require additional complexity\n3. **External Time-series Database**: Overkill for this use case and adds infrastructure complexity\n\nThe proposed approach of enhancing existing MCP tools provides the most seamless integration with current workflows while enabling powerful new capabilities.","author":{"url":"https://github.com/waynesun09","@type":"Person","name":"waynesun09"},"datePublished":"2025-09-17T16:53:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/511/sourcebot/issues/511"}