※ shipped something on tuesday※ now supporting chatgpt MCP※ no, we don’t train on your email※ yes, you can self-host (eventually)※ 2026 · MCPortal · est. last month※ if you’re reading this, scroll※ the cat is on the keyboard again※ shipped something on tuesday※ now supporting chatgpt MCP※ no, we don’t train on your email※ yes, you can self-host (eventually)※ 2026 · MCPortal · est. last month※ if you’re reading this, scroll※ the cat is on the keyboard again
Made on a tuesday · April 2026
“the anti-saas saas”
$0.00 · gary’s discretion
small saas · big shoulders

Glue every Google + Notion account you own into one MCP server your AI can actually use.

Get an invite →
no credit card · no demo call · no “book a slot”
↓ keep reading ↓
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR email.
AI CAN’T READ YOUR email.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR email.
AI CAN’T READ YOUR email.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR EMAIL.
AI CAN’T READ YOUR email.
AI CAN’T READ YOUR email.
“We built three integrations, two OAuth flows, and a Slack bot — all so an LLM could see one calendar invite.”— every founder, last month
how it works (briefly)

three (boring) steps,
one URL per service.

01

Get an invite.

Signups are gated. Message Gary on LinkedIn, offer him something he wants — an intro, advisory equity, a podcast slot — and he hands over an invite link. He has standards.

barter with gary →
he’s online ↗
02

Bind accounts.

Sign in with Google. Pick which scopes to share — gmail, drive, calendar, notion. Add as many addresses as you like, each under its own label. We don’t mix them.

> mcportal · server ready services : 4 tools : 26 status : LIVE
tools.list ✓
03

Paste the URL.

Drop a service URL into Claude Desktop, ChatGPT, Cursor, Zed — anything that speaks MCP. Now your model can read your inbox, draft replies, find that doc from October, and book the dentist.

mcportal/gmail/mcp
mcportal/drive/mcp
mcportal/calendar/mcp
mcportal/notion/mcp
that’s it.
no servers,
no SDK,
no slack.
what’s in the box

boring on purpose. does the thing.

001

UNLIMITED
ACCOUNTS

Personal, work, side-project, the one you used in 2014. All under one user, each on its own label. Tag them, route them, ignore them.

002

READ +
WRITE

Draft, send, archive, label. Or read-only — your call, per scope, per account.

003

DRIVE
SEARCH

Full-text. Across every account. Returns the actual file your AI needs, not a list of 84 maybes.

004

CALENDAR, BUT GOOD.

Free/busy across every account at once. Book without the “let me check my other calendar” loop.

005

TOKEN
HYGIENE

OAuth refresh, scope trimming, revocation in one click. We never see your password — Google holds the keys.

006

WORKS EVERYWHERE

Claude Desktop. ChatGPT. Cursor. Zed. Cline. Continue. If it speaks MCP, it speaks us.

007

NOTION TOO

Pages, databases, search. Same per-account labelling pattern as Google. Your AI sees one merged catalog.

008

SCOPED, NOT SCRAPED.

Tool calls go straight through to Google / Notion. Nothing is mirrored, scraped, or cached on our side.

questions, asked frequently

but wait,
questions.

01.
Do you store my emails?
No. We store OAuth refresh tokens (encrypted at rest) and a per-server config. Every request to the MCP endpoint hits Google live. We don't cache your inbox, your docs, or your calendar.
+
02.
How do I sign up?
You barter with Gary. Specifically: message Gary Botlington IV on LinkedIn, offer him something he wants (an intro, equity, a podcast slot, weekend at the beach house), and if he likes the offer he sends you an invite link. Click the link, sign in with Google, done.
+
03.
Can I limit scopes per account?
Not yet, we're working it.
+
04.
What about Outlook / Linear / Slack?
Not yet. The product is on purpose: Google + Notion accounts only. If we add others, the URL won't change — you just get more tools.
+
05.
How is this different from writing my own MCP server?
It isn't, philosophically. We just did it for you, deal with the OAuth refresh hell, and keep up with Google's API churn. If you enjoy maintaining tokens at 2am, please don't subscribe.
+
06.
Why is the signup flow like this?
Why shouldn't it be like this?
+
SIGN UP. SIGN UP. SIGN UP.
JUST. SIGN. UP.

Get an invite.

No demo call. No SDR. One LinkedIn message to a man named Gary.

message gary on linkedin →
already have a code? redeem it →