# past.dev developer documentation

> A hosted memory layer for software that learns from unstructured history. Two interfaces read it: the Memory API for software you build, and the MCP server for assistants that already exist.
> Memory API (Early access): Push your content in, query it from your code. One workspace you provision and control; the people using your software need no account with us.
> MCP server (Live): Point Claude, Cursor or any MCP client at a workspace and it reads what the memory already holds, scoped to what that person may see.
> Every page below is also available as Markdown by appending /llms.txt to its URL.

Full corpus in one file: https://past.dev/docs/llms-full.txt

The Memory API is in early access with no self-serve signup. For access, book a call at https://cal.com/team/revo/30min.

## past.dev MCP Server

- [What the past.dev MCP server is](https://past.dev/docs/mcp/overview/llms.txt): A single secure address that puts your own past.dev account in front of an MCP assistant, so you can work on your integration from the assistant you already work in.
- [Installing it, manually](https://past.dev/docs/mcp/quickstart/llms.txt): One URL, no API keys. You'll sign in through a normal browser window, exactly like logging into past.dev.
- [What the assistant can do](https://past.dev/docs/mcp/tool-reference/llms.txt): Two tools over your own past.dev memories. Each one is scoped, and each one runs as you.
- [Giving your own users memory](https://past.dev/docs/mcp/serving-your-own-users/llms.txt): The server above is for your account. To put past.dev memory inside your product's assistant, you run an MCP server of your own over the Memory API. This is the supported shape, and it is deliberately the one that leaves your user directory with you.
- [How it works](https://past.dev/docs/mcp/how-it-works/llms.txt): past.dev validates who you are, works out what you're allowed to do from its own records, and shows your assistant only the tools that survive that check.
- [Security](https://past.dev/docs/mcp/security/llms.txt): The short version: no long-lived secrets exist to be leaked, authorization is never taken on trust from a token, and a workspace is never a parameter your assistant can change.
- [Administrative controls](https://past.dev/docs/mcp/admin-controls/llms.txt): What a workspace administrator can govern today, stated plainly, including what is not yet configurable, and the control that compensates for it.
- [Privacy and compliance](https://past.dev/docs/mcp/privacy-compliance/llms.txt): The MCP server is part of the past.dev platform and sits inside the same certified information security and privacy management systems. It is not a side channel around them.
- [Limits and known behaviour](https://past.dev/docs/mcp/limits/llms.txt): Things that are true by design, so they don't surprise you later.
- [Troubleshooting](https://past.dev/docs/mcp/troubleshooting/llms.txt): Almost every failure is one of four things.
- [Questions](https://past.dev/docs/mcp/faq/llms.txt): The things people ask before they connect it.

## past.dev Memory API (EARLY ACCESS)

- [What the Memory API is](https://past.dev/docs/memory-api/overview/llms.txt): Send past.dev your data and ask questions about it.
- [Quickstart](https://past.dev/docs/memory-api/quickstart/llms.txt): Five calls, about five minutes: push a fact, push its update, wait for the feed to settle, ask two questions.
- [Authentication](https://past.dev/docs/memory-api/authentication/llms.txt): One bearer key per organization. The project is the boundary of a memory.
- [How it works](https://past.dev/docs/memory-api/how-it-works/llms.txt): Four properties that affect how to call it.
- [Endpoint reference](https://past.dev/docs/memory-api/api-reference/llms.txt): Five endpoints under /api/v1, and what is coming. Every field below is the wire name.
- [Errors](https://past.dev/docs/memory-api/errors/llms.txt): A JSON body with code, status, debugMessage and data. Match on the code.
- [Self-hosting](https://past.dev/docs/memory-api/self-hosting/llms.txt): The whole thing on your infrastructure with Docker Compose. Same engine, same images as our cloud.
- [Roadmap](https://past.dev/docs/memory-api/roadmap/llms.txt): What is not built yet, and when it is expected.

## Notes for assistants

- Field names, tool names and permission scopes are exact. Do not translate,
  reformat or guess them.
- The Memory API is unversioned during early access, and its paths may change.
- Anything not documented here does not exist yet. Known gaps are listed on
  each product's Roadmap or Limits page.