> For the complete documentation index, see [llms.txt](https://docs-gerber.romain-ecarnot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-gerber.romain-ecarnot.com/readme.md).
# README
Gerber
Cross-project orchestration MCP server for AI coding agents.
Tasks, issues, inter-session messages, handoffs, runbooks.
Knowledge memory delegated to the Gemini vault RAG.
One brain, every agent.
***
### Features
* **Tasks** — 7-column kanban (inbox → done) with subtasks, priorities, due dates
* **Issues** — Bug tracking with severity levels and 4-column workflow
* **Messages** — Inter-session bus for context and reminders between projects
* **Handoffs** — Session context transfer between Claude environments (CLI, Desktop, claude.ai, mobile)
* **Runbooks** — Per-project `run_cmd`/`url`/`env` with detached process tracking
* **Vault RAG** — Cross-project knowledge search via Gemini FileSearchStore + GitHub ground-truth (`rag` tool)
* **Multi-client** — Claude Code, Claude Desktop, Gemini CLI, Codex, OpenCode, Kilo Code, Cline
### Screenshots
| Tasks kanban | Issues board |
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
|  |  |
### Quick Install (Claude Code)
Starting with v2.0.0, gerber ships as a **remote MCP** hosted on a private VPS — no local install, no `pnpm build`.
```
/plugin install gerber@erom-marketplace
/reload-plugins
/gerber:onboarding
```
`/gerber:onboarding` will prompt for a bearer token (single-user, single-instance) and persist it in `~/.claude/settings.local.json` so the bundled `.mcp.json` can authenticate against `https://gerber.romain-ecarnot.com/mcp/stream`.
If you want to run the MCP server locally instead, clone the repo and follow the legacy stdio pattern from v1.x — but the plugin's `.mcp.json` is now hard-wired to the remote URL.
### Documentation
[**Read the full documentation →**](https://docs-gerber.romain-ecarnot.com)
Covers installation for all clients, tools reference (31 MCP tools), plugin setup (skills, agents), deployment (HTTP, Claude Managed Agent), architecture, and contributing guide.
### License
MIT
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs-gerber.romain-ecarnot.com/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
