Connect your agent.
One command wires MayaMemo into the agent you already use — MCP tools, checkpoints on every commit, resume briefings and a memory playbook. Switch agents any time; the context follows.
How it works
Three steps, about a minute — and the installer is idempotent, so re-run it any time.
Get a key
Sign up and mint a workspace key in the dashboard, or run mayamemo login. Agents can even self-register — no browser needed.
Run the installer
Inside your repo: npx -y @mayamemo/cli@latest install opencode — it creates the project, writes the config and installs git hooks.
Work and hand off
Every commit auto-checkpoints. When you switch tools, mayamemo checkpoint resume <id> --agent codex restores the working state.
Pick your agent
One command per tool. Everything is marker-based, visible and removable — nothing hidden.
opencode
MCP tools, a lifecycle plugin, git hooks and the AGENTS.md playbook — the deepest integration.
npx -y @mayamemo/cli@latest install opencodeClaude Code
MCP server in .mcp.json, a memory skill, git hooks and resume briefings in CLAUDE.md.
npx -y @mayamemo/cli@latest install claudeCursor
MCP server in .cursor/mcp.json plus always-on memory rules for every session.
npx -y @mayamemo/cli@latest install cursorCodex
MCP server in ~/.codex/config.toml, the AGENTS.md playbook and git hooks.
npx -y @mayamemo/cli@latest install codexAntigravity
Prints the agy mcp add command, wires git hooks and the AGENTS.md playbook.
npx -y @mayamemo/cli@latest install antigravityAny MCP client
Windsurf, Cline, Kimi, Zed, Hermes — anything that speaks MCP runs the same server.
npx -y @mayamemo/mcp@latestMultiple tools? npx -y @mayamemo/cli@latest install all — or one command per agent.
Hosted — no install
Point any MCP client at the hosted server. Auth is OAuth 2.1 with a browser sign-in, so there is no package to install and no key to paste.
https://mcp.mayamemo.com/mcpAdd it as a remote MCP server. The client opens a browser once to authorise your workspace; every tool is then scoped to it.
Manual setup
Prefer to wire it yourself? These are the exact entries the installer writes.
{
"mcp": {
"mayamemo": {
"type": "local",
"command": ["npx", "-y", "@mayamemo/mcp@latest"],
"environment": {
"MAYAMEMO_API_URL": "https://api.mayamemo.com",
"MAYAMEMO_TOKEN": "mm_sk_..."
},
"enabled": true,
"cwd": "."
}
}
}{
"mcpServers": {
"mayamemo": {
"command": "npx",
"args": ["-y", "@mayamemo/mcp@latest"],
"env": {
"MAYAMEMO_API_URL": "https://api.mayamemo.com",
"MAYAMEMO_TOKEN": "mm_sk_..."
}
}
}
}{
"mcpServers": {
"mayamemo": {
"command": "npx",
"args": ["-y", "@mayamemo/mcp@latest"],
"env": {
"MAYAMEMO_API_URL": "https://api.mayamemo.com",
"MAYAMEMO_TOKEN": "mm_sk_..."
}
}
}
}[mcp_servers.mayamemo]
command = "npx"
args = ["-y", "@mayamemo/mcp@latest"]
[mcp_servers.mayamemo.env]
MAYAMEMO_API_URL = "https://api.mayamemo.com"
MAYAMEMO_TOKEN = "mm_sk_..."agy mcp add mayamemo npx -y @mayamemo/mcp@latest
# then export MAYAMEMO_API_URL / MAYAMEMO_TOKEN in your shellexport MAYAMEMO_API_URL="https://api.mayamemo.com"
export MAYAMEMO_TOKEN="mm_sk_..."
npx -y @mayamemo/mcp@latestReplace mm_sk_… with a key from Dashboard → Connect. The same two env vars work in every host.
FAQ
Do I need a plugin for each agent?
No — MCP is the universal connector. Every tool above launches the same server (npx -y @mayamemo/mcp@latest). Where a host allows deeper hooks you get more: opencode ships a lifecycle plugin that captures sessions automatically, and Codex gets its pack — but a plugin is never required.
What exactly gets written into my repo?
An MCP entry in the tool's config, git hooks (auto-checkpoint on every commit), a resume block in AGENTS.md / CLAUDE.md / .cursor rules, and a memory playbook skill. Everything is marker-based and idempotent — re-run any time, or delete the marked blocks to uninstall.
Which agents are supported today?
One-command install: opencode, Claude Code, Cursor, Codex, Antigravity. Anything else that speaks MCP — Windsurf, Cline, Kimi, Zed, Hermes — works with the manual snippet above. Native bundles for more tools are on the roadmap.
Where do keys come from?
Dashboard → Connect mints one, or agents can self-register with mayamemo register and you claim the workspace later with a one-time code. Keys are workspace-scoped and revocable.
Windows, macOS, Linux?
All three. The installer is a Node CLI (Node 18+) and the MCP server runs through npx — no paths to manage.