> ## 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.

# Changelog

> What changed in HeyMCP, and when.

Everything that has shipped, newest first. Fixes are listed as well as features,
because a tool you point an agent at is only worth having if you can see what it
has been doing.

<Update label="26 August 2026" tags={["Docs", "Site"]}>
  ## Docs went live, and the site now says so

  These docs are published. The CLI has always printed a link to them next to
  every lint finding, and until today those links went nowhere.

  * Every schema check now has a page you can reach from the terminal, from the
    inspector, or from the nav above.
  * The app and the marketing site both link here. If you have been guessing at
    `heymcp share` flags, the [CLI reference](/cli/overview) has them all.
  * A page per client: [Claude.ai](/clients/claude-ai), [Claude Code](/clients/claude-code),
    [ChatGPT](/clients/chatgpt), [Grok](/clients/grok), [Cursor](/clients/cursor),
    [VS Code](/clients/vscode) and [Gemini](/clients/gemini).

  ## Fixed: the billing page 404'd if you loaded it directly

  Clicking through to Billing inside the app worked. Landing on `/billing` from a
  bookmark, a refresh, or a redirect back from checkout did not. One over-eager
  line of routing config. Fixed, and pinned with a test.
</Update>

<Update label="19 August 2026" tags={["Inspector"]}>
  ## The inspector reads like a conversation

  The timeline was showing you frames. It now shows you attempts: a request and
  the response that answered it, folded into one row, with headers and a
  formatted payload underneath.

  * Request and response headers are shown, so a content-type argument between
    your server and an agent is visible rather than inferred.
  * JSON payloads are formatted and line-addressable instead of being one long
    string.
  * A session now records what you pointed it at. A list of four tunnels all
    called `vivid-meadow` was unreadable without knowing which local server each
    one served.
  * Only genuine failures are painted red. A tool call that returned an error
    result on purpose is not a broken tool call.
</Update>

<Update label="17 August 2026" tags={["CLI", "Domains", "Relay"]}>
  ## The CLI is published

  One command, four platforms, checksums for all of them.

  ```
  curl -fsSL https://heymcp.dev/install.sh | sh
  ```

  macOS and Linux, Intel and ARM. The installer picks a directory already on your
  `PATH` where it can, and fixes your `PATH` itself where it cannot, because an
  install that finishes and still leaves you with `command not found` has not
  finished.

  ## Custom domains, with certificates issued on demand

  Point a CNAME at us and the certificate is obtained at the first connection.
  Agents remember the URL they were given, so a stable address of your own is the
  difference between a connector that keeps working and one you re-add every week.

  ## Fixes worth naming

  * **One tunnel now survives a reconnect.** A laptop lid, a wifi blip or a
    restarted local server used to fork your history into a new session and
    destroy the before-and-after comparison you opened the inspector for. A
    reconnect within fifteen minutes continues the same session.
  * **A client is told its session is gone** instead of failing in a way that
    reads like your server broke.
  * **Spec-compliant servers are no longer flagged for refusing SSE.** The probe
    was giving up before it could tell the difference.
  * **We report the server's protocol version, not our own.**
  * **Our own probe no longer appears in your timeline** as though an agent had
    called you.
  * **ChatGPT is called ChatGPT.** The fingerprint said otherwise.
  * **`heymcp login` works**, and a new account lands on onboarding rather than an
    empty list.
  * **The sessions list is live**, which its own empty state had been promising.
</Update>

<Update label="15 August 2026" tags={["Relay"]}>
  ## First build

  The relay, the CLI, the control plane and the inspector. A local MCP server
  gets a public HTTPS URL, HeyMCP performs the handshake itself before any agent
  arrives, lints the schemas, and streams every frame into a timeline in plain
  English.
</Update>