Local code-search MCP server for agents, using CPU-only hybrid retrieval to index repositories and return focused snippets for natural-language queries.
Semble indexes local paths or remote git repositories and returns code chunks through MCP tools., The interactive installer can modify agent configuration files, instruction files, and sub-agent files for supported clients., In MCP mode, local paths can be watched for file changes and re-indexed automatically., Remote repository search accepts git URLs and clones or indexes source on demand., Cached indexes and usage statistics can persist after the MCP session ends.
Privacy notes
Source code, filenames, directory structure, snippets, documentation, configuration files, search queries, related-code requests, cache keys, and tool results may be visible to the MCP client and model provider., Using `--content docs`, `--content config`, or `--content all` can include README files, deployment notes, YAML/TOML files, credentials accidentally present in config, and internal runbooks., Persistent cache data may reveal repository names, paths, symbols, comments, and source-derived chunks., Review `.gitignore` and `.sembleignore` coverage before indexing workspaces that contain generated files, vendored code, secrets, customer data, or unrelated private repositories.
Author
MinishLab
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
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.
5 safety and 4 privacy notes across 3 risk areas. Review closely: credentials & tokens, network access.
3 areas
SafetyNetwork accessSemble indexes local paths or remote git repositories and returns code chunks through MCP tools.
SafetyLocal filesThe interactive installer can modify agent configuration files, instruction files, and sub-agent files for supported clients.
SafetyLocal filesIn MCP mode, local paths can be watched for file changes and re-indexed automatically.
SafetyNetwork accessRemote repository search accepts git URLs and clones or indexes source on demand.
SafetyCredentials & tokensCached indexes and usage statistics can persist after the MCP session ends.
PrivacyNetwork accessSource code, filenames, directory structure, snippets, documentation, configuration files, search queries, related-code requests, cache keys, and tool results may be visible to the MCP client and model provider.
PrivacyCredentials & tokensUsing `--content docs`, `--content config`, or `--content all` can include README files, deployment notes, YAML/TOML files, credentials accidentally present in config, and internal runbooks.
PrivacyLocal filesPersistent cache data may reveal repository names, paths, symbols, comments, and source-derived chunks.
PrivacyCredentials & tokensReview `.gitignore` and `.sembleignore` coverage before indexing workspaces that contain generated files, vendored code, secrets, customer data, or unrelated private repositories.
Safety notes
Semble indexes local paths or remote git repositories and returns code chunks through MCP tools.
The interactive installer can modify agent configuration files, instruction files, and sub-agent files for supported clients.
In MCP mode, local paths can be watched for file changes and re-indexed automatically.
Remote repository search accepts git URLs and clones or indexes source on demand.
Cached indexes and usage statistics can persist after the MCP session ends.
Privacy notes
Source code, filenames, directory structure, snippets, documentation, configuration files, search queries, related-code requests, cache keys, and tool results may be visible to the MCP client and model provider.
Using `--content docs`, `--content config`, or `--content all` can include README files, deployment notes, YAML/TOML files, credentials accidentally present in config, and internal runbooks.
Persistent cache data may reveal repository names, paths, symbols, comments, and source-derived chunks.
Review `.gitignore` and `.sembleignore` coverage before indexing workspaces that contain generated files, vendored code, secrets, customer data, or unrelated private repositories.
Prerequisites
Python 3.10 or newer and uv available to the MCP client runtime.
A local repository or remote git repository you are authorized to index.
Approval before the interactive installer modifies MCP client configs, AGENTS.md, CLAUDE.md, or sub-agent files.
Cache location and retention reviewed before indexing proprietary repositories.
Optional `--content docs`, `--content config`, or `--content all` scope chosen deliberately for sensitive projects.
Semble is a local-first code-search MCP server for coding agents. It indexes
local paths or remote git repositories and exposes focused search results
through MCP instead of making Claude grep broadly and read entire files.
The MCP server provides search for natural-language or code queries and
find_related for finding chunks similar to a known file and line. The project
uses CPU-only hybrid retrieval with static code embeddings, BM25, tree-sitter
chunking, and reranking. Indexes are cached and local repositories can be
watched for automatic re-indexing during an MCP session.
These sources were reviewed on 2026-06-05. Prefer the live repository,
README, installation guide, Python project metadata, MCP server implementation,
cache implementation, benchmark notes, license, and PyPI metadata for current
commands, package versions, supported clients, tool behavior, cache behavior,
and benchmark claims.
Features
Search local repositories by natural-language or code query.
Search remote git repositories by passing an explicit repository URL.
Find code chunks related to a file path and line number from a prior result.
Cache indexes on disk for faster repeat queries.
Watch local paths in MCP mode and rebuild indexes after file changes.
Index code by default, with optional documentation, configuration, or all-file scopes.
Use .gitignore and .sembleignore rules to control indexed files.
Install MCP configs, usage instructions, or a dedicated search sub-agent for supported clients.
Run on CPU without requiring API keys, GPUs, or external vector services.
Installation
The recommended installer uses uv:
uv tool install semble
semble install
For manual MCP setup, configure the server to launch through uvx:
To include documentation, configuration, or every supported file type, append
--content docs, --content config, or --content all to the server command.
Use Cases
Ask Claude where a feature is implemented without loading every matched file.
Search unfamiliar repositories by behavior, API name, or architecture concept.
Find related implementations after inspecting one relevant search result.
Let a coding agent query documentation and config only when that scope is approved.
Add AGENTS.md or CLAUDE.md guidance so agents prefer Semble before broad grep/read.
Install a dedicated semble-search sub-agent in harnesses that support sub-agents.
Safety and Privacy
Semble is intentionally close to source code. It can index local repositories,
clone or index remote git repositories, persist cache data, and return source
chunks to the MCP client. Scope each search to repositories you are authorized
to expose to an AI assistant.
Use .gitignore and .sembleignore to exclude generated files, vendored code,
secrets, private fixtures, and unrelated projects. Treat caches and usage
statistics as source-derived artifacts, especially when using documentation,
configuration, or all-file indexing modes.
Duplicate Check
No MinishLab/semble entry, semble PyPI package entry, or matching source URL
was found in content/mcp.
Show that Semble MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/semble-mcp-server)
How it compares
Semble MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Local code-search MCP server for agents, using CPU-only hybrid retrieval to index repositories and return focused snippets for natural-language queries.
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.
✓Semble indexes local paths or remote git repositories and returns code chunks through MCP tools.
The interactive installer can modify agent configuration files, instruction files, and sub-agent files for supported clients.
In MCP mode, local paths can be watched for file changes and re-indexed automatically.
Remote repository search accepts git URLs and clones or indexes source on demand.
Cached indexes and usage statistics can persist after the MCP session ends.
✓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.
✓Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes.
The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving.
Static analysis tools may invoke local compilers, linters, or language tools depending on the repository.
Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends.
External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.
✓Searchcode analyzes public repositories through a hosted remote service; do not point it at private repository URLs unless you have a private/enterprise arrangement and have reviewed the current access controls.
The service can return code snippets, file contents, symbols, file trees, static-analysis findings, and credential-scan findings from public repositories.
Treat tool results as machine-assisted code intelligence. Confirm security findings, complexity claims, and dependency conclusions against the repository before making merge, hiring, acquisition, or incident decisions.
Large or repeated repository analysis can create automated traffic to Searchcode; keep agent loops bounded and avoid broad unattended scans.
Privacy notes
✓Source code, filenames, directory structure, snippets, documentation, configuration files, search queries, related-code requests, cache keys, and tool results may be visible to the MCP client and model provider.
Using `--content docs`, `--content config`, or `--content all` can include README files, deployment notes, YAML/TOML files, credentials accidentally present in config, and internal runbooks.
Persistent cache data may reveal repository names, paths, symbols, comments, and source-derived chunks.
Review `.gitignore` and `.sembleignore` coverage before indexing workspaces that contain generated files, vendored code, secrets, customer data, or unrelated private repositories.
✓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.
✓Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider.
Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans.
Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts.
Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.
✓Prompts and tool inputs can reveal which public repositories, symbols, files, dependencies, security concerns, or candidate portfolios a team is investigating.
Returned code snippets, findings, file paths, and repository metadata become part of the MCP client transcript and may be processed by the connected model provider.
Public code can still contain secrets, personal data, proprietary code accidentally committed upstream, or prompt-injection text. Review returned snippets before forwarding them into other tools or reports.
Searchcode's public page says the hosted MCP server is free during beta and does not require signup or an API key; review the live site before production use because pricing and private-code options may change.
Prerequisites
Python 3.10 or newer and uv available to the MCP client runtime.
A local repository or remote git repository you are authorized to index.
Approval before the interactive installer modifies MCP client configs, AGENTS.md, CLAUDE.md, or sub-agent files.
Cache location and retention reviewed before indexing proprietary repositories.
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.
Node.js and npx available to the MCP client runtime.
A repository or workspace you are authorized to index and expose to an MCP client.
Ollama embedding model available, or an approved OpenAI-compatible embedding provider and API key.
Static analysis tools installed if you want Context+ to run native linters or compilers.
MCP client with remote Streamable HTTP support, or `mcp-remote` for clients that still need a stdio bridge.
Public Git repository URLs or `owner/repo` names for the repositories Claude should inspect.
Team agreement that public repository metadata, code snippets, file paths, and static-analysis results may be sent through a hosted third-party MCP service.
Client-side policy for whether model-generated findings should be treated as triage hints or reviewed security results.
Install
uv tool install semble && semble install
uv tool install chunkhound
npx -y contextplus
claude mcp add searchcode --transport http https://api.searchcode.com/v1/mcp