CodeMeridian.Indexer 1.0.11

CodeMeridian Indexer

CodeMeridian.Indexer is the unified CLI for indexing code into CodeMeridian from C#, TypeScript/TSX, and documentation sources.

Install

dotnet tool install -g CodeMeridian.Indexer

Use

The indexer sends data to a running CodeMeridian backend. To create local MCP client config and start Neo4j plus the MCP server with Docker Compose:

codemeridian serve

codemeridian index .
codemeridian index C:\Projects\MyApp --project MyApp --clear
codemeridian index . --skip-csharp --skip-docs --skip-diagnostics
codemeridian index . --watch
codemeridian init .
codemeridian serve --no-start
codemeridian doctor --project CodeMeridian
codemeridian check-drift --project CodeMeridian --fail-on high

What It Does

• Detects C# projects, TypeScript/TSX roots, and documentation files.
• Indexes code into Neo4j through CodeMeridian.
• Skips unchanged files after the first successful run using .meridian/cache.
• Can run compiler, TypeScript, and lint diagnostics unless you skip them.
• Repo-controlled build and lint diagnostics are opt-in via --allow-repo-scripts.
• Can query the backend for a doctor status report without talking to Neo4j directly from the client.
• Can verify graph drift with codemeridian check-drift or codemeridian index --verify.
• Can create local MCP client config and start the backend stack with codemeridian serve.
• Supports dry runs and capability listing for environment checks.
• Can generate a local meridian.json and MCP client config with an auto-detected project name.
• Can also read CodeMeridian_Project from .env when you want a fixed project name without --project.

Package Contents

• LICENSE
• This readme
• The bundled TypeScript indexer assets

Notes

• Use --project <name> when you want a stable project context.
• Use CodeMeridian_Project in .env when you want the same project context applied automatically.
• Use codemeridian doctor --project <name> to ask the backend for graph health, drift, and counts.
• Use codemeridian check-drift --project <name> --fail-on high for a drift gate that exits non-zero in CI when the graph is too stale.
• Use codemeridian index --verify --project <name> when you want the same drift gate as part of an indexer workflow.
• Use --skip-diagnostics if you only want structural indexing.
• Use --allow-repo-scripts only on trusted repos when you want dotnet build and repo lint commands to run.
• Use --no-incremental or --force-full to scan all files without clearing the project.
• Use codemeridian init . to generate meridian.json, .vscode/mcp.json, and .codex/config.toml for a project. The generated meridian.json enables allowRepoScripts by default for trusted repos.
• Use codemeridian init --global --url http://localhost:5100 to create a user-level fallback config when you want the CLI to work across many repos without project-local config.
• Use codemeridian serve to create .env, .vscode/mcp.json, .codex/config.toml, and docker-compose.codemeridian.yml, then start the backend stack.
• Use codemeridian serve --no-start when you only want to write or merge those files.
• The global tool does not include Neo4j. It starts Neo4j and the MCP server through Docker using the published MCP server image.
• The repo-level README covers the full CodeMeridian product and architecture.