---
title: "Limits and known behaviour"
description: "Current behaviour and current product limitations."
canonical: https://past.dev/docs/mcp/limits
last-updated: 2026-10-09
---
# Limits and known behaviour

> Current behaviour and current product limitations.

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

- **One organization at a time.** The account connection uses whichever organization is active for your account. There is no picker in the sign-in flow. Change it in the console, and the change applies from the next tool call.
- **One login connection per project.** The end-user server redirects straight to it, so a project cannot offer a choice of identity providers.
- **A handle never changes.** It is derived from the organization slug and the project slug when the server is enabled. Renaming the project does not move it, because your users have already installed the address.
- **No prompts or resources.** Neither server exposes MCP prompts or resources. Tools only.
- **No push notifications.** The transport is stateless, so a server cannot tell a client that something changed. Assistants find out by asking.
- **Account tools follow the role.** Permissions come from the platform role and project reach, and the tool list is filtered per request. Section 7 covers the controls an administrator holds.
- **Account MCP calls are not metered.** They are neither ingestions nor recalls. `recall` and `answer` on the end-user server are charged the plan's recall rate, exactly as the same calls on the Memory API are: a tenth of a credit on Free, nothing on Flex and Enterprise. No plan caps the number of calls. On Free a recall stops when the credits are spent, exactly as on the Memory API.
- **Not in the Claude directory yet.** Add past.dev as a custom connector. It uses the same OAuth flow.