Alcove
About
Alcove gives AI coding agents on-demand access to your private project documentation — without dumping everything into the context window.
Details
- Author
- epicsagas
- Downloads
- 175
- Categories
- Other
Jump to
- 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
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
AlcoveCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"alcove": {
"alcove": {
"command": "alcove",
"args": []
}
}
}
}McpServers
{
"alcove": {
"command": "alcove",
"args": []
}
}How Alcove solves this
Alcove doesn't inject your docs. Agents search for what they need, when they need it.
~/projects/my-app $ claude "how is auth implemented?"
→ Alcove detects project: my-app
→ BM25 search: "auth" → ARCHITECTURE.md (score: 0.94), DECISIONS.md (score: 0.71)
→ Agent gets the 2 most relevant docs, not all 12
~/projects/my-api $ codex "review the API design"
→ Alcove detects project: my-api
→ Same doc structure, same access pattern
→ Different project, zero reconfiguration
Switch agents anytime. Switch projects anytime. The document layer stays standardized.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
