What is Alcove?
Alcove is an MCP server that gives AI coding agents on-demand access to your private project docs. It organizes documentation in a separate directory (one folder per project) and serves it to any MCP-compatible agent over stdio. Docs are never injected into the context window and never leak into public repositories. Built for developers who need agent access to architecture, decisions, runbooks, and PRDs without per-project configuration for every agent.
How to use Alcove?
Install via Homebrew on macOS (brew install epicsagas/alcove/alcove), cargo binstall alcove, cargo install alcove, or clone and make install. Run alcove setup for interactive configuration (docs location, document categories, agent setup). The MCP server starts with the alcove command (called by agents). Use CLI commands like alcove search, alcove validate, alcove doctor for local operations. Agents call tools such as search_project_docs and get_doc_file via stdio MCP.
Key features of Alcove
- On-demand doc retrieval — agents search, nothing pre-loaded into context
- BM25 ranked search (tantivy) with automatic grep fallback
- One doc-repo for multiple projects, organized by project folder
- Single setup works with any MCP-compatible agent
- Auto-detects project from current working directory
- Scoped access — each project only sees its own docs
- Cross-project search with
scope: "global"
- Standardized doc structure enforced via
policy.toml
- Document validation against team policy
Use cases of Alcove
- Give agents access to architecture docs without context bloat
- Search across all projects for patterns like authentication or rate limiting
- Enforce consistent documentation standards across a team
- Keep sensitive internal docs off your public GitHub repo
- Switch between projects and agents without reconfiguring doc access
コメント