codebase_index 0.3.2 → 0.4.0

data/CODE_OF_CONDUCT.md

@@ -1,83 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at info@leah.wtf. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -1,65 +0,0 @@
-# Contributing to CodebaseIndex
-
-Thank you for your interest in contributing to CodebaseIndex!
-
-## Bug Reports
-
-Please open an issue on GitHub with:
-
-- A clear description of the bug
-- Steps to reproduce
-- Expected vs. actual behavior
-- Your Ruby version, Rails version, and database adapter
-
-## Feature Requests
-
-Open an issue describing:
-
-- The problem you're trying to solve
-- Your proposed solution
-- Any alternatives you've considered
-
-## Pull Requests
-
-1. Fork the repo and create your branch from `main`
-2. Install dependencies: `bin/setup`
-3. Make your changes
-4. Add tests for new functionality
-5. Ensure the test suite passes: `bundle exec rake spec`
-6. Ensure code style passes: `bundle exec rubocop`
-7. Update CHANGELOG.md with your changes
-8. Open a pull request
-
-## Development Setup
-
-```bash
-git clone https://github.com/LeahArmstrong/codebase_index.git
-cd codebase_index
-bin/setup
-bundle exec rake spec    # Run tests
-bundle exec rubocop      # Check style
-```
-
-## Testing
-
-CodebaseIndex has two test suites:
-
-- **Gem unit specs** (`spec/`): Run with `bundle exec rake spec`. No Rails boot required.
-- **Integration specs**: Run inside a host Rails app to test real extraction.
-
-All new features need tests. Bug fixes should include a regression test.
-
-## Code Style
-
-- `frozen_string_literal: true` on every file
-- YARD documentation on public methods
-- `rescue StandardError`, never bare `rescue`
-- All extractors return `Array<ExtractedUnit>`
-
-## Runtime Introspection Requirement
-
-CodebaseIndex uses runtime introspection, not static parsing. If your feature requires access to Rails internals (ActiveRecord reflections, route introspection, etc.), it must run inside a booted Rails environment. Unit tests should use mocks/stubs; integration tests should run in a real Rails app.
-
-## License
-
-By contributing, you agree that your contributions will be licensed under the MIT License.

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2024-2026 Leah Armstrong
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

data/README.md

