Skip to main content
Glama
sangingeum

mcp-code-indexer

by sangingeum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STALE_TTLNoSeconds between staleness re-scans60
INDEX_ROOTNoState directory~/.mcp-code-indexer
OLLAMA_URLNoOllama base URLhttp://192.168.X.X:11434
QDRANT_URLNoQdrant base URLhttp://192.168.X.X:6333
EMBED_BATCHNoTexts per Ollama embed request48
EMBED_MODELNoEmbedding modelqwen3-embedding:8b
UPSERT_BATCHNoPoints per Qdrant upsert256
MAX_FILE_BYTESNoSkip files larger than this1048576

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_projectA

Register an absolute project directory for semantic indexing.

Creates the Qdrant collection and starts a full initial index in the
background (check progress with index_status). Errors if the path does
not exist or is already registered.
remove_projectA

Deregister a project and DELETE its Qdrant collection + manifest + registry entry entirely.

list_projectsA

List registered projects with per-project index summary and staleness.

semantic_searchA

Semantic code search across indexed projects. THE hot path.

Automatically runs a staleness check first and incrementally re-indexes
changed files, so results are always fresh (within one scan interval).
Args: query (natural language); project (optional path — omit to search
all registered projects); limit; file_filter (optional substring/glob
on file path, e.g. '*.py').
index_statusA

Check indexing state for a project: idle | indexing | stale | error, plus last-pass progress. Also triggers the staleness check.

reindex_projectA

Force a full rebuild of a project's index (chunker/model change, suspected corruption).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add_project registers, remove_project deregisters, list_projects lists, semantic_search searches, index_status checks status, and reindex_project forces rebuild. No overlapping or ambiguous functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (add_project, remove_project, list_projects, semantic_search, index_status, reindex_project) with snake_case throughout.

Tool Count5/5

Six tools perfectly cover the lifecycle of project management and indexing for a code indexer: add, remove, list, search, status, and reindex. No tool is extraneous or missing.

Completeness5/5

The tool set provides complete CRUD for projects (add, remove, list) plus essential operations for indexing and searching (semantic_search, index_status, reindex_project). This covers all core workflows for a code indexer.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources