Semble
Open-source code search for AI agents that cuts token use by ~98% on CPU.
Semble delivers on its promise of fast, private, and token-cheap code search for AI agents. If you use coding agents and want to cut token costs without sacrificing retrieval quality, it's a strong open-source bet. But skip it if you need a managed SaaS with dashboards, access controls, or real-time indexing — those are out of scope.
Verified 3d ago · liveness 67/100 · cite: rightaichoice.com/tools/semble
- Developers using AI coding agents who want instant code navigation without full-file reads
- Teams needing local, private code search with no external API calls or cloud dependencies
- Agent builders integrating code retrieval into MCP workflows for token-efficient access
- Solo devs who want to reduce token costs and latency when querying large repos
- Users who need a cloud-hosted, managed code search service with a web dashboard
- Teams that require granular access control, permissions, or audit logging
- Use cases demanding real-time indexing of frequently changing repos
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Semble if you need a managed, cloud-hosted code search with dashboards, access controls, or real-time indexing — it's a local library, not a SaaS.
Requires uv and Python environment setup, which may add friction for non-Python developers.
Semble is free and open-source (MIT), making it the most cost-effective option for developers and small teams who want token-efficient code search without per-seat fees. Compared to managed RAG services or cloud code search tools that charge per GB or per query, Semble has zero ongoing costs.
In short
Semble — Open-source code search for AI agents that cuts token use by ~98% on CPU. Best for Developers using AI coding agents who want instant code navigation without full-file reads, Teams needing local, private code search with no external API calls or cloud dependencies, Agent builders integrating code retrieval into MCP workflows for token-efficient access. Free to use.
What people actually say about Semble — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
41 mentions across 4 sources (Hacker News, Product Hunt, GitHub, Lemmy) · researched Jul 3, 2026.
- +Near-instant indexing: 250ms for an average repo, faster than alternatives.
- +Query latency of ~1.5ms — snappy even on large codebases.
- +Claims 98% fewer tokens than grep+read, with verifiable savings per repo.
- +Zero-setup: runs on CPU, no API keys, no GPU required.
- +Natural-language code search with semantic + lexical hybrid retrieval.
- −MCP integration hangs on Codex-cli and other agents, causing frustration.
- −First-run session can deadlock on Windows 10 for up to 20 minutes.
- −No agent-level benchmarks to support the 98% token savings claim.
- −Custom tree-sitter grammars not supported, limiting language coverage.
- −Requires arcane instructions to coerce Claude Code into compliance.
- • No hidden costs, but token consumption from storing index on disk may affect disk space on very large repos
Viability Score
How well maintained and how widely used is Semble? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: August 2026
How we score →Key Features
- Natural-language code search
- Code-aware chunking via tree-sitter
- Static Model2Vec embeddings with potion-code-16M
- BM25 lexical retrieval for identifiers and APIs
- Reciprocal Rank Fusion of semantic and lexical scores
- Adaptive weighting for symbol-like vs. natural-language queries
- Definition boosts for defining vs. referencing chunks
- Identifier stem matching (e.g., 'parse config' matches 'parseConfig')
- File coherence reranking
- Noise penalties for test files, legacy code, and stubs
- Indexes local paths and git URLs
- MCP tools: search and find_related
- Zero-setup install via 'semble install'
- Runs entirely on CPU, milliseconds per query
- Uninstall via 'semble uninstall'
About Semble
Semble is an open-source code search library built specifically for AI coding agents. It lets agents like Claude Code, Cursor, Codex, OpenCode, and Gemini ask questions in natural language (e.g., "How is authentication handled?") and receive only the relevant code snippets — no grepping, no reading entire files. This replaces the traditional grep-and-read workflow with a token-efficient retrieval that can index an average repository in about 250 ms and answer queries in roughly 1.5 ms, all on CPU. Under the hood, Semble splits code into tree-sitter–aware chunks and scores them with a hybrid approach: static Model2Vec embeddings (using the code-specialized potion-code-16M model) for semantic similarity, plus BM25 for lexical matches on identifiers and APIs. The two lists are fused via Reciprocal Rank Fusion, then reranked with code-aware signals like definition boosts, identifier stem matching, file coherence, and noise penalties for test or legacy files. The result is retrieval quality on par with larger code-specialized transformer models — an NDCG@10 of 0.854 on benchmarks — at a fraction of the size and cost. Semble runs entirely on CPU with zero external dependencies. No API keys, GPU, or cloud services required. You can use it as an MCP server, a CLI tool via AGENTS.md, or a dedicated sub-agent. The interactive installer, `semble install`, detects your installed coding agents and lets you enable the integrations you want. It also supports indexing both local paths and git URLs, and offers two MCP tools: `search` and `find_related`. For developers and teams who want fast, private, and token-efficient code search without sending code to a cloud service, Semble is a lightweight local alternative to managed RAG setups. It's MIT-licensed and open source, so you can inspect, modify, and self-host it as you see fit.
Behind the Verdict
Semble addresses a real pain point for developers using AI coding agents: the token-expensive, slow grep-and-read workflow. By returning only the relevant code snippets, it dramatically reduces token consumption and latency. The hybrid retrieval approach combining static embeddings and BM25 with RRF is clever and effective, hitting an NDCG@10 of 0.854 on benchmarks. The zero-setup installer and MCP integration make it accessible to a wide range of agents. Its main weakness is that it's a local library, not a managed service — so teams looking for centralized access control, audit logs, or real-time indexing will need to build those themselves. It's also not suited for non-developers or those who need a web UI. Overall, for developers and teams prioritizing privacy, speed, and cost-efficiency in code search, Semble is a compelling open-source choice.
Researching Semble? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Semble actually fits — and what changes day-one when you adopt it.
Install Semble with 'uv tool install semble' and 'semble install' to enable MCP integration with Claude Code.
Outcome: Ask natural-language questions like 'How is auth handled?' and get relevant snippets instantly, saving token usage and time.
Set up Semble as an MCP server for Cursor and share the AGENTS.md snippet with the team.
Outcome: Team members ask natural-language queries and retrieve code without manual grepping, improving onboarding and productivity.
Index a git URL of a popular repo and enable the MCP tools for contributors.
Outcome: Contributors quickly find relevant code, reducing friction and improving contribution quality.
Use Cases
- Search a large codebase with natural language questions like 'How is authentication handled?'
- Find related code given a specific file location using find_related MCP tool
- Integrate code retrieval into Claude Code or Cursor via MCP server
- Index a git repository by URL and query it without cloning manually
- Reduce token usage in agent workflows by returning only relevant snippets
Models Under the Hood
as of 2026-08-31
Limitations
- Semble is a code search library that runs locally on CPU, requiring no API keys, GPU, or external services.
- It integrates with coding agents via an MCP server, CLI instructions in AGENTS.md, or a dedicated sub-agent, and is installed using the command 'uv tool install semble' followed by 'semble install'.
- It returns only relevant code snippets, reducing token usage by approximately 98% compared to grep+read, with fast indexing and query times.
as of 2026-08-24
Verification history
We have re-verified Semble 6 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Semble tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0
Ideal for
Developers and teams who want a free, self-hosted code search solution with full control and privacy.
What this tier adds
Free and open-source under MIT license; includes all features, no paywall.
Where the pricing makes sense
The company stage and team size where Semble's pricing actually pencils out — and where peers do it cheaper.
Semble is free and open-source (MIT), making it the most cost-effective option for developers and small teams who want token-efficient code search without per-seat fees. Compared to managed RAG services or cloud code search tools that charge per GB or per query, Semble has zero ongoing costs.
Setup time & first value
How long it actually takes to get something useful out of Semble — broken out by persona, not the marketing-page minute.
Most developers can get Semble running within 5–10 minutes: install uv, then run 'uv tool install semble' and 'semble install' to automatically configure MCP, CLI, and sub-agent integrations.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Semble
Common stack mates teams adopt alongside Semble, with the specific reason each pairing earns its keep.
agentcad
Open-source MCP server for AI agents to design, render, and export 3D CAD parts via code
Bito
AI model router and code context engine that cuts agent token spend by grounding requests in your codebase and routing to right-sized
MarsX
Open-source dev platform uniting AI, NoCode, Code, and reusable MicroApps.
Featured Head-to-Head Comparisons
Semble vs Spider Cloud
These tools aren't direct competitors: Spider Cloud excels at web data extraction for AI/LLM pipelines, while Semble is a local code search library for AI coding agents. Choose based on your data source—web or code.
Semble vs Voyage Ai
If you need high-accuracy retrieval on enterprise documents with domain-specific models and compliance, Voyage AI is the clear choice—but be prepared for enterprise pricing. For developers building AI coding agents that need instant, local, and token-cheap code search, Semble is a fantastic free tool that integrates seamlessly with popular IDEs and MCP workflows. Choose based on your primary use case: documents vs. code.
Semble vs Temporal Ai
Choose Temporal if you need robust, durable orchestration for AI agents or microservices that survive failures and require human-in-the-loop; choose Semble if you mainly want to supercharge your AI coding agent with instant, token-efficient code search. They solve different problems — Temporal is a workflow engine, Semble is a code retrieval library — so the right choice depends on whether your bottleneck is reliability or context window limits.
Alternatives to Semble
View allFrequently Asked Questions
Best-of guides
Used Semble? Help shape our editorial sentiment research.


