Connect your apps. Add any MCP server.
SAAM can use any tool server that speaks MCP, and your apps as the catalog switches on. You choose which agents may use each one, and anything that sends or changes something asks first.
Rolling outWhat it does
- Adds an MCP server from its web address, with a sign-in window if it needs one.
- Lets you pick which of your agents may use each server.
- Connects apps through a sign-in window as the app catalog is switched on.
How to start
- Open Integrations, choose Browse MCP servers, paste the address, tick the agents, then ask SAAM to use it.
Limits
- The one-click app catalog is built and rolling out. It is not switched on for everyone yet.
- Servers that run local programs are turned off.
- Tools that send, create or delete ask first unless you set a rule.
Paste an address. Pick who may use it.
MCP is an open way for tools to talk to an agent. Add a server from its https address. If it needs a sign-in, a window opens and you approve it.
Then choose which of your agents may use it. You can also ask SAAM in chat to add a server, and an approval card asks you to authorize it.
- TTravelOn
- HHomeOn
- FFamilyOff
Integrations, Browse MCP servers: search the public directory and find the Add server URL field. Nothing is connected in the recording. 23 seconds.
Paste the address
An https address. Streamable HTTP and SSE servers work.
Sign in if it asks
OAuth is supported, or you can add an access token.
Pick the agents
Only the agents you tick can use the server.
Ask SAAM to use it
Say what you want. It picks the right tool.
Apps connect through a sign-in window.
Gmail, Calendar, Drive, Notion and Slack are first on the list. You approve each one in a sign-in window, on your own account, and you can disconnect it from the app's page. The app catalog is built and is rolling out now. Until it is switched on for you, the MCP route is the way to connect a tool. Apps connect through a third-party connector service, which the privacy policy covers.
MCP servers
Add one by address. Works today.
LiveAdd from chat
Ask SAAM to add a server and approve it on a card.
LiveOne-click apps
A catalog of apps with a sign-in window each.
Rolling out
Anything that changes something asks first.
Looking things up runs on its own. Sending, creating, updating, posting and deleting wait for your yes. If SAAM cannot tell what a tool does, it asks.
Set a rule to always allow or always ask, per tool, per app or per kind of action, in Settings, General, Advanced. Jobs started by a webhook always ask before they change anything.
get_eventsRuns on its ownsearch_notesRuns on its ownsend_messageAsks firstdelete_fileAsks firstdo_thingAsks first (not sure)
Reads
Get, list, search and read run without a card.
Changes
Send, create, update, post and delete ask first.
Not sure
A tool SAAM does not recognise asks first.
Servers belong to you.
Each server belongs to your account, its sign-in details are stored encrypted, and only the agents you pick can use it. SAAM refuses addresses that point at private networks, and each call times out after 30 seconds.
Meet SAAM.
Open SAAM on the web and say what needs doing. It starts learning how you like things done.

