THE INSTALLATION GUIDE
A home for your
agent’s memory.
Start your server, connect an agent, and save something worth remembering. Here’s everything you need to put down the first roots.
- 01
Give your memories a home.
Sign in to your Grove deployment and install the client with npm. Self-hosting? Compose starts the API, worker, and private PostgreSQL.
macOS, Linux, or Windows with DockerDocker setupgit clone https://github.com/miniaxolotl/grove.git cd grove cp .env.example .env # Set Grove Clerk keys and generated passwords in .env docker compose up -d --buildRequires Git, Docker Compose, and a configured Grove Clerk application. Set the keys and generated passwords before starting. The first run downloads the local embedding model.
npm setupnpm install -g @miniaxolotl/grove grove init --client opencode --url https://api.usegrove.cloud grove status --client opencode --jsonRequires Node.js 22+. Connects to hosted Grove; self-hosted users can substitute their API origin. Use --client claude or --client codex for those agents. Approve the connection in your dashboard.
Check that Grove is ready
Readiness checkcurl --fail http://localhost:26080/health/readyWait for initialization to finish. The readiness endpoint returns HTTP 200 after the database and configured embedding model are ready.
- 02
Make the connection.
Give your agent access to Grove’s MCP tools. Use the OpenCode configuration, or connect your preferred MCP client.
Client configuration referenceopencode.json{ "$schema": "https://opencode.ai/config.json", "plugins": ["@miniaxolotl/grove-opencode-plugin"] }Grove init merges this entry into OpenCode V2 configuration. The plugin adds four memory tools and bounded context recall. Run grove project after approving project access to resolve the same repository identity across agents and worktrees.
Streamable HTTP endpointhttps://api.usegrove.cloud/mcpAdd a remote MCP server named
grovewith this URL and the Streamable HTTP transport. Configuration fields vary by client. Self-hosted users can substitute their API origin. Sign in with OAuth or provide a named, scoped API key.Prefer stdio? Install the npm package and configure your client to launch
grove mcp --stdioafter running grove login. The bridge and hooks share the same Grove-managed connection. Plant your first memory.
Ask your agent to save something worth keeping. Open a new session, search for it, and pick up the thread.
Ask your agent to rememberUse Grove to remember this confirmed decision in my current project: "We use PostgreSQL for billing because we need transactions."Then, in a new session
Ask your agent to recallRecall our billing database decision from Grove for this project. What did we decide, and why?Grove makes memory available through tools. Ask your agent to use them, or add saving and recall instructions to your agent’s workflow.
Ready to grow from here?
Explore the four memory tools, manage connections in your dashboard, or set up Grove on your own server.