Integration proposal: Semble MCP code-search companion (auto-drafted 2026-06-22)

[NativeTeachingAidsB]

Auto-generated by weekly-landscape-scan routine (2026-06-22). DRAFT — needs human review. Labels to add: integration-proposal, auto-generated
Score: 10

What is Semble?

Semble (github.com/MinishLab/semble) is an MCP code-search server that indexes a codebase and returns exact code snippets to AI agents using ~98% fewer tokens than grep+read, at 99% of retrieval quality of a 137M-parameter code-trained transformer. 5,400 stars, 231 forks, v0.4.0 released June 20, 2026. MIT licensed, CPU-only, no API keys.

It installs into Claude Code, Cursor, Codex, OpenCode, and any MCP-compatible agent — exactly the same set codetalker targets.

Integration opportunity

Semble and codetalker are natural co-residents in the same MCP server list — both are stdio servers, no conflicts. Co-documenting them increases codetalker's discoverability among Semble's growing user base.

Minimum effort: add a "paired with Semble" callout and config snippet to docs/integrations/claude-code.md.

Optional: document an agent prompt that narrates Semble search results via tts_speak.

Combined config example

{
  "mcpServers": {
    "codetalker": { "command": "codetalker-mcp", "args": [] },
    "semble":     { "command": "uvx", "args": ["semble"] }
  }
}

Full draft spec

See docs/superpowers/specs/2026-06-22-integrate-semble.md on branch docs/landscape-report-2026-06-22.

Open questions

• Is there value in narrating Semble search results (noisy?) or just document co-install?
• Should codetalker maintain a "companion MCP tools" section in the integration README?