Fleet a side project atPostHog
All packs

MCP gateway

The hub signs in to your MCP servers once, and agents on every machine reach them through it.

Needs a hub

Add to your Fleet

How it works

  1. Agent on any machine
  2. Tunnel to the hub
  3. MCP gateway
  4. Your MCP servers

Workflows

  • MCP gateway

    On with the pack

    The hub signs in to your MCP servers once, and agents on every machine reach them through it.

  • Slack bridge

    Off until you turn it on

    Agents read Slack as you through the MCP gateway, and leave only unsent drafts and canvases.

    Read before you turn it on

    The bridge acts as your Slack account. It reads what you can read, and writes only drafts you send yourself and canvases. Native Codex turns its Slack app off on every machine, so agents reach Slack only through the bridge.

  • Gmail

    Off until you turn it on

    Agents read your mail and leave replies as unsent drafts, through the MCP gateway.

    Read before you turn it on

    The route acts as your Google account through a ChatGPT sign-in. Only its allowlist keeps agents from tools that send, change or delete, so native Codex turns Gmail off on every machine.

  • Google Calendar

    Off until you turn it on

    Agents read your calendar through the MCP gateway, and change nothing.

    Read before you turn it on

    The route acts as your Google account through a ChatGPT sign-in. Only its allowlist keeps agents from tools that send, change or delete, so native Codex turns Google Calendar off on every machine.

  • Google Drive

    Off until you turn it on

    Agents read your documents, sheets and slides through the MCP gateway, and change nothing.

    Read before you turn it on

    The route acts as your Google account through a ChatGPT sign-in. Only its allowlist keeps agents from tools that send, change or delete, so native Codex turns Google Drive off on every machine.

  • Mail replies start threads

    Off until you turn it on

    A reply in a Gmail conversation that you wrote in starts a T3 thread about it, and later replies in that conversation go to the same thread.

    Read before you turn it on

    Mail from outside becomes agent prompts. The prompt treats every email as data, and the Gmail route can only read mail and write drafts.

  • Review wait wakes threads

    Off until you turn it on

    When a ready pull request of yours waits 4 hours on a review nobody gave, the T3 thread that links it wakes up, and again at 24 hours. A thread that has waited 30 minutes on a decision it put to you in prose, while a watch keeps it under Working, is told once to ask with the question tool.

    Read before you turn it on

    Reads your pull requests on GitHub and your own Slack messages from the last 12 hours. It messages your threads and changes nothing on GitHub or Slack.

What it costs

The hub needs Docker. Every other machine reaches the gateway through its tunnel to the hub.

Know before you turn it on

The hub holds the sign-ins for your MCP servers, and each machine holds a key that reaches all of them. Keep the hub as private as your laptop.

Settings3 settings that your agent asks about
  • mcp-gateway.mailQueryWhich Gmail search finds the mail that may be a reply to you? Mail watch adds the time window itself.Default: in:inbox -from:me -category:promotions -category:social -category:forums
  • mcp-gateway.reviewWaitSearchWhich GitHub search qualifiers narrow the ready pull requests that review wait watches, such as org:your-org? Leave it empty for all of yours.
  • mcp-gateway.reviewWaitAsksWhich Slack search filter finds your own review asks, such as from:<@U012ABCDEF> in:#your-team? Review wait holds a pull request you linked there in the last 12 hours.

Add MCP gateway to your Fleet

Paste this prompt into a T3 Code thread on a machine that runs Fleet.

Your install prompt

Add this Fleet pack to my setup with me: MCP gateway.

Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself.

1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on.
2. This pack needs a hub: MCP gateway. Run `fleet hub status`. When it prints "The hub: not named", I have no hub yet. Tell me, leave that pack out, and offer to add a hub and a node first with step 9 of https://raw.githubusercontent.com/Silthus/fleet-engine/main/SETUP.md. Otherwise the name after "The hub:" is the SSH name of the hub. Use it as the host of each SSH command in a note.
3. Read the setup note of each pack. Ask me what it asks, and collect the flags that it names. Where a note names "the setup command" or "the command in step 9", use the `fleet packs` command of this prompt. Do not run a step that a note puts after that command yet.
   - MCP gateway: ~/.local/share/fleet/engine/packs/mcp-gateway/SETUP.md
4. Turn the packs on with one command, and add the flags that the notes name:
   fleet packs --add mcp-gateway
5. Run `fleet update` on the hub over SSH, so the hub has the packs before a note's next step needs them.
6. Do the steps that each note puts after the command.
7. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens.
8. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.
Open in T3 Code

Add more packs in one prompt