Salana
Product · Integrations
It is the memory that is connected, not the app. Your Salana Memory reaches your other systems through MCP, the open standard for connecting AI to tools; the Salana App is the visual tool working on top of it. Connect an app to the memory once and every agent, chat and automation can use it: read your mail, update the CRM, post the listing, pull the numbers.
MCP stands for Model Context Protocol. It is an open standard, published by Anthropic in late 2024 and since adopted across the industry, that describes how an AI model connects to an outside system: which tools the system offers, what each one takes and returns, and how to call it safely. A system that speaks MCP is an MCP server; the model is the client.
Before MCP every AI product wrote its own integration for every app, and every app wrote one for every AI. With MCP an app publishes one server and any model can use it. It is becoming the plug that connects systems together, the way USB did for hardware. Gmail, Notion, GitHub, HubSpot, Stripe, Slack and hundreds of others already have one.
The list of connected MCP servers is part of the folder, next to the notes and the automations. Every agent that opens the memory, in any chat and any scheduled turn, starts with that list. Connect a tool once and it is available everywhere the memory is.
A tool with its own login (Notion, GitHub, HubSpot) is signed in once; the Salana App gives you the button, and the connection is kept with your memory. Keys for the rest are referenced by name and kept in your environment, never written into the folder.
Ask “what did the customer write last week” and the agent reads the mailbox; “add them to the CRM” and it does, in the same turn, with the memory's context around it.
A schedule runs with the same tools: the receipts harvester reads Gmail, the listing poster publishes to Instagram, the signal webhook writes a draft. Tokens are refreshed by the connector, so schedules keep working.
Anything with a URL and a key. Robert's companies expose their admin data as MCP servers (a CRM, a listings platform, a trading platform) and every agent reads them like any other tool.
An aggregator such as Composio connects Gmail, Google Calendar and Drive, Slack, HubSpot, Meta Ads, Stripe and more through one server, with the sign-ins hosted for you.
Thirty of the most common, each with an MCP server today. Connect one to your memory and every agent can use it.
The Salana App's Settings has a tool catalog for connecting to the memory directly: Composio, Gmail, Google Calendar, Google Drive, Slack, HubSpot, Notion, GitHub, Linear, Stripe, PayPal, Square, Atlassian, Asana, monday.com, ClickUp, Intercom, Sentry, Vercel, Netlify, Supabase, Neon, Cloudflare, Figma, Canva, Webflow, Wix, Cloudinary, Hugging Face, Zapier, and any MCP server by URL. Search for a tool that is not listed and the catalog finds its server.
The integrations are not where your value sits; they are pipes into the memory. What comes through them is written into the folder as records you own: the mail becomes a receipt in the archive, the platform stats become a CSV, the CRM change becomes a log line. Swap a tool and the history stays. Swap the AI, or the app you look at the memory through, and the tools stay connected, because they are connected to the memory and the standard is the same on both sides.
Your files, every model, yours forever.