BrewingCoder/outpost2

Self-hosted, multi-user MCP server with named connections. One person, several
unrelated Microsoft Entra tenants and other providers, reachable conversationally from a
phone.
Say "check work email" and it knows which mailbox. Say "all" and it checks every one.
## The problem it solves
Every open-source Microsoft/Outlook MCP server is local stdio, single-operator, and
addresses accounts by opaque id — so none of them can be reached from a phone at all,
and none of them can hold two tenants at once without you knowing which GUID is which.
That matters because the real use case is not sitting at a desk. It is a voice
conversation while driving, where you cannot read an id, cannot click a consent screen,
and cannot open Outlook to finish the job. Everything here follows from that: the web app
is configuration only, every tool answers in prose, and anything that cannot be said out
loud is a design bug.
## This is self-hosted. There is no service to sign up for.
Nobody sells seats on an OutPost2 instance, including us. You run your own, against your
own Entra app registration, holding your own users' tokens. outpost.brewingcoder.com is
one person's private deployment, not an invitation — it will not let you in.
The licence enforces this in both directions: you can run it commercially inside your own
organisation, and you may not run it as a service for other people. See
Licence.
## What it does
50 tools across three providers, all resolved through the same named-connection model.
| Area | Tools |
| Connections | listconnections |
| Mail — read | listmail readmail searchmail listattachments readattachment |
| Mail — write | sendmail sendmailwithattachments replymail forwardmail |
| Mail — manage | markmail movemail flagmail categorisemail listcategories reportjunk |
| Calendar — read | listevents readevent |
| Calendar — write | createevent updateevent cancelevent respondtoinvite |
| Calendar — scheduling | checkavailability suggestmeetingtimes |
| People | findperson listcontacts savecontact updatecontact |
| Teams chats | listchats readchat sendchatmessage |
| Issues (YouTrack) | createissue getissue updateissue searchissues commentonissue listprojects createproject |
| Code (GitHub) | githubrepositories githubreponames githubissues githubpullrequests githubcommits githubitem githubtriage githubfiles githubfile |
| Files and jobs | listfiles checkqueue + a web approval queue |
| Feedback | reportfriction — the agent files its own bug reports mid-task |
Large attachments stream to Graph in 320 KiB-multiple chunks from object storage and never
buffer in memory, so sending is a resumable job rather than a tool call that times out.
Calendar times are the mailbox's own, not the server's: the mailbox timezone is read from
Graph and every reading and writing of a time goes through it, so "move it to two" means
two o'clock where you are and still does either side of a clock change.
Some things happen when nobody is watching — a tenant administrator approving a
connection days after the user gave up, a long send finishing. Set a Telegram chat id on
the notifications page and you hear about those; set nothing and the settings page and