mmk-hub

Self-hosted MCP hub

Claude connects one Google account.
You have more than one.

mmk-hub is a hub you run in your own Google Cloud project. Add every account you own, then reach all of them from a single Claude connector, in a single conversation.

Requires a Google Workspace account for Google's Developer Preview. No card, no spam.

one connectorPOST /mcp/••••••••••
{
  "name": "gmail_search_threads",
  "arguments": {
    "account": "personal",
    "query": "invoice"
  }
}
routes toyou@gmail.comSame connector. Same conversation.

The wall

One connector, one account. That is the whole problem.

Claude's Google connectors authorize a single Google account each. If your mail is split across a personal address and a work domain, Claude can only ever see one of them at a time.

The usual workaround is to rebuild the tools yourself against Google's raw interfaces. That throws away the part Google already got right: the tools on their own hosted MCP servers are shaped for Claude, and Claude handles them well.

mmk-hub keeps Google's tools exactly as they are and adds the one thing missing: an account name on every call.

How it works

Yours end to end, in three steps.

  1. Deploy the hub into your project

    One click from the installer, or one command by hand. It sets the hub up inside your own Google Cloud project, generates your keys, and costs nothing while it sits idle.

  2. Connect your accounts

    Sign in to your hub’s own admin UI, add an account, and pick which of the eight Google services it uses. Consent happens between you and Google.

  3. Point Claude at one URL

    Add the hub as a custom connector. Tools appear as gmail_*, calendar_* and so on, each one naming the account it should act on, which is what routes the call.

Coverage

Eight Google services today. Any MCP server next.

  • gmail_*

    Gmail

    Read, search, and send mail

  • calendar_*

    Calendar

    Read, create, update, and delete events

  • drive_*

    Drive

    Browse, read, and upload files

  • docs_*

    Docs

    Read and edit documents

  • sheets_*

    Sheets

    Read and update spreadsheets

  • slides_*

    Slides

    Read and edit presentations

  • chat_*

    Chat

    Read and send space messages

  • people_*

    People

    Look up and manage contacts

In progress

Beyond Google

Notion already runs a hosted MCP server that follows the shared standard for how a client finds a server and signs in to it. Building that once covers every server following the same standard, so connecting one will mean pasting a URL, with nothing to set up by hand.

  • NotionPages, databases, and search
  • LinearIssues and projects
  • Any MCP serverThat follows the shared standard

Services chosen per account

Give work its calendar and drive, give personal only mail. Change it any time from the admin UI, with nothing to reinstall.

Reconnect prompts that say why

Adding a service to an account means Google has to grant it more access. The hub names exactly which permission is still missing, until you approve it once more.

Usage you can actually see

Calls, errors and last-used per account, service and tool. Possible because the traffic runs through your hub.

Gmail and Workspace accounts

Pick the account type and the hub uses the right sign-in details for it, including a separate set per domain for Workspace.

Where the keys live

Your project. Your keys. Your bill.

The hub runs inside your own Google Cloud project. Your Google sign-in keys and your usage bill stay there. Nothing passes through Magic Meal Kits, and Claude never receives a key to your Google account, because the hub adds those credentials itself, after the request has left Claude.

What crossesClaude to hubHub to Google
Your short-lived Google keyNeverAttached by the hub
Your long-lived Google keyNeverEncrypted, in your project
Your Google sign-in secretNeverYour project only
Message and file contentRelayed, never storedThe origin

Being straight about the trade: because every call routes through your hub, your hub can see traffic in transit, and if it is down, every connected account is down with it. That is the cost of putting one connector in front of many accounts.

Pricing

Buy it once. Run it forever.

Starter

For one person running a couple of accounts.

TBAone time

  • Up to 2 connected Google accounts
  • All 8 Google services
  • Per-account service selection, nothing to reinstall
  • Admin UI with usage monitoring
  • 1 year of updates
Get access
Recommended

Pro

For a team, or anyone past two accounts.

TBAone time

  • Unlimited connected Google accounts
  • All 8 Google services
  • Per-account service selection, nothing to reinstall
  • Admin UI with usage monitoring
  • Lifetime updates, including features added later
  • Priority support
Get access

Pay once, use forever. Runs in your own Google Cloud project, so hosting is billed to you by Google, not by us.

  • Sold to businesses for business use.
  • Digital licence, so all sales are final. Run the free preflight check first to confirm Google can reach your project.

Before you buy

The parts worth knowing first.

What do I need before this works?

Google's Gmail, Calendar and Drive MCP servers are in Developer Preview, and they reject projects that are not enrolled. Enrolment needs a Google Workspace account and the number of the Google Cloud project you deploy into, and approval takes a few days. Apply first, then deploy while you wait. Until approval lands, every tool call returns a permission error even though the hub itself is healthy.

Can I use it with a personal Gmail account?

Partly. The hub connects consumer Gmail accounts, but a project on a consumer account cannot enrol in the Developer Preview, and Google expires its sign-in every seven days, so you would reconnect weekly. A Workspace account, approved for use inside your own organisation, does not expire.

Where do my Google credentials live?

In your own Google Cloud project. Your Google sign-in keys and your usage bill stay there; nothing passes through Magic Meal Kits. Claude never receives a key to your Google account either, because the hub adds those credentials itself, after the request has left Claude.

What does it cost to run?

You pay Google directly. The hub costs nothing while it sits idle, so light usage, under roughly ten thousand tool calls a month, comes to about zero. Heavier or business-scale traffic is billed by Google at their rates.

How long does setup take?

The deployment itself takes a couple of minutes from the installer. One step, creating your sign-in details inside Google, has to be done by hand because Google offers no way to automate it, and waiting for Developer Preview approval is the long pole at a few days.

Does it work with Notion, or other MCP servers?

Not yet, and it is the next thing being built. Notion already runs a hosted MCP server that follows the shared standard for how a client finds a server and signs in to it, so building that once covers Notion and every other server following the same standard. When it ships, adding one will be a matter of pasting the server URL, with nothing to set up by hand. Today the hub connects Google accounts only.

Is my data stored anywhere?

No. The hub relays message, calendar and file content and never stores it. It keeps only what it needs to run: your account settings, your sign-in details and your Google sign-in keys, all held encrypted inside your own project.

Get access

Put every account in one conversation.

Leave your email and we will write when access opens. Google's Developer Preview approval takes a few days, so it is worth starting that in parallel.

Already approved for the preview? Run the installer.