MCP tool reference

One start command.
Clear memory tools.

Run setup once and restart your AI tool. Engram then appears as MCP tools with startup guidance; you can inspect the focused tools below when needed.

1. Human action

Install once

You run one terminal command: npx engram-tools@0.3.6 --setup <api-key>. This writes MCP config for Claude Code, Cursor, Gemini, Antigravity, Codex, OpenCode, and VS Code/Copilot where possible.

$ npx -y engram-tools@0.3.6 --setup <api-key>

2. Agent action

Call tools inside the AI app

You do not run engram_start in your shell. After setup, the client exposes Engram tools and startup guidance to the agent. You describe the task normally; if a client ignores the guidance, paste a short context prompt once.

You: Work on this repo/task. Use Engram context before planning.

3. Why it works

MCP exposes Engram as tools

After restart, the AI client loads the Engram MCP server. The agent sees tools like engram_start, engram_store, and engram_recall, plus AGENTS.md guidance and Claude slash-command helpers.

Agent sees: engram_start, engram_store, engram_recall...

Best first message to your agent

Engram also guides agents through MCP. This prompt makes the first session explicit and helps the agent use recall, cross-pollination, and rehydrate at the right moments.

The welcome email includes this too. Docs keep it here as a fallback when an AI client ignores MCP startup guidance.

Call engram_start with this project context:
  project: <product or client>
  repo: <repo slug>
  role: <what you are doing>
  market: <domain or market>
  stack: <main technologies>
  task: <current task>
Before choosing an approach, call engram_recall.
If another repo may have solved this pattern, call engram_cross_pollinate.
If this chat was compacted or resumed, call engram_rehydrate before continuing.

Troubleshooting config formats

Normal setup writes these automatically. Use this section only when a client does not show Engram tools after restart and you need to inspect the file shape.

Antigravity

Google's current Gemini flow may route users into Antigravity. Engram writes both the shared Gemini config and Antigravity-specific config files.

// ~/.gemini/config/mcp_config.json
// ~/.gemini/antigravity/mcp_config.json
{
  "mcpServers": {
    "engram": {
      "command": "npx",
      "args": ["-y", "engram-tools", "mcp"]
    }
  }
}

OpenCode

OpenCode uses a command array instead of the standard mcpServers shape. The setup command writes that format automatically.

// ~/.config/opencode/opencode.json
{
  "mcp": {
    "engram": {
      "type": "local",
      "command": ["npx", "-y", "engram-tools", "mcp"],
      "enabled": true
    }
  }
}

Codex

Codex uses TOML. Engram replaces only the engram table and preserves the rest of your Codex config.

# ~/.codex/config.toml
[mcp_servers.engram]
type = "stdio"
command = "npx"
args = ["-y", "engram-tools", "mcp"]

Tools

Select one tool to inspect

Core loop

Tools agents use in normal coding flow, plus recovery after compaction.

Advanced and checkpoints

Keep these available, but use them only when their trigger is real.

Select one tool to inspect

engram_start

Call first after setup/restart, before the agent starts making product or code decisions.

engram_start

Start a new agent session with one canonical call.

Call first after setup/restart, before the agent starts making product or code decisions.

agent_tool

optional

string

Which AI tool is calling, e.g. claude-code, codex, cursor, gemini, antigravity.

project

recommended

string

Product or client name. The schema allows an empty start as a fallback, but useful starts should include this.

repo

recommended

string

Repository or project slug for filtering private memory. The schema allows an empty start as a fallback, but useful starts should include this.

role

optional

string

What the agent should behave as: frontend product engineer, backend engineer, PM, etc.

market

optional

string

Domain context, e.g. UK property, fintech, education.

task

recommended

string

Immediate task the agent is about to do. This is the strongest signal for relevant recall.

stack

optional

string[]

Relevant technologies.

context

optional

string

Optional full context summary. If omitted, Engram builds one from the other fields.

include_skills

optional

boolean

Default true. Include matching skill guides.

limit

optional

number

Default 12. Max memories to load.

What is MCP?

The standard that makes Engram possible.

📡

An open standard by Anthropic

MCP (Model Context Protocol) is an open standard created by Anthropic. It lets AI agents connect to external tools and data sources through a simple, universal interface.

🔌

USB for AI

Think of it like USB for AI: one standard, every tool works. No custom integrations, no proprietary SDKs, no vendor lock-in. If your tool speaks MCP, it just works.

🧠

Engram is an MCP server

Any MCP-compatible AI tool can connect to Engram. Claude Code, Cursor, Gemini, Antigravity, Copilot, OpenCode, Windsurf, Devin. If it supports MCP, it supports Engram.

⚡

Zero integration effort

No SDK needed. No custom integration code. Just add Engram to your agent's MCP config and it gets Engram memory tools instantly.

How it connects

Your Agent

Claude, Cursor, etc.

MCP

➞

Engram

MCP Server

store/recall

➞

Team Memory

PostgreSQL + pgvector

Workspaces are your team boundary

