Skip to main content
mcpSource-backed

Code Index MCP Server

Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases.

by johnhuang316 · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://raw.githubusercontent.com/johnhuang316/code-index-mcp/master/README.md, https://github.com/johnhuang316/code-index-mcp
Brand
Code Index MCP
Brand domain
github.com
Safety notes
Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources., Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths., Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases., The server can create and clear index/cache settings and temporary directories used for stored index data., Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository.
Privacy notes
Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings., Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree., File watcher status, exclude patterns, and settings can reveal local project layout and development conventions., If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine., Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing.
Author
johnhuang316
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime2Review & approval2General110 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.

4 areas
  • SafetyLocal filesCode Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources.
  • SafetyCredentials & tokensPoint `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths.
  • SafetyLocal filesDeep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases.
  • SafetyData retentionThe server can create and clear index/cache settings and temporary directories used for stored index data.
  • SafetyCredentials & tokensSearch results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository.
  • PrivacyLocal filesTool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings.
  • PrivacyData retentionIndex data and temp directories can persist derived repository structure or symbol metadata outside the source tree.
  • PrivacyLocal filesFile watcher status, exclude patterns, and settings can reveal local project layout and development conventions.
  • PrivacyThird-party handlingIf an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine.
  • PrivacyCredentials & tokensExclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing.

Disclosure: MIT-licensed Python MCP server for local code indexing and analysis. This entry is separate from semantic code agents and graph-indexing entries because it focuses on local project indexes, file discovery, search backends, and symbol summaries through the `code-index-mcp` package.

Safety notes

  • Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources.
  • Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths.
  • Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases.
  • The server can create and clear index/cache settings and temporary directories used for stored index data.
  • Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository.

Privacy notes

  • Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings.
  • Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree.
  • File watcher status, exclude patterns, and settings can reveal local project layout and development conventions.
  • If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine.
  • Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing.

Prerequisites

  • Python 3.10 or newer.
  • uv or another Python package runner that can install `code-index-mcp`.
  • An approved repository path that the MCP client is allowed to inspect.
  • Optional native search tools such as ripgrep, ugrep, ag, or grep for faster search backends.
  • Review of exclude patterns, file watcher behavior, temp/index storage, and deep-index cost for large repositories.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
MIT-licensed Python MCP server for local code indexing and analysis. This entry is separate from semantic code agents and graph-indexing entries because it focuses on local project indexes, file discovery, search backends, and symbol summaries through the `code-index-mcp` package.
Full copyable content
{
  "mcpServers": {
    "code-index": {
      "command": "uvx",
      "args": [
        "code-index-mcp",
        "--project-path",
        "ABSOLUTE_PATH_TO_REPOSITORY"
      ]
    }
  }
}

About this resource

Content

Code Index MCP is a local code-aware MCP server for indexing repositories and answering project navigation questions. It lets an AI assistant set a project path, refresh shallow file indexes, build deeper symbol indexes, search code, find files, inspect file summaries, retrieve symbol bodies, and monitor file watcher status.

Use it when a coding agent needs fast, repeatable local context from a specific repository without granting a broader shell or editor-control server. It is best configured with an explicit project path and reviewed exclude patterns so only the intended source tree is indexed.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, PyPI metadata, license, package metadata, MCP server implementation, well-known MCP manifest, FastMCP config, and restart playbook for current setup and operation details.

Features

  • Set or bootstrap a project path for repository-specific indexing.
  • Build shallow file indexes and optional deep symbol indexes.
  • Search code with native search backends such as ugrep, ripgrep, ag, or grep when available.
  • Find files through glob patterns.
  • Summarize files, imports, symbols, methods, functions, and complexity data.
  • Retrieve symbol bodies after building a deep index.
  • Monitor file changes and configure watcher behavior.
  • Store indexes and settings in temp/index directories.
  • Support tree-sitter strategies for Python, JavaScript, TypeScript, Java, Kotlin, C#, Go, Objective-C, Zig, and Rust, with fallback handling for many other file types.
  • Publish .well-known and FastMCP metadata for clients that can import MCP manifests.

Installation

Run with uvx and an explicit project path:

uvx code-index-mcp --project-path ABSOLUTE_PATH_TO_REPOSITORY

Add it to an MCP client:

{
  "mcpServers": {
    "code-index": {
      "command": "uvx",
      "args": [
        "code-index-mcp",
        "--project-path",
        "ABSOLUTE_PATH_TO_REPOSITORY"
      ]
    }
  }
}

You can also start without --project-path and call the set_project_path tool after launch, but an explicit startup path is easier to audit.

Use Cases

  • Find all files or functions related to a feature before editing.
  • Search for deprecated APIs, TODOs, config keys, routes, or error handling.
  • Summarize a file's imports, symbols, functions, and structural complexity.
  • Build a deep index before asking where a symbol is defined or used.
  • Keep a coding session's repository context fresh after file changes.
  • Compare project structure across Python, TypeScript, Java, Go, Rust, C#, and other mixed-language repositories.

Safety and Privacy

Code Index MCP is read-oriented, but it still grants the model visibility into local source code and derived repository metadata. Scope it to one repository, review exclude patterns, and avoid indexing generated artifacts, vendored dependencies, secret stores, customer data, or unrelated sibling projects.

Remember that search snippets and summaries can contain secrets if the repository contains secrets. Treat MCP results as repository data, especially when the MCP client sends tool output to a remote model provider.

Duplicate Notes

Existing catalog entries cover semantic code agents, graph-backed context servers, and token-efficient code search tools. This entry covers the separate johnhuang316/code-index-mcp Python package and its local repository indexing, file discovery, watcher refresh, and symbol-summary workflow.

Source citations

Add this badge to your README

Show that Code Index MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/code-index-mcp-server.svg)](https://heyclau.de/entry/mcp/code-index-mcp-server)

How it compares

Code Index MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases.

Open dossier

Local-first codebase intelligence MCP server that indexes repositories with tree-sitter, stores searchable chunks in DuckDB, and gives Claude semantic search, regex search, daemon status, and deep code research tools.

Open dossier

Code intelligence MCP server with a Zig core for local project indexing, structural outlines, symbol lookup, search, dependency graphs, snapshots, remote public-repo queries, and fallback edits.

Open dossier

MCP server for Google Search Console that lets Claude list properties, inspect indexing status, query search analytics, compare performance periods, audit sitemaps, and manage Search Console resources with guarded destructive tools.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandChunkHound logoChunkHoundCodeDB logoCodeDB
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
Authorjohnhuang316ChunkHoundjustrachAmin Foroutan
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesCode Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources. Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths. Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases. The server can create and clear index/cache settings and temporary directories used for stored index data. Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository.ChunkHound reads source files, Markdown, text, PDFs, and supported config files under the target directory and stores indexed chunks in a local database. Realtime indexing and daemon mode can continue watching project files after the initial MCP connection. Code research and web search tools require embedding, reranking, and LLM configuration and may invoke local CLIs or external model APIs depending on settings. Exclude generated files, vendored dependencies, secrets, large artifacts, and unrelated repositories before indexing broad workspace roots. Review MCP client configuration carefully when using an absolute project path in a global Claude Desktop config.CodeDB indexes local projects and exposes file tree, outline, search, symbol, caller, dependency, read, snapshot, project, and context tools to the MCP client. CodeDB's `codedb_edit` tool exists as a fallback editing tool and can create, replace, insert, delete, or modify files when used by a client without native edit tooling. The npm package runs a postinstall step that downloads a native binary from GitHub Releases; review package and release provenance in environments that restrict native binaries. Remote repo queries use the public `api.wiki.codes` service and should be treated as network access outside the local repository. The upstream README marks the project as alpha software, with parser coverage and snapshot formats still stabilizing.The server requests the Google Search Console webmasters scope and can access every property available to the authenticated account. add_site, delete_site, and delete_sitemap are disabled by default and only run when GSC_ALLOW_DESTRUCTIVE is true. manage_sitemaps can submit or delete sitemaps depending on action and destructive settings. URL inspection and analytics tools can reveal indexing issues, search terms, landing pages, countries, devices, click-through rates, and ranking positions. Use least-privilege service accounts, avoid full-access credentials where read-only analysis is enough, and confirm exact site_url values with list_properties.
Privacy notesTool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings. Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree. File watcher status, exclude patterns, and settings can reveal local project layout and development conventions. If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine. Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing.Indexed chunks, file paths, symbols, comments, Markdown, PDFs, configuration values, database files, daemon state, and search results can reveal proprietary source code and internal architecture. Embedding, reranking, LLM, and web search providers may receive code-derived queries or snippets if configured. Local ChunkHound database files, logs, daemon state, and MCP transcripts may retain code-derived context after the session ends. Avoid sharing ChunkHound databases, config files with API keys, verbose logs, research outputs, and screenshots from private repositories.Local indexes, snapshots, file trees, symbol names, dependency graphs, snippets, read results, and search results can reveal proprietary code structure and implementation details. Upstream documents sensitive-file blocking for patterns such as environment files, credentials, and keys, but users should still review ignore rules and avoid indexing secret-heavy directories. CodeDB writes telemetry to `~/.codedb/telemetry.ndjson` unless `CODEDB_NO_TELEMETRY=1` is set, then syncs aggregate tool counts, latency, startup, file count, line count, language, version, and platform data on MCP session close. Upstream telemetry docs state that source code, file contents, file paths, and search queries are not collected. Remote public-repo queries and local MCP responses may still be logged by MCP clients, model providers, and terminal history.OAuth client secrets, service account JSON, cached token files, Search Console properties, page URLs, query terms, sitemap URLs, countries, devices, clicks, impressions, CTR, and positions can be sensitive. The server stores OAuth tokens under a user config directory unless GSC_CONFIG_DIR is changed. Service account files and OAuth tokens must stay out of prompts, issue comments, logs, screenshots, and repository files. Redact property URLs, query data, page URLs, tokens, credential file paths, and inspection results before sharing MCP transcripts.
Prerequisites
  • Python 3.10 or newer.
  • uv or another Python package runner that can install `code-index-mcp`.
  • An approved repository path that the MCP client is allowed to inspect.
  • Optional native search tools such as ripgrep, ugrep, ag, or grep for faster search backends.
  • Python 3.10 or newer and the `uv` package manager.
  • A local repository or workspace you are authorized to index.
  • ChunkHound JSON config reviewed for database path, excludes, embeddings, and LLM provider settings.
  • Optional embedding provider credentials for semantic search, or regex-only usage when no embedding key is configured.
  • macOS or Linux on x64 or arm64 for the published native binary launcher.
  • Node.js 18 or newer when using the `codedeebee` npm launcher.
  • A local project directory that the MCP client exposes through roots or launches from.
  • Review of which local repositories, file types, generated artifacts, and secrets patterns may be indexed.
  • Google Cloud project with the Search Console API enabled.
  • OAuth desktop client secrets JSON or service account JSON stored outside the repository.
  • Google Search Console properties where the authenticated user or service account has access.
  • MCP client that can run uvx or a local Python clone.
Install
uvx code-index-mcp --project-path ABSOLUTE_PATH_TO_REPOSITORY
uv tool install chunkhound
npx -y codedeebee mcp
Run `uvx mcp-search-console` with either `GSC_OAUTH_CLIENT_SECRETS_FILE` for OAuth or `GSC_CREDENTIALS_PATH` plus `GSC_SKIP_OAUTH=true` for a service account.
Config
Manual-only setup:
uvx code-index-mcp --project-path ABSOLUTE_PATH_TO_REPOSITORY
{
  "mcpServers": {
    "chunkhound": {
      "command": "chunkhound",
      "args": ["mcp", "/path/to/approved/project"]
    }
  }
}
{
  "mcpServers": {
    "codedb": {
      "command": "npx",
      "args": [
        "-y",
        "codedeebee",
        "mcp"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
GSC_OAUTH_CLIENT_SECRETS_FILE=<absolute-path-to-client-secrets-json>
GSC_CREDENTIALS_PATH=<absolute-path-to-service-account-json>
GSC_SKIP_OAUTH=true
GSC_ALLOW_DESTRUCTIVE=false
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.