---
title: "What the past.dev MCP servers are"
description: "past.dev operates two authenticated MCP servers: one for the people who administer an organization, and one for your product's end users."
canonical: https://past.dev/docs/mcp/overview
last-updated: 2026-10-09
---
# What the past.dev MCP servers are

> past.dev operates two authenticated MCP servers: one for the people who administer an organization, and one for your product's end users.

Product: past.dev MCP Server. Source: https://past.dev/docs/mcp/overview

MCP, the Model Context Protocol, is an open standard that connects AI assistants to data and tools. past.dev operates two authenticated MCP servers. They share a host and nothing else: each one signs a different person in, and each one carries its own tools.

| Server | Who signs in, and what it carries |
| --- | --- |
| **Account server** | `https://app.past.dev/mcp`. A console member administers the organization from an assistant: projects, project keys, members, access, plan, usage, the request log and the debugging reads. It also recalls and ingests in the projects that member reaches. 54 tools, filtered by the caller's platform role. Section 02 connects it and section 03 lists every tool. |
| **End-user server** | `https://api.past.dev/mcp/<handle>`, one per project. Your own end users reach that project's memory from their own assistant. They sign in at your identity provider and never hold a past.dev account. Four tools. Section 04 describes it. |
| **Documentation server** | `https://past.dev/mcp`. This documentation, read-only and unauthenticated. Use it while you write code against the API. It reaches no account data. |

### Which server you want

- **You administer past.dev, or your own assistant needs a project's memory.** Connect the account server. It does what the console does, as you, under your role, and it recalls and ingests in the projects you reach.
- **Your users need their own memory.** Enable the end-user server on the project. Each user signs in at your identity provider and recalls only what their identity may see.
- **You are writing integration code.** Add the documentation server, and call the [Memory API](/docs/memory-api/overview) for ingestion and recall from your own software.

> **The account server reads and writes memory as you**
>
> `recall_memory` and `ingest_memory` act on a project's memory as `POST /api/v1/recall` and `POST /api/v1/ingest` do: the same arguments, refusals and price. They work only in the projects you reach, at project Read for a recall and project Write for an ingestion. With no `identity`, a recall reads what the console's Memories screen shows.
>
> To give your own users an assistant over a project's memory, enable the end-user server on that project, described in section 04. Your own software calls the Memory API.

### What connects to it

Both servers work with clients that support remote MCP servers over Streamable HTTP with OAuth. These include Claude desktop, Claude web, Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf and Zed. Section 02 gives the setup for each one.

> **Claude setup**
>
> past.dev is **listed in Claude's connector directory**. Find past.dev there and connect it, or add the account server manually as a custom connector at `https://app.past.dev/mcp`. Both ways use the same OAuth flow and the same security controls.