codeseeker 1.8.0 → 1.8.1

package/LICENSE

@@ -1,21 +1,216 @@
-MIT License
-
-Copyright (c) 2025 CodeSeeker Contributors
-
-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.
+The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 ("Apache-2.0"). All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0.
+
+Contributions for which relicensing consent has been obtained are licensed under Apache-2.0. Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License.
+
+No rights beyond those granted by the applicable original license are conveyed for such contributions.
+
+---
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright
+      owner or by an individual or Legal Entity authorized to submit on behalf
+      of the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+---
+
+MIT License
+
+Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC.
+
+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.
+
+---
+
+Creative Commons Attribution 4.0 International (CC-BY-4.0)
+
+Documentation in this project (excluding specifications) is licensed under
+CC-BY-4.0. See https://creativecommons.org/licenses/by/4.0/legalcode for
+the full license text.

package/README.md

@@ -1,468 +1,153 @@
-# CodeSeeker
-
-**Graph-powered code intelligence for Claude Code.** CodeSeeker builds a knowledge graph of your codebase—not just embeddings—so Claude understands how your code actually connects.
-
-[![npm version](https://img.shields.io/npm/v/codeseeker.svg)](https://www.npmjs.com/package/codeseeker)
-[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
-[![TypeScript](https://img.shields.io/badge/TypeScript-100%25-blue.svg)](https://www.typescriptlang.org/)
-
-> **What is CodeSeeker?** An MCP server that gives AI assistants semantic code search and knowledge graph traversal. Works with **Claude Code**, **GitHub Copilot**, **Cursor**, and **Claude Desktop**.
-
-> **⚠️ NOT A VS CODE EXTENSION:** CodeSeeker is installed via `npm`, not the VS Code marketplace. It's an MCP server that enhances AI assistants, not a standalone extension.
-
-## Installation
-
-> **🚨 Important:** CodeSeeker is **NOT a VS Code extension**. It's an **MCP server** (Model Context Protocol) that works WITH AI assistants like Claude Code and GitHub Copilot. Don't look for it in the VS Code marketplace—install via the methods below.
-
-### ⚡ One-Line Install (Easiest)
-
-Copy/paste ONE command - auto-detects your system and configures everything:
-
-**macOS/Linux:**
-```bash
-curl -fsSL https://raw.githubusercontent.com/jghiringhelli/codeseeker/master/scripts/install.sh | sh
-```
-
-**Windows (PowerShell):**
-```powershell
-irm https://raw.githubusercontent.com/jghiringhelli/codeseeker/master/scripts/install.ps1 | iex
-```
-
-Restart your IDE and you're done!
-
-### 📦 Package Managers (Advanced)
-
-**Linux (Snap) - All Distributions:**
-```bash
-sudo snap install codeseeker
-codeseeker install --vscode      # or --cursor, --windsurf
-```
-> ⚠️ **Snap limitation:** Due to strict confinement, the snap can only access projects in your home directory (`~/`). For projects outside `~/`, use npm or Homebrew instead.
-
-**macOS/Linux (Homebrew):**
-```bash
-brew install jghiringhelli/codeseeker/codeseeker
-codeseeker install --vscode      # or --cursor, --windsurf
-```
-
-**Windows (Chocolatey):**
-```powershell
-choco install codeseeker
-codeseeker install --vscode      # or --cursor, --windsurf
-```
-
-**Cross-platform (npm):**
-```bash
-npm install -g codeseeker
-codeseeker install --vscode      # or --cursor, --windsurf
-```
-
-### 🚀 No Install Required (npx)
-
-Run without installing:
-```bash
-npx codeseeker init
-npx codeseeker -c "how does authentication work?"
-```
-
-### 🔌 Claude Code Plugin
-
-If you use Claude Code CLI, you can install as a plugin:
-
-```bash
-/plugin install codeseeker@github:jghiringhelli/codeseeker#plugin
-```
-
-This gives you auto-sync hooks and slash commands (`/codeseeker:init`, `/codeseeker:reindex`).
-
-### ☁️ Devcontainer / GitHub Codespaces
-
-CodeSeeker auto-installs in devcontainers! Just add `.devcontainer/devcontainer.json`:
-
-```json
-{
-  "name": "My Project",
-  "image": "mcr.microsoft.com/devcontainers/javascript-node:18",
-  "postCreateCommand": "npm install -g codeseeker && codeseeker install --vscode"
-}
-```
-
-Or use our pre-configured devcontainer (already included in this repo).
-
-### ✅ Verify Installation
-
-Ask your AI assistant: *"What CodeSeeker tools do you have?"*
-
-You should see: `search`, `search_and_read`, `show_dependencies`, `read_with_context`, `standards`, etc.
-
----
-
-## The Problem
-
-Claude Code is powerful, but it navigates your codebase like a tourist with a phrasebook:
-- **Grep searches** find text matches, not semantic meaning
-- **File reads** show code in isolation, missing the bigger picture
-- **No memory** of your project's patterns—every session starts fresh
-
-The result? Claude asks you to explain code relationships it should already know. It writes validation logic that doesn't match your existing patterns. It misses dependencies and breaks things.
-
-## How CodeSeeker Fixes This
-
-CodeSeeker builds a **knowledge graph** of your codebase:
-
-```
-┌─────────────┐     imports      ┌─────────────┐
-│  auth.ts    │ ───────────────▶ │  user.ts    │
-└─────────────┘                  └─────────────┘
-       │                                │
-       │ calls                          │ extends
-       ▼                                ▼
-┌─────────────┐     implements   ┌─────────────┐
-│ session.ts  │ ◀─────────────── │ BaseUser.ts │
-└─────────────┘                  └─────────────┘
-```
-
-When you ask "add password reset to authentication", Claude doesn't just find files containing "auth"—it traverses the graph to find:
-- What `auth.ts` imports and exports
-- Which services call authentication functions
-- What patterns exist in related code
-- How your project handles similar flows
-
-This is **Graph RAG** (Retrieval-Augmented Generation), not just vector search.
-
-## Advanced Installation Options
-
-<details>
-<summary><b>📋 Manual MCP Configuration</b> (if auto-install doesn't work)</summary>
-
-### VS Code (Claude Code & GitHub Copilot)
-
-Add to `.vscode/mcp.json` in your project:
-
-```json
-{
-  "mcpServers": {
-    "codeseeker": {
-      "command": "npx",
-      "args": ["-y", "codeseeker", "serve", "--mcp"],
-      "env": {
-        "CODESEEKER_STORAGE_MODE": "embedded"
-      }
-    }
-  }
-}
-```
-
-### Cursor
-
-Add to `.cursor/mcp.json` in your project:
-
-```json
-{
-  "mcpServers": {
-    "codeseeker": {
-      "command": "npx",
-      "args": ["-y", "codeseeker", "serve", "--mcp"],
-      "env": {
-        "CODESEEKER_STORAGE_MODE": "embedded"
-      }
-    }
-  }
-}
-```
-
-### Claude Desktop
-
-Add to your `claude_desktop_config.json`:
-
-**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
-**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
-
-```json
-{
-  "mcpServers": {
-    "codeseeker": {
-      "command": "npx",
-      "args": ["-y", "codeseeker", "serve", "--mcp"],
-      "env": {
-        "CODESEEKER_STORAGE_MODE": "embedded"
-      }
-    }
-  }
-}
-```
-
-### Global vs Project-Level Configuration
-
-```bash
-# Apply to all projects (user-level)
-codeseeker install --vscode --global
-
-# Apply to current project only
-codeseeker install --vscode
-```
-
-</details>
-
-<details>
-<summary><b>🖥️ CLI Standalone Usage</b> (without AI assistant)</summary>
-
-```bash
-npm install -g codeseeker
-cd your-project
-codeseeker init
-codeseeker -c "how does authentication work in this project?"
-```
-
-</details>
-
-## What You Get
-
-Once configured, Claude has access to these MCP tools (used automatically):
-
-| Tool | What It Does |
-|------|--------------|
-| `search_code` | Hybrid search: vector + text + path with RRF fusion |
-| `find_and_read` | Search + Read in one step - returns file content directly |
-| `get_code_relationships` | Traverse the knowledge graph (imports, calls, extends) |
-| `get_file_context` | Read a file with its related code automatically included |
-| `get_coding_standards` | Your project's detected patterns (validation, error handling) |
-| `index_project` | Manually trigger indexing (rarely needed) |
-| `notify_file_changes` | Update index for specific files |
-| `manage_index` | Dynamically exclude/include files from the index |
-
-**You don't invoke these manually**—Claude uses them automatically when searching code or analyzing relationships.
-
-## How Indexing Works
-
-**You don't need to manually index.** When Claude uses any CodeSeeker tool, the tool automatically checks if the project is indexed. If not, it indexes on first use.
-
-```
-User: "Find the authentication logic"
-        │
-        ▼
-┌─────────────────────────────────────┐
-│ Claude calls search_code()          │
-│         │                           │
-│         ▼                           │
-│ Project indexed? ──No──► Index now  │
-│         │                  (auto)   │
-│        Yes                   │      │
-│         │◀───────────────────┘      │
-│         ▼                           │
-│ Return search results               │
-└─────────────────────────────────────┘
-```
-
-First search on a new project takes 30 seconds to several minutes (depending on size). Subsequent searches are instant.
-
-## What Makes It Different
-
-| Approach | How It Works | Strengths | Limitations |
-|----------|--------------|-----------|-------------|
-| **Grep/ripgrep** | Text pattern matching | Fast, universal | No semantic understanding |
-| **Vector search only** | Embedding similarity | Finds similar code | Misses structural relationships |
-| **LSP-based tools** | Language server protocol | Precise symbol definitions | No semantic search, no cross-file reasoning |
-| **CodeSeeker** | Knowledge graph + hybrid search | Semantic + structure + patterns | Requires initial indexing (30s-5min) |
-
-### CodeSeeker's Unique Capabilities
-
-**What LSP tools can't do:**
-- *"Find code that handles errors like this"* → Semantic search finds similar patterns
-- *"What validation approach does this project use?"* → Auto-detected coding standards
-- *"Show me everything related to authentication"* → Graph traversal across indirect dependencies
-
-**What vector-only search misses:**
-- Direct import/export relationships
-- Class inheritance chains
-- Function call graphs
-- Which files actually depend on which
-
-CodeSeeker combines all three: **graph traversal** for structure, **vector search** for meaning, **text search** for precision—fused with Reciprocal Rank Fusion (RRF) for optimal results.
-
-## Auto-Detected Coding Standards
-
-CodeSeeker analyzes your codebase and extracts patterns:
-
-```json
-{
-  "validation": {
-    "email": {
-      "preferred": "z.string().email()",
-      "usage_count": 12,
-      "files": ["src/auth.ts", "src/user.ts"]
-    }
-  },
-  "react-patterns": {
-    "state": {
-      "preferred": "useState<T>()",
-      "usage_count": 45
-    }
-  }
-}
-```
-
-Detected pattern categories:
-- **validation**: Zod, Yup, Joi, validator.js, custom regex
-- **error-handling**: API error responses, try-catch patterns, custom Error classes
-- **logging**: Console, Winston, Bunyan, structured logging
-- **testing**: Jest/Vitest setup, assertion patterns
-- **react-patterns**: Hooks (useState, useEffect, useMemo, useCallback, useRef)
-- **state-management**: Redux Toolkit, Zustand, React Context, TanStack Query
-- **api-patterns**: Fetch, Axios, Express routes, Next.js API routes
-
-When Claude writes new code, it follows your existing conventions instead of inventing new ones.
-
-## Managing Index Exclusions
-
-If Claude notices files that shouldn't be indexed (like Unity's Library folder, build outputs, or generated files), it can dynamically exclude them:
-
-```typescript
-// Exclude Unity Library folder and generated files
-manage_index({
-  action: "exclude",
-  project: "my-unity-game",
-  paths: ["Library/**", "Temp/**", "*.generated.cs"],
-  reason: "Unity build artifacts"
-})
-```
-
-Exclusions are persisted in `.codeseeker/exclusions.json` and automatically respected during reindexing.
-
-## Language Support
-
-| Language | Parser | Relationship Extraction |
-|----------|--------|------------------------|
-| TypeScript/JavaScript | Babel AST | Excellent |
-| Python | Tree-sitter | Excellent |
-| Java | Tree-sitter | Excellent |
-| C# | Regex | Good |
-| Go | Regex | Good |
-| Rust, C/C++, Ruby, PHP | Regex | Basic |
-
-Tree-sitter parsers install automatically when needed.
-
-## Keeping the Index in Sync
-
-### With Claude Code Plugin
-
-The plugin installs **hooks** that automatically update the index:
-
-| Event | What Happens |
-|-------|--------------|
-| Claude edits a file | Index updated automatically |
-| Claude runs `git pull/checkout/merge` | Full reindex triggered |
-| You run `/codeseeker:reindex` | Manual full reindex |
-
-**You don't need to do anything**—the plugin handles sync automatically.
-
-### With MCP Server Only (Cursor, Claude Desktop)
-
-- **Claude-initiated changes**: Claude can call `notify_file_changes` tool
-- **Manual changes**: Not automatically detected—ask Claude to reindex periodically
-
-### Sync Summary
-
-| Setup | Claude Edits | Git Operations | Manual Edits |
-|-------|--------------|----------------|--------------|
-| **Plugin** (Claude Code) | Auto | Auto | Manual |
-| **MCP** (Cursor, Desktop) | Ask Claude | Ask Claude | Ask Claude |
-| **CLI** | Auto | Auto | Manual |
-
-## When CodeSeeker Helps Most
-
-**Good fit:**
-- Large codebases (10K+ files) where Claude struggles to find relevant code
-- Projects with established patterns you want Claude to follow
-- Complex dependency chains across multiple files
-- Teams wanting consistent AI-generated code
-
-**Less useful:**
-- Greenfield projects with little existing code
-- Single-file scripts
-- Projects where you're actively changing architecture
-
-## Architecture
-
-```
-┌──────────────────────────────────────────────────────────┐
-│                     Claude Code                          │
-│                         │                                │
-│                    MCP Protocol                          │
-│                         │                                │
-│  ┌──────────────────────▼──────────────────────────┐    │
-│  │              CodeSeeker MCP Server               │    │
-│  │  ┌─────────────┬─────────────┬────────────────┐ │    │
-│  │  │   Vector    │  Knowledge  │    Coding      │ │    │
-│  │  │   Search    │    Graph    │   Standards    │ │    │
-│  │  │  (SQLite)   │  (SQLite)   │   (JSON)       │ │    │
-│  │  └─────────────┴─────────────┴────────────────┘ │    │
-│  └─────────────────────────────────────────────────┘    │
-└──────────────────────────────────────────────────────────┘
-```
-
-All data stored locally in `.codeseeker/`. No external services required.
-
-For large teams (100K+ files, shared indexes), server mode supports PostgreSQL + Neo4j. See [Storage Documentation](docs/technical/storage.md).
-
-## Troubleshooting
-
-### "I can't find CodeSeeker in the VS Code marketplace"
-
-**CodeSeeker is NOT a VS Code extension.** It's an MCP server that works WITH AI assistants.
-
-✅ **Correct:** Install via npm: `npm install -g codeseeker`
-❌ **Wrong:** Looking for it in VS Code Extensions marketplace
-
-### MCP server not connecting
-
-1. Verify npm and npx work: `npx -y codeseeker --version`
-2. Check MCP config file syntax (valid JSON, no trailing commas)
-3. Restart your editor/Claude application completely
-4. Check that Node.js is installed: `node --version` (need v18+)
-
-### Indexing seems slow
-
-First-time indexing of large projects (50K+ files) can take 5+ minutes. Subsequent uses are instant.
-
-### Tools not appearing in Claude
-
-1. Ask Claude: *"What CodeSeeker tools do you have?"*
-2. If no tools appear, check MCP config file exists and has correct syntax
-3. Restart your IDE completely (not just reload window)
-4. Check Claude/Copilot MCP connection status in IDE
-
-### Still stuck?
-
-Open an issue: [GitHub Issues](https://github.com/jghiringhelli/codeseeker/issues)
-
-## Documentation
-
-- [Integration Guide](docs/INTEGRATION.md) - How all components connect
-- [Architecture](docs/technical/architecture.md) - Technical deep dive
-- [CLI Commands](docs/install/cli_commands_manual.md) - Full command reference
-
-## Supported Platforms
-
-| Platform | MCP Support | Install Command |
-|----------|-------------|-----------------|
-| **Claude Code** (VS Code) | Yes | `codeseeker install --vscode` or plugin |
-| **GitHub Copilot** (VS Code) | Yes (VS Code 1.99+) | `codeseeker install --vscode` |
-| **Cursor** | Yes | `codeseeker install --cursor` |
-| **Claude Desktop** | Yes | Manual config |
-| **Windsurf** | Yes | `codeseeker install --windsurf` |
-| **Visual Studio** | Yes | `codeseeker install --vs` |
-
-> **Note:** Claude Code and GitHub Copilot both run in VS Code and share the same MCP configuration (`.vscode/mcp.json`). The flags `--vscode`, `--claude-code`, and `--copilot` are interchangeable.
-
-## Support
-
-If CodeSeeker is useful to you, consider [sponsoring the project](https://github.com/sponsors/jghiringhelli).
-
-## License
-
-MIT License. See [LICENSE](LICENSE).
-
----
-
-*CodeSeeker gives Claude the code understanding that grep and embeddings alone can't provide.*
+# MCP Registry
+
+The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
+
+[**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
+
+## Development Status
+
+**2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
+
+**2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
+
+Current key maintainers:
+- **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)  
+- **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
+- **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
+- **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
+
+## Contributing
+
+We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
+
+Often (but not always) ideas flow through this pipeline:
+
+- **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
+- **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
+- **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work  
+- **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
+
+### Quick start:
+
+#### Pre-requisites
+
+- **Docker**
+- **Go 1.24.x**
+- **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
+- **golangci-lint v2.4.0**
+
+#### Running the server
+
+```bash
+# Start full development environment
+make dev-compose
+```
+
+This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
+
+**Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
+
+By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
+
+The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
+
+<details>
+<summary>Alternative: Running a pre-built Docker image</summary>
+
+Pre-built Docker images are automatically published to GitHub Container Registry:
+
+```bash
+# Run latest stable release
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
+
+# Run latest from main branch (continuous deployment)
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
+
+# Run specific release version
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
+
+# Run development build from main branch
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
+```
+
+**Available tags:** 
+- **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
+- **Continuous**: `main` (latest main branch build)
+- **Development**: `main-<date>-<sha>` (specific commit builds)
+
+</details>
+
+#### Publishing a server
+
+To publish a server, we've built a simple CLI. You can use it with:
+
+```bash
+# Build the latest CLI
+make publisher
+
+# Use it!
+./bin/mcp-publisher --help
+```
+
+See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
+
+#### Other commands
+
+```bash
+# Run lint, unit tests and integration tests
+make check
+```
+
+There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
+
+<!--
+For Claude and other AI tools: Always prefer make targets over custom commands where possible.
+-->
+
+## Architecture
+
+### Project Structure
+
+```
+├── cmd/                     # Application entry points
+│   └── publisher/           # Server publishing tool
+├── data/                    # Seed data
+├── deploy/                  # Deployment configuration (Pulumi)
+├── docs/                    # Documentation
+├── internal/                # Private application code
+│   ├── api/                 # HTTP handlers and routing
+│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)
+│   ├── config/              # Configuration management
+│   ├── database/            # Data persistence (PostgreSQL)
+│   ├── service/             # Business logic
+│   ├── telemetry/           # Metrics and monitoring
+│   └── validators/          # Input validation
+├── pkg/                     # Public packages
+│   ├── api/                 # API types and structures
+│   │   └── v0/              # Version 0 API types
+│   └── model/               # Data models for server.json
+├── scripts/                 # Development and testing scripts
+├── tests/                   # Integration tests
+└── tools/                   # CLI tools and utilities
+    └── validate-*.sh        # Schema validation tools
+```
+
+### Authentication
+
+Publishing supports multiple authentication methods:
+- **GitHub OAuth** - For publishing by logging into GitHub
+- **GitHub OIDC** - For publishing from GitHub Actions
+- **DNS verification** - For proving ownership of a domain and its subdomains
+- **HTTP verification** - For proving ownership of a domain
+
+The registry validates namespace ownership when publishing. E.g. to publish...:
+- `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
+- `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
+
+## Community Projects
+
+Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
+
+## More documentation
+
+See the [documentation](./docs) for more details if your question has not been answered here!

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codeseeker",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "Graph-powered code intelligence for Claude Code. Semantic search + knowledge graph for better AI code understanding.",
   "main": "dist/index.js",
   "bin": {

package/scripts/postinstall.js

@@ -163,11 +163,14 @@ const USER_LEVEL_AGENT_FILES = [
  */
 function isNonInteractive() {
   return !process.stdin.isTTY ||
+         !process.stdout.isTTY ||
          process.env.CI === 'true' ||
          process.env.CONTINUOUS_INTEGRATION === 'true' ||
          process.env.npm_config_yes === 'true' ||
          process.env.CODESEEKER_SKIP_POSTINSTALL === 'true' ||
-         process.env.ChocolateyInstall !== undefined;  // Skip in Chocolatey environments
+         process.env.ChocolateyInstall !== undefined ||  // Chocolatey package manager
+         process.env.CHOCOLATEY_VERSION !== undefined || // Another Chocolatey indicator
+         process.env.ChocolateyToolsLocation !== undefined; // Yet another Chocolatey indicator
 }
 
 /**