Documentation
Build with Auld memory.
Guides and reference for the Memory API, the MCP servers and agent plugins. Examples use plain HTTP; set AULD_API_BASE to your project host.
Memory API
- OverviewThe Memory API turns time-stamped records from your systems into memories an agent can recall: current facts, their history, and the sources behind them, filtered by who is asking.
- QuickstartSend a fact, send the fact that replaces it, wait for processing, and recall as one identity.
- SetupA production checklist: projects and keys, identities and audiences, backfill, live sync, recall in the agent, and verification.
- AuthenticationEvery request carries a project key as a bearer token.
- ConceptsSix nouns describe everything the API does.
- How it worksThe guarantees and behaviours to design around: asynchronous ingestion, idempotency, ordering, supersession, ranking and limits.
- Access controlUse identities, audiences and visibility to make sure each viewer recalls only what they are allowed to see.
- Sending dataGood memory starts with good records.
- WebhooksA webhook source gives another system a URL to post events to.
- API referenceEvery endpoint, grouped by resource.
- ErrorsErrors use HTTP status codes and a consistent JSON body.
- DebuggingMost surprises come from one of five causes.
MCP
- OverviewTwo Model Context Protocol servers: a memory server that gives an agent remember and recall tools, and a documentation server that lets coding assistants read these docs.
- QuickstartCreate an MCP token, add the server to your client, and test it with one remember and one recall.
- How it worksThe memory server is a thin, stateless layer over the Memory API with its own token model.
- ToolsFour memory tools and two documentation tools.
- Serving your own usersIf your product exposes its own MCP server or tools to many users, call the REST API from your tool handlers instead of handing out Auld tokens.
- Admin controlsProject administrators decide what each MCP token can do.
- SecurityMCP puts a model between your user and your data.
- Privacy and complianceWhat the MCP server stores, how to delete it, and what remains your responsibility.
- LimitsThe constraints you will meet in practice.
- TroubleshootingSymptoms, likely causes and fixes.
- FAQShort answers about the MCP servers.
Plugins
- OverviewGive coding agents and IDE assistants project memory: decisions, conventions and context that outlast a session and can be shared with a team.
- QuickstartFrom key to first recalled note in five minutes.
- ConfigurationThe scripts in these guides read a small set of environment variables.
- Claude CodeUse Claude Code hooks to recall memory before each prompt and save a session summary at the end — or connect the MCP server.
- CodexRegister the Auld MCP server in Codex’s configuration and add a standing instruction in AGENTS.md.
- CursorAdd the Auld MCP server to Cursor and a project rule that tells the agent to recall before answering history questions.
- JetBrains IDEsConnect the Auld MCP server to the AI features in IntelliJ IDEA, PyCharm, WebStorm and other JetBrains IDEs.
- Hermes AgentHermes Agent loads MCP servers from the mcp_servers section of its config.yaml.