> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heymcp.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans and limits

> What each plan allows.

The free tier isn't a trial. Upgrade when history and a domain of your own start
to matter.

## The plans

|                                    | **Hobby** | **Pro**    |
| ---------------------------------- | --------- | ---------- |
| Price                              | Free      | \$12/month |
| Servers shared at once             | 3         | 10         |
| Events per month                   | 5,000     | Unlimited  |
| History                            | 24 hours  | 7 days     |
| Handshake probe, checks and replay | Yes       | Yes        |
| A slug you choose                  | —         | Yes        |
| Custom domains                     | —         | 1          |
| Daily transfer                     | 100 MB    | 2 GB       |
| Max request body                   | 2 MB      | 8 MB       |

## What the limits mean in practice

<AccordionGroup>
  <Accordion title="Servers shared at once">
    Each running `heymcp share` is one tunnel. Close the terminal and the slot
    frees immediately. [`heymcp sessions`](/cli/sessions) shows what's live.

    A `heymcp share` past the limit is refused with a message saying so.
  </Accordion>

  <Accordion title="Events per month">
    One event is one MCP frame — a request or a response. A busy afternoon of
    real agent testing is typically hundreds, not thousands.

    This is a **soft cap**, checked once when a tunnel opens rather than on
    every event. A session already running keeps recording, so a single long
    session can overshoot rather than being cut off mid-conversation.
  </Accordion>

  <Accordion title="History">
    How long events are kept before pruning. **The window is stamped on each
    session when it opens**, from the plan in force at that moment — so
    upgrading doesn't resurrect yesterday's expired history, and downgrading
    doesn't delete history you could already see.

    An expired session keeps its row so you can see it happened. See
    [Sessions and history](/concepts/sessions#retention).
  </Accordion>

  <Accordion title="A slug you choose">
    Both plans get a **reserved slug** — a permanent two-word subdomain minted
    at first sign-in. Pro adds
    [`--slug`](/cli/share) for picking your own.
  </Accordion>

  <Accordion title="Max request body">
    A request larger than this is refused at the edge with a 413 and a JSON-RPC
    body. Relevant if your tools take large payloads — an uploaded document, a
    long transcript.
  </Accordion>
</AccordionGroup>

## Bounds that apply on every plan

These aren't plan limits, they're how the inspector stays honest:

|                             | Bound  | Effect                                                                     |
| --------------------------- | ------ | -------------------------------------------------------------------------- |
| Event payload               | 256 KB | Truncated in the inspector and flagged. **Forwarded to the client whole.** |
| Events buffered per session | 2,000  | Oldest dropped, with a visible `DROP` marker in the timeline.              |

## No teams

HeyMCP has no team model. A session belongs to exactly one account, and nobody
else can read it.

The Stripe quantity on a Pro subscription buys **extra custom domains**, not
seats. If several people need HeyMCP, each needs their own account.

## Upgrading

From **Billing** in [app.heymcp.dev](https://app.heymcp.dev). See
[Billing](/account/billing).