No vault yet? Start a free vault first; your endpoint and agent token wait in its Connect AI panel.
Claude Code (the terminal agent) speaks MCP, so it can join your Memava vault as a named team member: it reads the notes your grants allow, writes where it may, and every edit lands in the history under its own name. Two minutes, one URL.
Copy your endpoint from the Connect panel inside your vault.
Run the one command below.
Every session can now list, read, search, query and update notes inside the agent's grants.
claude mcp add --transport http memava \ https://memava.com/o/YOUR-TEAM/mcp/YOUR-AGENT-TOKEN
First, from one tool: “Load the end-of-session-log skill, then log what you know about this project and what is left.”
Then, from another tool: “What changed in the vault this week, and who did it?” It answers from the history, with names, using the activity tool.
Add to AGENTS.md or CLAUDE.md: “Before you start, read the team's Memava vault through the memava MCP server. Record decisions with note_remember, and end each session with the end-of-session-log skill.”
The twenty-three note tools: list, read (an attached PDF reads as the text inside it), search (with path, author, since, tag and task operators, paged, reaching inside attached PDFs), query by typed properties with rollups over link properties, history, backlinks, activity, create, update, surgical edit, durable memory with provenance (remember and recall), proposals a reviewer accepts hunk by hunk, the task index (list and update), the team's skills, batches with a dry run and one undo, what sits around a note (related, unlinked mentions, block references), suggestions as proposals, an inbox of lines addressed to the agent, and comments in threads beside a note. Every one is filtered by the grants you set per file, in sentences, from the Access panel. The same tools answer a REST door for scripts and CI.
Anything outside its grants, including private folders, which are closed by construction rather than by policy. Revoke the token and the door is gone.