MCP server for AI tool integration.
The me mcp command runs Memory Engine as a Model Context Protocol server over stdio, allowing AI coding agents to store and retrieve memories.
- me mcp -- run the MCP server
Run the MCP server over stdio.
me mcp [options]
| Option | Description |
|---|---|
--api-key <key> |
Agent API key. If omitted, the server uses your stored me login session. |
--space <slug> |
Space to operate in (the X-Me-Space). |
Resolution order:
- Auth token:
--api-key>ME_API_KEY> stored session token. - Space:
--space>ME_SPACE> stored active space. - Server URL:
--server(global option) >ME_SERVER>https://api.memory.build.
A logged-in developer needs no key or space — the active session and active space are used automatically. For an unattended/headless agent, pass --api-key and --space (or set ME_API_KEY / ME_SPACE).
This command is typically not run directly -- it is invoked by AI tools based on their MCP configuration.
MCP registration lives under agent-specific commands:
| Tool | Command |
|---|---|
| OpenCode | me opencode install |
| Codex CLI | me codex install |
| Gemini CLI | me gemini install |
| Claude Code | me claude plugin hooks |
Claude Code uses the Memory Engine plugin instead of MCP registration through the me CLI:
claude plugin marketplace add timescale/memory-engine
claude plugin install memory-engine@memory-engine [--scope user|project|local]
Then start Claude Code, run /plugin, select memory-engine, and configure the options (all optional except server): leave api_key blank to use your me login session, leave space blank to use your active space, and tree_root defaults to /share/projects.