mcp-code-indexer 3.1.2__tar.gz → 3.1.4__tar.gz

{mcp_code_indexer-3.1.2/src/mcp_code_indexer.egg-info → mcp_code_indexer-3.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcp-code-indexer
-Version: 3.1.2
+Version: 3.1.4
 Summary: MCP server that tracks file descriptions across codebases, enabling AI agents to efficiently navigate and understand code through searchable summaries and token-aware overviews.
 Author: MCP Code Indexer Contributors
 Maintainer: MCP Code Indexer Contributors
@@ -59,8 +59,8 @@ Dynamic: requires-python
 
 # MCP Code Indexer 🚀
 
-[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?23)](https://badge.fury.io/py/mcp-code-indexer)
-[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?23)](https://pypi.org/project/mcp-code-indexer/)
+[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?24)](https://badge.fury.io/py/mcp-code-indexer)
+[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?24)](https://pypi.org/project/mcp-code-indexer/)
 [![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 A production-ready **Model Context Protocol (MCP) server** that revolutionizes how AI agents navigate and understand codebases. Built for high-concurrency environments with advanced database resilience, the server provides instant access to intelligent descriptions, semantic search, and context-aware recommendations while maintaining 800+ writes/sec throughput.

{mcp_code_indexer-3.1.2 → mcp_code_indexer-3.1.4}/README.md

@@ -1,7 +1,7 @@
 # MCP Code Indexer 🚀
 
-[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?23)](https://badge.fury.io/py/mcp-code-indexer)
-[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?23)](https://pypi.org/project/mcp-code-indexer/)
+[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?24)](https://badge.fury.io/py/mcp-code-indexer)
+[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?24)](https://pypi.org/project/mcp-code-indexer/)
 [![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 A production-ready **Model Context Protocol (MCP) server** that revolutionizes how AI agents navigate and understand codebases. Built for high-concurrency environments with advanced database resilience, the server provides instant access to intelligent descriptions, semantic search, and context-aware recommendations while maintaining 800+ writes/sec throughput.

{mcp_code_indexer-3.1.2 → mcp_code_indexer-3.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mcp-code-indexer"
-version = "3.1.2"
+version = "3.1.4"
 description = "MCP server that tracks file descriptions across codebases, enabling AI agents to efficiently navigate and understand code through searchable summaries and token-aware overviews."
 readme = "README.md"
 license = {text = "MIT"}

{mcp_code_indexer-3.1.2 → mcp_code_indexer-3.1.4}/src/mcp_code_indexer/database/database.py

@@ -910,64 +910,7 @@ class DatabaseManager:
             row = await cursor.fetchone()
             return row['count'] if row else 0
     
-    # Upstream inheritance operations
-    
-    async def inherit_from_upstream(self, project: Project, target_branch: str = "main") -> int:
-        """
-        Inherit file descriptions from upstream repository.
-        
-        Args:
-            project: Target project that should inherit descriptions
-            target_branch: Branch to inherit descriptions into
-            
-        Returns:
-            Number of descriptions inherited
-        """
-        if not project.upstream_origin:
-            return 0
-        
-        # Find upstream project
-        upstream_project = await self.find_project_by_origin(project.upstream_origin)
-        if not upstream_project:
-            logger.debug(f"No upstream project found for {project.upstream_origin}")
-            return 0
-        
-        # Get upstream descriptions
-        upstream_descriptions = await self.get_all_file_descriptions(
-            upstream_project.id, target_branch
-        )
-        
-        if not upstream_descriptions:
-            logger.debug(f"No upstream descriptions found in branch {target_branch}")
-            return 0
-        
-        # Get existing descriptions to avoid overwriting
-        existing_descriptions = await self.get_all_file_descriptions(
-            project.id, target_branch
-        )
-        existing_paths = {desc.file_path for desc in existing_descriptions}
-        
-        # Create new descriptions for files that don't exist locally
-        inherited_descriptions = []
-        for upstream_desc in upstream_descriptions:
-            if upstream_desc.file_path not in existing_paths:
-                new_desc = FileDescription(
-                    project_id=project.id,
-                    branch=target_branch,
-                    file_path=upstream_desc.file_path,
-                    description=upstream_desc.description,
-                    file_hash=None,  # Don't copy hash as local file may differ
-                    last_modified=datetime.utcnow(),
-                    version=1,
-                    source_project_id=upstream_project.id  # Track inheritance source
-                )
-                inherited_descriptions.append(new_desc)
-        
-        if inherited_descriptions:
-            await self.batch_create_file_descriptions(inherited_descriptions)
-            logger.info(f"Inherited {len(inherited_descriptions)} descriptions from upstream")
-        
-        return len(inherited_descriptions)
+
     
 
     

{mcp_code_indexer-3.1.2 → mcp_code_indexer-3.1.4}/src/mcp_code_indexer/server/mcp_server.py

@@ -349,48 +349,49 @@ class MCPCodeIndexServer:
                 ),
                 types.Tool(
                     name="update_codebase_overview",
-                    description="""Updates the condensed codebase overview. Create a comprehensive narrative that would help a new developer understand this codebase. Include: (1) A visual directory tree showing the main folders and their purposes, (2) Overall architecture - how components fit together, (3) Core business logic and main workflows, (4) Key technical patterns and conventions used, (5) Important dependencies and integrations, (6) Database schema overview if applicable, (7) API structure if applicable, (8) Testing approach, (9) Build and deployment notes. Write in a clear, structured format with headers and sections. Be thorough but organized - imagine writing a technical onboarding document. The overview should be substantial (think 10-20 pages of text) but well-structured so specific sections can be found easily.
+                    description="""Creates a concise codebase overview for AI agents. Focus on essential navigation and context in 3500-7000 words. Include: (1) One-paragraph system summary - what it does and its core purpose, (2) Directory tree with one-line descriptions for each major folder, (3) Key architectural patterns (e.g., MVC, microservices, event-driven) in 2-3 sentences, (4) Critical file locations (entry points, config, main business logic), (5) Essential conventions (naming, file organization, error handling), (6) Important gotchas or non-obvious connections. Keep it scannable and action-oriented.
 
-Example Structure:
+Example:
 
 ````
+## System Summary
+E-commerce platform handling product catalog, orders, and payments with React frontend and Node.js API.
+
 ## Directory Structure
 ```
 src/
-├── api/          # REST API endpoints and middleware
-├── models/       # Database models and business logic  
-├── services/     # External service integrations
-├── utils/        # Shared utilities and helpers
-└── tests/        # Test suites
+├── api/          # REST endpoints (auth in auth.js, orders in orders/)
+├── models/       # Sequelize models (User, Product, Order)
+├── services/     # Stripe (payments/), SendGrid (email/)
+├── client/       # React app (components/, pages/, hooks/)
+└── shared/       # Types and constants used by both API and client
 ```
 
-## Architecture Overview
-[Describe how components interact, data flow, key design decisions]
-
-## Core Components
-### API Layer
-[Details about API structure, authentication, routing]
+## Architecture
+RESTful API with JWT auth. React frontend calls API. Background jobs via Bull queue. PostgreSQL with Sequelize ORM.
 
-### Data Model
-[Key entities, relationships, database design]
+## Key Files
+- Entry: `src/index.js` (starts Express server)
+- Config: `src/config/` (env-specific settings)
+- Routes: `src/api/routes.js` (all endpoints defined here)
+- Auth: `src/middleware/auth.js` (JWT validation)
 
-## Key Workflows
-1. User Authentication Flow
-   [Step-by-step description]
-2. Data Processing Pipeline
-   [How data moves through the system]
+## Conventions
+- Files named `[entity].service.js` handle business logic
+- All API routes return `{ success: boolean, data?: any, error?: string }`
+- Database migrations in `migrations/` - run before adding models
 
-[Continue with other sections...]"
-````                    
-
-                    """,
+## Important Notes
+- Payment webhooks MUST be idempotent (check `processedWebhooks` table)
+- User emails are case-insensitive (lowercase in DB)
+- Order status transitions enforced in `Order.beforeUpdate` hook
+````""",
                     inputSchema={
                         "type": "object",
                         "properties": {
                             "projectName": {"type": "string", "description": "The name of the project"},
                             "folderPath": {"type": "string", "description": "Absolute path to the project folder on disk"},
-
-                            "overview": {"type": "string", "description": "Comprehensive narrative overview of the codebase (10-30k tokens recommended)"}
+                            "overview": {"type": "string", "description": "Concise codebase overview (aim for 3500-7500 words / 5k-10k tokens)"}
                         },
                         "required": ["projectName", "folderPath", "overview"],
                         "additionalProperties": False

{mcp_code_indexer-3.1.2 → mcp_code_indexer-3.1.4/src/mcp_code_indexer.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcp-code-indexer
-Version: 3.1.2
+Version: 3.1.4
 Summary: MCP server that tracks file descriptions across codebases, enabling AI agents to efficiently navigate and understand code through searchable summaries and token-aware overviews.
 Author: MCP Code Indexer Contributors
 Maintainer: MCP Code Indexer Contributors
@@ -59,8 +59,8 @@ Dynamic: requires-python
 
 # MCP Code Indexer 🚀
 
-[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?23)](https://badge.fury.io/py/mcp-code-indexer)
-[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?23)](https://pypi.org/project/mcp-code-indexer/)
+[![PyPI version](https://badge.fury.io/py/mcp-code-indexer.svg?24)](https://badge.fury.io/py/mcp-code-indexer)
+[![Python](https://img.shields.io/pypi/pyversions/mcp-code-indexer.svg?24)](https://pypi.org/project/mcp-code-indexer/)
 [![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 A production-ready **Model Context Protocol (MCP) server** that revolutionizes how AI agents navigate and understand codebases. Built for high-concurrency environments with advanced database resilience, the server provides instant access to intelligent descriptions, semantic search, and context-aware recommendations while maintaining 800+ writes/sec throughput.