@@ -1,325 +0,0 @@
-# CodebaseIndex
-
-A Rails codebase extraction and indexing system designed to provide accurate, version-specific context for AI-assisted development tooling.
-
-## The Problem
-
-LLMs working with Rails codebases face a fundamental accuracy gap. Training data contains documentation and examples from many Rails versions, but a production app runs on *one* version. When a developer asks "what options does `has_many` support?" or "what callbacks fire when a record is saved?", the answer depends on their exact Rails version — and generic LLM responses often get it wrong.
-
-Beyond version accuracy, Rails conventions hide enormous amounts of implementation behind "magic." A model file might be 50 lines, but with concerns inlined, schema context, callbacks, validations, and association behavior, the *actual* surface area is 10x that. AI tools that only see the source file miss most of what matters.
-
-CodebaseIndex solves this by:
-
-- **Running inside Rails** to leverage runtime introspection (not just static parsing)
-- **Inlining concerns** directly into model source so the full picture is visible
-- **Prepending schema comments** with column types, indexes, and foreign keys
-- **Mapping routes to controllers** so HTTP → action flow is explicit
-- **Indexing the exact Rails/gem source** for the versions in `Gemfile.lock`
-- **Tracking dependencies** bidirectionally so you can trace impact across the codebase
-- **Enriching with git data** so you know what's actively changing vs. dormant
-
-See [Why CodebaseIndex?](docs/WHY_CODEBASE_INDEX.md) for concrete before/after examples.
-
-## Quick Start
-
-```bash
-# Add to your Rails app's Gemfile, then:
-bundle install
-rails generate codebase_index:install
-bundle exec rake codebase_index:extract
-bundle exec rake codebase_index:stats
-# Add the MCP server to .mcp.json (see below) and start asking questions
-```
-
-See [Getting Started](docs/GETTING_STARTED.md) for the full walkthrough including Docker, storage presets, and CI setup.
-
-## Installation
-
-Add to your Gemfile:
-
-```ruby
-gem 'codebase_index'
-```
-
-Then:
-
-```bash
-bundle install
-rails generate codebase_index:install
-rails db:migrate
-```
-
-Create a minimal configuration:
-
-```ruby
-# config/initializers/codebase_index.rb
-CodebaseIndex.configure do |config|
-  config.output_dir = Rails.root.join('tmp/codebase_index')
-end
-```
-
-Or install the gem directly:
-
-```bash
-gem install codebase_index
-```
-
-> **Requires Rails.** Extraction runs inside a booted Rails application using runtime introspection (`ActiveRecord::Base.descendants`, `Rails.application.routes`, etc.). The gem cannot extract from source files alone. See [Getting Started](docs/GETTING_STARTED.md) for full setup details.
-
-## Target Environment
-
-Designed for Rails applications of any scale, with particular strength in large monoliths:
-
-- Any database (MySQL, PostgreSQL, SQLite)
-- Any background job system (Sidekiq, Solid Queue, GoodJob, inline)
-- Any view layer (ERB, Phlex, ViewComponent)
-- Docker or bare metal, CI or manual
-- Continuous or one-shot indexing
-
-See [docs/BACKEND_MATRIX.md](docs/BACKEND_MATRIX.md) for supported infrastructure combinations.
-
-## Use Cases
-
-**1. Coding & Debugging** — Primary context for AI coding assistants. Answer "how does our checkout flow work?" with the actual service, model callbacks, controller actions, and framework behavior for the running version.
-
-**2. Performance Analysis** — Correlate code structure with runtime behavior. Identify models with high write volume and complex callback chains, find N+1-prone association patterns, surface hot code paths.
-
-**3. Deeper Analytics** — Query frequency by scope, error rates by action, background job characteristics. Bridge the gap between code structure and operational data.
-
-**4. Support & Marketing Tooling** — Domain-concept retrieval for non-developers. Map business terms to code paths, surface feature flags, document user-facing behavior.
-
-## Architecture
-
-```
-┌─────────────────────────────────────────────────────────────────────┐
-│                        CodebaseIndex                                │
-├─────────────────────────────────────────────────────────────────────┤
-│                                                                     │
-│  ┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐ │
-│  │   Extraction    │───▶│     Storage     │◀───│    Retrieval    │ │
-│  └─────────────────┘    └─────────────────┘    └─────────────────┘ │
-│          │                      │                      │           │
-│          ▼                      ▼                      ▼           │
-│  ┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐ │
-│  │   Extractors    │    │  JSON per unit  │    │ Query Classifier│ │
-│  │  · Model        │    │  Vector Index   │    │ Context Assembly│ │
-│  │  · Controller   │    │  Metadata Index │    │ Result Ranking  │ │
-│  │  · Service      │    │  Dep Graph      │    │                 │ │
-│  │  · Component    │    │                 │    │                 │ │
-│  │  · Rails Source │    │                 │    │                 │ │
-│  └─────────────────┘    └─────────────────┘    └─────────────────┘ │
-│                                                                     │
-└─────────────────────────────────────────────────────────────────────┘
-```
-
-### Extraction Pipeline
-
-Extraction runs inside the Rails application (via rake task) to access runtime introspection — `ActiveRecord::Base.descendants`, `Rails.application.routes`, reflection APIs, etc. This is fundamentally more accurate than static parsing.
-
-**Four phases:**
-
-1. **Extract** — Each extractor produces `ExtractedUnit` objects with source, metadata, and dependencies
-2. **Resolve dependents** — Build reverse dependency edges (who calls what)
-3. **Enrich with git** — Last modified, contributors, change frequency, recent commits
-4. **Write output** — JSON per unit, dependency graph, manifest, structural summary
-
-### Extractors (34)
-
-34 extractors cover every major Rails concept: models (with inlined concerns and schema), controllers (with route context), services, jobs, mailers, GraphQL types/mutations/resolvers, serializers, view components (Phlex and ViewComponent), ERB templates, decorators, concerns, validators, policies, routes, middleware, engines, i18n, Action Cable, rake tasks, migrations, database views, state machines, events, caching patterns, factories, test mappings, and Rails framework source pinned to exact installed versions.
-
-See [docs/EXTRACTOR_REFERENCE.md](docs/EXTRACTOR_REFERENCE.md) for per-extractor documentation with configuration, edge cases, and example output.
-
-### Key Design Decisions
-
-**Concern inlining** — included concerns are embedded directly in the model's source. **Route prepending** — controllers get a route header showing HTTP verb → path → action. **Semantic chunking** — models split by purpose (associations, callbacks, validations), controllers split per-action. **Dependency graph with BFS blast radius** — forward and reverse edges enable change-impact traversal.
-
-## MCP Servers
-
-CodebaseIndex ships two [MCP](https://modelcontextprotocol.io/) servers for integrating with AI development tools (Claude Code, Cursor, Windsurf, etc.).
-
-**Index Server** (27 tools) — Reads pre-extracted data from disk. No Rails boot required. Provides code lookup, dependency traversal, graph analysis, semantic search, pipeline management, feedback collection, and temporal snapshots.
-
-```bash
-codebase-index-mcp /path/to/rails-app/tmp/codebase_index
-```
-
-**Console Server** (31 tools) — Bridges to a live Rails process for database queries, model diagnostics, job monitoring, and guarded operations. All queries run in rolled-back transactions with SQL validation and audit logging.
-
-```bash
-codebase-console-mcp
-```
-
-See [docs/MCP_SERVERS.md](docs/MCP_SERVERS.md) for the full tool catalog and setup instructions.
-
-### Claude Code Setup
-
-Add the servers to your project's `.mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "codebase-index": {
-      "command": "codebase-index-mcp-start",
-      "args": ["/path/to/rails-app/tmp/codebase_index"]
-    },
-    "codebase-console": {
-      "command": "bundle",
-      "args": ["exec", "rake", "codebase_index:console"],
-      "cwd": "/path/to/rails-app"
-    }
-  }
-}
-```
-
-> **Recommended**: Use `codebase-index-mcp-start` instead of `codebase-index-mcp` for Claude Code. It validates the index directory exists, checks for a manifest, ensures dependencies are installed, and restarts automatically on failure.
-
-The **index server** reads from a pre-extracted directory — run `bundle exec rake codebase_index:extract` in your Rails app first.
-
-The **console server** runs embedded inside your Rails app (no config file needed). For Docker setups, see [docs/DOCKER_SETUP.md](docs/DOCKER_SETUP.md).
-
-## Subsystems
-
-```
-lib/codebase_index/
-├── extractor.rb              # Orchestrator — coordinates all 34 extractors
-├── extracted_unit.rb         # Core value object (the universal currency)
-├── dependency_graph.rb       # Directed graph + PageRank scoring
-├── graph_analyzer.rb         # Structural analysis (orphans, hubs, cycles, bridges)
-├── retriever.rb              # Retrieval orchestrator with degradation tiers
-├── extractors/               # 34 extractors (one per Rails concept)
-├── ast/                      # Prism-based AST layer
-├── ruby_analyzer/            # Static analysis (class, method, dataflow)
-├── chunking/                 # Semantic chunking (type-aware splitting)
-├── embedding/                # Embedding pipeline (OpenAI, Ollama)
-├── storage/                  # Storage backends (pgvector, Qdrant, SQLite)
-├── retrieval/                # Retrieval pipeline (classify, search, rank, assemble)
-├── mcp/                      # MCP Index Server (27 tools)
-├── console/                  # Console MCP Server (31 tools, 4 tiers)
-├── coordination/             # Multi-agent pipeline locking
-├── notion/                   # Notion export
-├── session_tracer/           # Session tracing middleware
-├── temporal/                 # Temporal snapshot system
-└── evaluation/               # Retrieval evaluation harness
-
-exe/
-├── codebase-index-mcp        # Index Server executable (stdio)
-├── codebase-index-mcp-start  # Self-healing MCP wrapper
-├── codebase-index-mcp-http   # Index Server (HTTP/Rack)
-└── codebase-console-mcp      # Console MCP Server executable
-```
-
-See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for the full pipeline explanation — extraction phases, dependency graph, retrieval pipeline, storage backends, and semantic chunking.
-
-## Usage
-
-### Full Extraction
-
-```bash
-bundle exec rake codebase_index:extract
-```
-
-### Incremental (CI)
-
-```bash
-bundle exec rake codebase_index:incremental
-```
-
-Auto-detects GitHub Actions / GitLab CI environment. See [Getting Started](docs/GETTING_STARTED.md) for CI workflow YAML.
-
-### Docker
-
-Extraction runs inside the container; the Index Server runs on the host reading volume-mounted output. See [docs/DOCKER_SETUP.md](docs/DOCKER_SETUP.md) for Docker setup, MCP config, and troubleshooting.
-
-```bash
-docker compose exec app bundle exec rake codebase_index:extract
-```
-
-### Other Tasks
-
-```bash
-rake codebase_index:validate          # Check index integrity
-rake codebase_index:stats             # Show unit counts, sizes, graph stats
-rake codebase_index:clean             # Remove index
-rake codebase_index:embed             # Embed all extracted units
-rake codebase_index:embed_incremental # Embed changed units only
-rake codebase_index:flow[EntryPoint]  # Generate execution flow for an entry point
-rake codebase_index:console           # Start console MCP server
-rake codebase_index:notion_sync       # Sync models/columns to Notion databases
-```
-
-See [docs/NOTION_INTEGRATION.md](docs/NOTION_INTEGRATION.md) for Notion export configuration.
-
-### Ruby API
-
-> **Requires a booted Rails environment.** These methods use runtime introspection and must be called from within a Rails process (console, rake task, initializer).
-
-```ruby
-# Full extraction (output_dir from configuration)
-CodebaseIndex.extract!
-
-# Incremental
-CodebaseIndex.extract_changed!(["app/models/user.rb", "app/services/checkout.rb"])
-
-# Configuration
-CodebaseIndex.configure do |config|
-  config.output_dir = Rails.root.join("tmp/codebase_index")
-  config.max_context_tokens = 8000
-  config.include_framework_sources = true
-  config.add_gem "devise", paths: ["lib/devise/models"], priority: :high
-end
-```
-
-## Output Structure
-
-```
-tmp/codebase_index/
-├── manifest.json              # Extraction metadata, git SHA, checksums
-├── dependency_graph.json      # Full graph with forward/reverse edges
-├── SUMMARY.md                 # Human-readable structural overview
-├── models/
-│   ├── _index.json            # Quick lookup index
-│   ├── User.json              # Full extracted unit
-│   └── Order.json
-├── controllers/
-│   ├── _index.json
-│   └── OrdersController.json
-├── services/
-│   ├── _index.json
-│   └── CheckoutService.json
-├── components/
-│   └── ...
-└── rails_source/
-    └── ...
-```
-
-Each unit JSON contains: `identifier`, `type`, `file_path`, `source_code` (annotated), `metadata` (rich structured data), `dependencies`, `dependents`, `chunks` (if applicable), and `estimated_tokens`.
-
-## Documentation
-
-| Guide | Purpose |
-|-------|---------|
-| [Getting Started](docs/GETTING_STARTED.md) | Install, configure, extract, inspect |
-| [FAQ](docs/FAQ.md) | Common questions about setup, extraction, MCP, Docker |
-| [Troubleshooting](docs/TROUBLESHOOTING.md) | Symptom → cause → fix for common problems |
-| [Architecture](docs/ARCHITECTURE.md) | Pipeline stages, dependency graph, retrieval, storage |
-| [Extractor Reference](docs/EXTRACTOR_REFERENCE.md) | What each of the 34 extractors captures |
-| [MCP Servers](docs/MCP_SERVERS.md) | Full tool catalog and setup for Claude Code, Cursor, Windsurf |
-| [MCP Tool Cookbook](docs/MCP_TOOL_COOKBOOK.md) | Scenario-based examples for common tasks |
-| [Configuration Reference](docs/CONFIGURATION_REFERENCE.md) | All options with defaults |
-| [Backend Matrix](docs/BACKEND_MATRIX.md) | Supported infrastructure combinations |
-
-## Development
-
-```bash
-bin/setup          # Install dependencies
-bundle exec rake spec      # Run tests
-bundle exec rubocop        # Lint
-```
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/LeahArmstrong/codebase_index. See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](LICENSE.txt).

data/exe/codebase-console

@@ -1,59 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# Embedded console MCP server — runs inside a Rails environment.
-#
-# Usage (via rake, recommended):
-#   bundle exec rake codebase_index:console
-#
-# Usage (via rails runner):
-#   bundle exec rails runner "$(bundle show codebase_index)/exe/codebase-console"
-#
-# The rake task captures stdout before Rails boots and passes the fd via
-# $codebase_index_protocol_out. When run via rails runner, this script
-# captures stdout itself to keep MCP protocol clean.
-
-# Check if the rake task already captured stdout for us.
-protocol_out = $codebase_index_protocol_out # rubocop:disable Style/GlobalVars
-
-unless protocol_out
-  # Running via rails runner — capture stdout ourselves.
-  protocol_out = $stdout.dup
-  $stdout.reopen($stderr)
-end
-
-require 'codebase_index/console/server'
-
-# Ensure all application models are loaded for the registry.
-Rails.application.eager_load!
-
-registry = ActiveRecord::Base.descendants.each_with_object({}) do |model, hash|
-  next if model.abstract_class?
-  next unless model.table_exists?
-
-  hash[model.name] = model.column_names
-rescue StandardError
-  next
-end
-
-validator = CodebaseIndex::Console::ModelValidator.new(registry: registry)
-safe_context = CodebaseIndex::Console::SafeContext.new(connection: ActiveRecord::Base.connection)
-
-redacted_columns = if CodebaseIndex.respond_to?(:configuration) && CodebaseIndex.configuration
-                     Array(CodebaseIndex.configuration.console_redacted_columns)
-                   else
-                     []
-                   end
-
-server = CodebaseIndex::Console::Server.build_embedded(
-  model_validator: validator,
-  safe_context: safe_context,
-  redacted_columns: redacted_columns
-)
-
-# Restore the protocol output for MCP transport.
-$stdout.reopen(protocol_out)
-protocol_out.close unless protocol_out.closed?
-
-transport = MCP::Server::Transports::StdioTransport.new(server)
-transport.open

data/exe/codebase-console-mcp

@@ -1,22 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# Console MCP server for querying live Rails application state.
-#
-# Usage:
-#   codebase-console-mcp
-#   CODEBASE_CONSOLE_CONFIG=/path/to/console.yml codebase-console-mcp
-#
-# Connects to a Rails application via a bridge process (Docker exec, direct,
-# or SSH) and exposes read-only query tools via the Model Context Protocol
-# (stdio transport).
-
-require 'yaml'
-require_relative '../lib/codebase_index/console/server'
-
-config_path = ENV.fetch('CODEBASE_CONSOLE_CONFIG', File.expand_path('~/.codebase_index/console.yml'))
-config = File.exist?(config_path) ? YAML.safe_load_file(config_path) : {}
-
-server = CodebaseIndex::Console::Server.build(config: config)
-transport = MCP::Server::Transports::StdioTransport.new(server)
-transport.open

data/exe/codebase-index-mcp

@@ -1,34 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# MCP server for querying CodebaseIndex extraction output.
-#
-# Usage:
-#   codebase-index-mcp [INDEX_DIR]
-#   CODEBASE_INDEX_DIR=/path/to/output codebase-index-mcp
-#
-# Reads JSON files from the extraction output directory and exposes
-# them via the Model Context Protocol (stdio transport).
-# Does NOT require Rails — only reads pre-extracted data.
-
-require_relative '../lib/codebase_index'
-require_relative '../lib/codebase_index/dependency_graph'
-require_relative '../lib/codebase_index/graph_analyzer'
-require_relative '../lib/codebase_index/mcp/server'
-require_relative '../lib/codebase_index/mcp/bootstrapper'
-require_relative '../lib/codebase_index/embedding/text_preparer'
-require_relative '../lib/codebase_index/embedding/indexer'
-
-index_dir = CodebaseIndex::MCP::Bootstrapper.resolve_index_dir(ARGV)
-retriever = CodebaseIndex::MCP::Bootstrapper.build_retriever
-snapshot_store = CodebaseIndex::MCP::Bootstrapper.build_snapshot_store(index_dir)
-
-server = CodebaseIndex::MCP::Server.build(index_dir: index_dir, retriever: retriever, snapshot_store: snapshot_store)
-
-# Pin protocol version for broad client compatibility (Claude Code, Cursor, etc.)
-if ENV['MCP_PROTOCOL_VERSION']
-  server.configuration = MCP::Configuration.new(protocol_version: ENV['MCP_PROTOCOL_VERSION'])
-end
-
-transport = MCP::Server::Transports::StdioTransport.new(server)
-transport.open

data/exe/codebase-index-mcp-http

@@ -1,37 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# MCP server for querying CodebaseIndex extraction output over HTTP.
-#
-# Usage:
-#   codebase-index-mcp-http [INDEX_DIR]
-#   CODEBASE_INDEX_DIR=/path/to/output codebase-index-mcp-http
-#
-# Reads JSON files from the extraction output directory and exposes
-# them via the Model Context Protocol (Streamable HTTP transport).
-# Requires the `rackup` gem and a Rack-compatible server (e.g., puma).
-
-require 'rackup'
-require_relative '../lib/codebase_index'
-require_relative '../lib/codebase_index/dependency_graph'
-require_relative '../lib/codebase_index/graph_analyzer'
-require_relative '../lib/codebase_index/mcp/server'
-require_relative '../lib/codebase_index/mcp/bootstrapper'
-require_relative '../lib/codebase_index/embedding/text_preparer'
-require_relative '../lib/codebase_index/embedding/indexer'
-
-index_dir = CodebaseIndex::MCP::Bootstrapper.resolve_index_dir(ARGV)
-retriever = CodebaseIndex::MCP::Bootstrapper.build_retriever
-snapshot_store = CodebaseIndex::MCP::Bootstrapper.build_snapshot_store(index_dir)
-
-port = (ENV['PORT'] || 9292).to_i
-host = ENV['HOST'] || 'localhost'
-
-server = CodebaseIndex::MCP::Server.build(index_dir: index_dir, retriever: retriever, snapshot_store: snapshot_store)
-transport = MCP::Server::Transports::StreamableHTTPTransport.new(server)
-server.transport = transport
-
-app = proc { |env| transport.handle_request(Rack::Request.new(env)) }
-
-warn "CodebaseIndex MCP HTTP server starting on http://#{host}:#{port}"
-Rackup::Handler.default.run(app, Port: port, Host: host)