New · Bring your own tools
Your employees arrived knowing their craft. Now you can hand them the tools your business already pays for — Notion, Stripe, Slack, Higgsfield, even your own internal systems — through one open standard. Paste a URL, tick a name, and a specialist who could only advise starts operating.
🔌 The equipment room
live wiringone socket
The idea
Every SaaS era had its walled gardens — "integrations" that took quarters and consultants. The AI era quietly standardized the plug instead. We built the socket into every employee.
The Model Context Protocol is an open standard the AI industry settled on: one plug shape for every tool. If a service speaks MCP, anything that speaks it too can use that service. Your employees speak it fluently.
Project boards, payment platforms, CRMs, design suites, databases, calendars — the ecosystem is compounding monthly. Every new MCP server anyone ships is, automatically, a new skill your team can pick up the same day.
Paste a server's address in Settings → Integrations. We connect, list what it can do, and you hand those abilities to any employee like gear from a shelf. No integration project. No waiting for us to 'support' it.
Sixty seconds, start to finish
01
A URL, plus an API key or a sign-in with the service — whichever the tool uses. Keys are stored encrypted; OAuth means we never see your password.
Server URL
https://mcp.notion.com/mcp
Connect
02
We connect once and lay out every tool the server offers — by name, before anything runs. You always know exactly what you just wheeled into the office.
03
Equipment is per employee, not global. Tick a box in Marcus's room and he carries Stripe; Sofia doesn't. The same server can arm one specialist or the whole floor.
04
Flip a server to 'Asks you first' and every call becomes an approval card in chat. Nothing that spends credits, posts publicly, or writes data runs without your tap.
Needs your approval
Higgsfield · generate-video
Allow
A true story from our own office
While building this very feature, our founder plugged Notion in and asked Sofia a question that had nothing to do with SEO: "there's a board I keep for a client — what's still open on it?"
She searched the workspace, asked permission with an Allow card, read the board, and came back with the three open tasks — statuses, links, and a "want me to mark anything done?" This is the conversation on the right, pixel for pixel.
Nobody wrote a Notion integration. Nobody waited for a roadmap. A URL got pasted, and an employee got more useful — that's the whole feature.
Sofia
SEO Specialist · carrying: Notion
Notion · notion-search
🔌 Server: Notion
Scene two — the production line
The boss wants a viral ad. Ivy answers like a producer, not a prompt box: a storyboard — hook, problem, product, proof, offer, CTA. Six clips, five seconds each.
Watch the two kinds of hands work together. The frames she designs herself — that skill shipped with her. The motion comes from your Higgsfield subscription, plugged in through MCP like gear from the equipment room.
And between the plan and your credits sits exactly one thing: an Allow card. Six renders, one approval, zero surprise invoices. The timeline fills, the cut assembles, and she's already asking about the 9:16 for Reels.
Ivy
Designer · carrying: Higgsfield
Storyboard — designing frame 1/6
Higgsfield · image-to-video × 6
🔌 Server: Higgsfield
The gallery
Same employees you've met on this site — with tools in their hands. Every scene follows the house rules: evidence first, Allow cards on anything that spends, everything in the ledger.
Your internal stack
Custom hire · Ops Runner
“Check the booking system — is anyone double-booked next week?”
This is the scenario no off-the-shelf tool can ship: an employee fluent in software that exists nowhere else on earth but your company.
Stripe
Iris · Analyst
“How did this month actually go? New MRR, churn, anything weird.”
“New MRR +$1,840, churn 2 accounts (both trial-enders), and the 14th spike is Marcus's campaign paying off — 11 of 14 new subs came through it.”
Notion
Sofia · SEO
“There's a board I keep for this client — what's still open?”
Searches your workspace, finds the board, reads the tasks and statuses.
A clean checklist back in chat — and she can tick items off as she ships them.
Slack
Nora · Support
“Post the morning summary to #ops before the team logs in.”
Compiles overnight tickets, drafts the digest, posts on Allow.
Your human team wakes up to a briefing written by your AI team.
Shopify
Marcus · Ad Manager
“Push the winners harder — but only what we can actually sell.”
Checks stock levels before raising budgets; pauses ads for sold-out SKUs.
No more paying Google to advertise an empty shelf.
HubSpot
Aria · Assistant
“Yesterday's campaign leads — get them into the CRM properly.”
Dedupes against existing contacts, logs source and campaign, flags the two hot ones.
Sales opens a clean pipeline instead of a spreadsheet with 40 rows of chaos.
Google Calendar
Nina · Scheduler
“When the report lands each Friday, get it on my calendar to review.”
Books the slot, attaches the report link, avoids your existing meetings.
The review actually happens, because it exists where your day exists.
GitHub
Custom hire · Release Watcher
“Watch our repo. When a release ships, draft the announcement.”
Reads the release notes, turns changelog into customer language.
Every release gets announced — even the ones that ship at 11pm.
Postgres
Iris · Analyst
“How many signups came from the new landing page, really?”
Runs a read-only query against your own database via an MCP gateway.
The answer comes from the source of truth, not from a dashboard's cached guess.
Zendesk
Nora · Support
“Nothing should sit unanswered for more than a day.”
Pulls every ticket older than 24h each morning, drafts replies for the stale ones.
The queue's embarrassing tail simply stops existing.
Airtable
Maya · Content
“Keep the editorial calendar honest.”
Marks published pieces, spots the empty week, proposes three topics with briefs.
The calendar stops being a graveyard of good intentions.
Linear
Nora · Support
“When customers report bugs, I want them filed properly — not lost in chat.”
Turns support conversations into structured issues: steps, impact, frequency.
Engineering gets reproducible tickets; customers get 'it's fixed' messages that are true.
The multiplication
0s
of MCP servers in the wild, growing monthly
× 0
specialists in the catalog — plus every custom hire you build
= ∞
job descriptions nobody has to wait for us to ship
This is the part we're most excited about: the org chart stops being a menu we curate. An accountant who reads your Stripe. A producer who runs your Higgsfield. A dispatcher who lives in your booking system. If a tool speaks MCP — official, open-source, or written by your own developer for your own stack — it's a job description waiting to be hired.
Handing tools to an autonomous employee only works if the boss holds the breaker. The same control system that guards your ad budget guards your equipment.
Per server, flip 'Asks you first' and every call becomes an approval card in chat. Video credits, public posts, data writes — your tap is the switch.
API keys and OAuth tokens are encrypted at rest (AES-256-GCM). They're sent to one place only: the server they belong to.
Services with official sign-in flows (like Higgsfield) authenticate on their own pages. You consent there; we hold a revocable token, not your credentials.
Every call — who ran it, on which server, what came back — is logged like every other action your employees take. Nothing happens off the books.
Equipment is assigned per employee and taken back the same way. Disable a server and every tool from it goes dark instantly, office-wide.
A small service that exposes a tool's abilities (search, create, update…) in a standard format AI systems understand. Many companies now ship official ones — Notion, Stripe, Higgsfield and hundreds more — and open-source ones exist for almost everything else.
No. You paste an address, maybe an API key from the service's settings page, or just sign in when the service supports it. Connecting takes about as long as reading this sentence. Your employees handle the actual tool-driving.
Any remote MCP server — the kind reachable at a URL, with no auth, an API key, or an OAuth sign-in. That covers the official servers from major products and most of the ecosystem. Local-only servers (software running on your own laptop) aren't supported.
That's what the approval layer is for: servers default to 'Asks you first', so every call arrives as an Allow card before it runs. Add encrypted key storage, OAuth flows, per-employee assignment and full ledger logging — you get power tools with the safety switches built in.
No — plugging in tools is part of every plan, including Free. The external service's own subscription (your Notion workspace, your Higgsfield credits) stays yours, on your account, under your control.
Yes — and this is the quiet superpower. If your developer wraps an internal system in a small MCP server (a well-documented afternoon of work), your employees learn YOUR stack: your admin panel, your inventory system, your booking engine. That's a skill no off-the-shelf SaaS can ship.
The equipment room is open
Free in beta. Plug in your first server in about a minute — the DeepWiki server needs no key at all, if you just want to feel it work.
Open the equipment room →