Local code intelligence MCP server for AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"seam-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Seam Local code intelligence MCP server for AI agents. Index your codebase once; let agents query instead of grep. ## Status Semantic search shipped (opt-in local embeddings, hybrid FTS5+cosine via RRF, `[semantic]` extra, no network at query time). Phase 10 complete — Swift support (11 → 12 languages); Kotlin deferred (grammar maturity). Agentic-readiness hardening done (MCP error/not-found contract, `.seam/` gitignore, distribution → `seam-mcp`). `seam install` ships — one-command MCP wiring for Claude Code / Cursor / Codex. Full CLI-only surface (`query`/`search`/`context` + analysis commands) usable with no MCP server. 1747 tests. Gate green. ## Quickstart Not yet published to PyPI (the name `seam` there belongs to an unrelated package; the distribution will be `seam-mcp`). Install from source for now: Not yet published to PyPI (the distribution will be `seam-mcp`; the import package and `seam` command keep that name). Install from source for now: ```bash git clone <repo-url> && cd seam uv sync # CLI only (no MCP server, no semantic search) uv sync --extra server # add the MCP server (`seam start`) — needs the `mcp` package uv sync --extra semantic # add semantic search (fastembed, ONNX on CPU, no torch, ~67 MB model on first run) # or install everything: uv sync --extra server --extra semantic ``` The **MCP server is optional**. The CLI works on its own — these all query the index directly, no server needed: ```bash cd /path/to/your/project uv run seam init # index the project uv run seam search "auth token" # full-text search uv run seam query "verify user login" # hybrid FTS + graph search uv run seam context authenticate_user # 360-degree view of a symbol uv run seam impact authenticate_user # blast radius # also: trace · changes · why · clusters · affected · pack · status · sync ``` To expose Seam to an AI agent, install the `server` extra and let `seam install` write the MCP config for …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.