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

# Stopping the hub

> What Stop hub does, what it takes with it, and what changes if you deploy again afterwards.

Stopping removes the hub from your Google Cloud project. Your Google accounts
stay connected to Google; what goes is the thing that was talking to them on
your behalf.

Nothing is billed once it is gone, and nothing is billed while it sits idle
either, so cost is rarely the reason to do this.

## Before you stop

<Warning>
  **Stopping is not pausing.** Deploying again afterwards issues a **new admin
  token**, and the connector tokens your clients hold are signed from it, so
  every client you have connected will have to connect again.

  If you are only trying to move to a newer version, use **Upgrade now** on the
  installer instead. Nothing has to be redone after that.
  See [Setting up](/quickstart#keeping-it-up-to-date).
</Warning>

What does survive is more than the interface implies. The accounts you
connected are still there when you deploy again, because they are kept in your
own project rather than in the hub. So is your OAuth client. And the MCP
address is derived from your project and region, so it comes back the same:
the address in your client is still correct, it is the sign-in behind it that
was reissued.

## How to stop it

<Steps>
  <Step title="Open the installer">
    Go to [the installer](https://make.magicmealkits.com/v2/deploy) and scroll
    to the bottom of the MCP Hub section.
  </Step>

  <Step title="Press 허브 정지">
    <Frame>
      <img src="https://mintcdn.com/mcp-hub/_5S572FR3uaOuoK1/assets/install/stop-card.png?fit=max&auto=format&n=_5S572FR3uaOuoK1&q=85&s=c32297c9b0ff76d71cbc90298b3003cf" alt="The stop card at the bottom of the installer, with its button" width="1680" height="350" data-path="assets/install/stop-card.png" />
    </Frame>
  </Step>

  <Step title="Type the service name">
    The confirmation asks you to type it, and the button stays disabled until
    it matches. It is `mmk-hub`, the same for everyone.

    <Frame>
      <img src="https://mintcdn.com/mcp-hub/_5S572FR3uaOuoK1/assets/install/stop-confirm.png?fit=max&auto=format&n=_5S572FR3uaOuoK1&q=85&s=9e80a20d751213fdcc4040d175abb9f0" alt="The confirmation dialog with the service name typed in" width="985" height="500" data-path="assets/install/stop-confirm.png" />
    </Frame>
  </Step>

  <Step title="Done">
    <Frame>
      <img src="https://mintcdn.com/mcp-hub/_5S572FR3uaOuoK1/assets/install/stop-done.png?fit=max&auto=format&n=_5S572FR3uaOuoK1&q=85&s=c39690b8b7df4976f40c1eb6189bfa8c" alt="A confirmation that the hub has been stopped" width="780" height="130" data-path="assets/install/stop-done.png" />
    </Frame>

    The deploy card comes back in place of the running one, so the page is
    ready to install again whenever you want it.
  </Step>
</Steps>

## Afterwards

Connected accounts stop working immediately. Claude will report that it cannot
reach the connector rather than that anything is wrong with your accounts.

Deploying again brings them back as they were, still connected, without going
through Google's consent screens a second time. What you do have to redo is the
connector in each client, using the new admin token.

## Next

* [Setting up](/quickstart), if you are deploying again
* [Troubleshooting](/troubleshooting)
