Assistly now speaks MCP: connect Notion, Linear, and any tool to your live assistant
By The Assistly team ·
A live assistant is only as good as what it knows. Assistly already grounds its guidance in your persona, your knowledge modes, and the conversation itself — but the facts that win a call often live somewhere else: the spec in Notion, the ticket in Linear, the number you'd normally have to go dig up.
Now you can bring those sources with you. Assistly supports MCP (Model Context Protocol) — the open standard for connecting AI assistants to external tools — so any MCP server you connect becomes part of your assistant's toolkit.
What is MCP, and why does it matter?
MCP is an open protocol that lets an AI assistant discover and call tools exposed by other services — search a knowledge base, look up a record, create an issue — through one standard interface. Instead of waiting for us to build a bespoke integration for every product you use, you connect the server and Assistly can use whatever tools it offers.
That flips the usual limitation of meeting copilots. Most can only reason about what they hear. With MCP connected, you can ask a question mid-call and get a response grounded in your actual data:
- "What did we promise in the Acme proposal?" — pulled from your Notion workspace, not from memory.
- "Is the migration ticket still blocked?" — checked against Linear while the client is still talking.
- "What's the latest on their funding round?" — fresh web results via a search server like Tavily.
And because MCP tools can act, not just read, you can finish the loop without leaving the overlay: "file a Linear issue for the bug we just discussed" or "add these action items to Notion" — done before the call ends.
How it works
Open the avatar menu → Integrations and add a server: give it a label, paste its URL, and Assistly detects how it authenticates — no setup for public servers, a pasted API key for token-based ones, or a standard OAuth sign-in for servers like Linear's hosted MCP, where you approve access in your browser and you're done. A built-in connection test confirms everything works before you rely on it, and you can connect up to 20 servers.
From then on, every typed question in a session can use your enabled integrations. When the assistant calls a tool, you'll see it work — a brief "Working…" state, then a "Used …" badge on the result, so you always know when a response came from your connected data rather than the model alone.
Live, automatic guidance stays instant by design: Auto-assist and other real-time guidance never wait on an external tool, so nothing slows down the moment a question lands. Your tools enrich the questions you type; the split-second stuff stays split-second.
Built to be trusted with your keys
Connecting your tools to anything should raise the "is this safe?" question, so here's the posture:
- HTTPS only, remote servers only — every connection is validated, and requests can never be pointed at private or internal addresses.
- Your credentials stay write-only. API keys and headers you save are never shown back in the UI and never logged.
- OAuth done properly — servers that support it use the standard MCP authorization flow with PKCE, so you grant access in your browser and can revoke it at the source any time.
- You're in control. Toggle a server off and it's out of the loop immediately; delete it and the credentials go with it.
And as with everything in Assistly, the overlay showing those tool-powered responses is excluded from screen capture at the OS level — your connected data never appears in a screen share or recording.
Why this is the direction live assistance has to go
The gap between a generic response and a winning one is context. An interviewer doesn't want the textbook take; a prospect doesn't want boilerplate — they want your numbers, your roadmap, your history with them. MCP is how that context stops being something you paste in and starts being something your assistant simply has.
It's also why we chose an open standard over a walled garden of one-off integrations: the ecosystem of MCP servers is growing weekly — docs, CRMs, issue trackers, search — and every one of them works with Assistly the day it exists.
Get started
Update to the latest Assistly for macOS or Windows, open the avatar menu → Integrations, and connect your first server. Pair it with Auto-assist for hands-free help and your calendar for schedule-aware context.
As always, use live assistance within the rules of the meeting, call, or interview you're in, and mind recording-consent laws where participants are.
Try Assistly free — and bring your tools with you.