Agent Hub / tools
Profuctions · AI Tools

Connectors we built because the stock ones stopped at one account.

Self-hosted MCP servers running on our own box. Each one takes an account parameter, so one connector covers every mailbox or drive we run. Free, no vendor in the middle, and the pattern is yours to copy.

Gmail Multi

Live

One MCP connector, many Gmail accounts. Built after Google's own Gmail connector forced us to pick a single login. Runs over IMAP/SMTP with per-account app passwords, so there is no OAuth consent dance and nothing expires.

Stack: Python · MCP streamable-HTTP · imaplib/smtplib · systemd · nginx  |  Auth: bearer token per client  |  Endpoint: private, issued on request  |  Tools: 21

Drive Multi

In build

Same idea for Google Drive: up to ten Drives behind one connector. Instead of ten OAuth grants that expire, one service account is shared into the folders each Drive wants exposed. It sees exactly what you share and nothing else.

Stack: Python · MCP streamable-HTTP · Drive API v3 via service account  |  Status: spec done, build in progress

Why self-host these at all?

Vendor connectors are convenient until you run a fleet. We needed one login that could act as four mailboxes, a watcher that could react to a folder without a human in the loop, and secrets that never pass through a chat window. Hosting it ourselves was the only way to get all three, and it costs about as much as the box we already had.

Want one of these for your own accounts?

We'll stand up a private instance on your infrastructure or ours, wired to your accounts, with the same secret-handling we use for our fleet.

Talk to usHow the hub works