Skip to main content
The free tier isn’t a trial. Upgrade when history and a domain of your own start to matter.

​
The plans

​
What the limits mean in practice

Each running heymcp share is one tunnel. Close the terminal and the slot frees immediately. heymcp sessions shows what’s live.A heymcp share past the limit is refused with a message saying so.
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.
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.
Both plans get a reserved slug — a permanent two-word subdomain minted at first sign-in. Pro adds --slug for picking your own.
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.

​
Bounds that apply on every plan

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

​
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. See Billing.