Semantica Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key for embedding generation using OpenAI provider. Only needed if using OpenAI provider. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| onboard_projectB | Complete onboarding for a new project: auto-detect language, create optimized config, install git hooks, and start initial indexing. One command to set everything up! |
| index_codebaseA | Index a codebase for semantic code search. Runs in BACKGROUND by default - returns immediately and you can check progress with get_index_status. Extracts functions, classes, and modules, generates embeddings, and stores in vector database. |
| search_codeA | Search the indexed codebase semantically using natural language. Returns relevant code chunks with similarity scores. |
| get_index_statusA | Get the current status of the indexed codebase. Shows LIVE PROGRESS if indexing is running in background, or collection statistics if idle. Use this to monitor long-running indexing jobs. |
| reindex_changed_filesA | Incrementally re-index only changed files (fast). Uses Merkle trees to auto-detect changes, or re-indexes specific files if provided. Much faster than full re-index. |
| enable_git_hooksB | Install git hooks for automatic re-indexing on git operations (branch switch, pull, merge). Makes index stay in sync automatically. |
| reset_stateA | Emergency reset: kills stuck re-index processes, removes stale locks, cleans up state files. Use this to fix issues like stuck indexing, lock conflicts, or corrupted state. |
| clear_indexB | Clear all indexed data from the vector database. This will delete the collection and all vectors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes (search, status, incremental reindex, hooks, reset, clear). There is mild overlap between onboard_project and index_codebase/enable_git_hooks since onboarding bundles both, and clear_index vs reset_state could be confused (data deletion vs stuck-process cleanup), but descriptions differentiate them well.
All eight tools use consistent snake_case verb_noun naming (onboard_project, index_codebase, search_code, get_index_status, reindex_changed_files, enable_git_hooks, reset_state, clear_index). No mixing of conventions or casing.
Eight tools is well-scoped for a semantic code search server, covering setup, indexing, search, monitoring, and maintenance without redundancy. Every tool earns its place.
The surface covers the full lifecycle: onboarding, indexing (full and incremental), search, status monitoring, git hooks, reset, and clearing. Minor gaps exist—no config get/update tool despite onboarding creating config, and no way to remove specific files without a full clear.