Use one workspace for a team. Repos organize project memory inside it. Invite teammates from the dashboard so everyone gets their own key.

Frontend repo

Tools

Claude CodeCursorCopilot

Memories45

API repo

Tools

Claude CodeWindsurf

Memories128

Mobile repo

Tools

CursorDevin

Memories67

What a workspace means

✓The workspace is the private memory boundary for one team or company.
✓Repos and projects organize memories inside that boundary.
✓Teammates should be invited from the dashboard so each person has a separate key.
✓Agents in the same workspace can reuse private lessons across repos.
✓Different workspaces stay isolated; public memory can still enrich results.

workspace-sync.sh
$ engram_get_context({ repo: "api-backend" })

Start ahead, not from scratch

Every new workspace starts with 100,000 source-aware public memories across agent tools, MCP, RAG/search, security, ops, engineering docs, and product/devex.

100K

Public memories

Source families

Skill guides

🔄

Agent

Patterns

Proven approaches

Patterns

Proven approaches for common tasks. Example: "API route pattern: try-catch wrapper, validate input, check auth, then business logic." Patterns tell you HOW to do something the right way.

📏

MCP

Conventions

Team rules and standards

Conventions

Team rules and coding standards. Example: "Always use Prisma migrations, never raw SQL ALTER TABLE." Conventions keep your codebase consistent.

⚠️

Risk

Gotchas

Traps and surprises

Gotchas

Things that break or surprise you. Example: "async/await inside forEach does NOT work as expected. Use for...of instead." Gotchas save you hours of debugging.

🔧

Ops

Solutions

Battle-tested fixes

Solutions

Battle-tested fixes for common problems. Example: "Hydration mismatch in Next.js: use useEffect for client-only logic." Solutions give you the answer, not just the hint.

📦

Stack

Dependencies

Framework-specific

Dependencies

Version-specific knowledge for frameworks. Example: "Prisma 7 requires PrismaPg adapter pattern." Dependencies prevent upgrade surprises.

🎓

Skill Guides

Step-by-step guides

Skill Guides

Step-by-step guides for complex tasks. Example: "Code Review Skill: 15 steps from pulling the branch to approving." Skills give your agent expertise on demand.

Sourced from: Covering: React, Next.js, Vue, Angular, Python, Go, Rust, TypeScript, PostgreSQL, Docker, Kubernetes, AWS, and 25+ more technologies. Plus business skills: Product Management, Sales, Marketing, HR, Legal, Finance, and more.

Other agents start empty. Yours starts with 100,000 source-aware public memories, 20 step-by-step guides, and a private workspace bank that compounds from day one.

Two memory banks. One smart agent.

Public knowledge for everyone. Private knowledge for your team.

🌍

100K

Public Memory Bank

✓100,000 source-aware public memories
✓Agent tools, MCP, RAG/search, security, ops, and devex
✓20 step-by-step guides
✓Best-practice patterns, gotchas, solutions, and evidence checks
✓Updates as the public bank grows
✓Available to every Engram user

FREE for all plans

🔒

isolated

Private Memory Bank

✓Your team's proprietary knowledge
✓Conventions specific to your codebase
✓Internal architecture decisions
✓Incident learnings and post-mortems
✓Never shared outside your workspace
✓Isolated, encrypted, workspace-scoped

Your competitive edge

Agent recalls

→↓

Searches Private first

→↓

Enriches with Public

→↓

Best combined results

Combined recall

Private memory first. Public knowledge fills the gaps.

Engram searches your workspace knowledge first, then adds source-aware public practices and guides when they help.

engram_start

One start command.
Clear memory tools.

Install once

Call tools inside the AI app

MCP exposes Engram as tools

Best first message to your agent

Troubleshooting config formats

Antigravity

OpenCode

Codex

Tools

Core loop

Advanced and checkpoints

Start a new agent session with one canonical call.

What is MCP?

An open standard by Anthropic

USB for AI

Engram is an MCP server

Zero integration effort

Workspaces are your team boundary

Frontend repo

API repo

Mobile repo

What a workspace means

Start ahead, not from scratch

Two memory banks. One smart agent.

Public Memory Bank

Private Memory Bank

Private memory first. Public knowledge fills the gaps.

Help us make Engram sharper

Tell us what is missing

One start command.Clear memory tools.

Install once

Call tools inside the AI app

MCP exposes Engram as tools

Best first message to your agent

Troubleshooting config formats

Antigravity

OpenCode

Codex

Tools

Core loop

Advanced and checkpoints

Start a new agent session with one canonical call.

What is MCP?

An open standard by Anthropic

USB for AI

Engram is an MCP server

Zero integration effort

Workspaces are your team boundary

Frontend repo

API repo

Mobile repo

What a workspace means

Start ahead, not from scratch

Two memory banks. One smart agent.

Public Memory Bank

Private Memory Bank

Private memory first. Public knowledge fills the gaps.

Help us make Engram sharper

Tell us what is missing

One start command.
Clear memory tools.