---
title: "Questions"
description: "The things people ask before they connect it."
canonical: https://past.dev/docs/mcp/faq
last-updated: 2026-08-26
---
# Questions

> The things people ask before they connect it.

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

#### Does connecting this give Claude access to everything in past.dev?

It gives Claude access to exactly what *you* have access to, through the tools listed in section 3. Not your colleagues' private memories, not other workspaces, not anything your visibility doesn't cover.

#### Can it delete my data?

No. The tools search, read and add. There is no destructive delete among them; removing something happens in the past.dev app.

#### Do I need an admin to set this up?

No. Any workspace member can connect it for themselves. Nothing is provisioned centrally, and one person's connection has no effect on anyone else's.

#### Can my whole team share one connection?

No, and that's deliberate. Each person connects with their own account so every action is attributed to them and bounded by their own permissions.

#### How do I disconnect?

Remove the connector in your AI client. That stops it calling past.dev, and for an ordinary disconnect it's enough.

If you need access genuinely cut off, a lost laptop or a departing colleague, removing the connector isn't sufficient, because the token lives with the client. Remove the person's workspace membership. past.dev checks it on every request, so their next call fails no matter what credentials they still hold. There is no self-service way to revoke an MCP connection on its own today; ask past.dev support if you need the underlying grant torn down as well.

#### Does it cost anything?

Not through this server. Both tools read and write the database directly, with no model in the loop, so neither consumes AI usage. What does cost is the Memory API itself: `/recall` and `/answer` report `usage.recallCostUsd` and `usage.answerCostUsd` on every response, so an MCP server you build over them prices itself per call.

#### Will it appear in the Claude directory?

That's the intention. Until then, the manual custom-connector setup in section 2 is the supported path, and nothing about it is second-class. A directory listing would change discovery, not capability or security.