Stedia connects to 18 tools, including Outlook, Gmail, SharePoint, Google Sheets and Shopify, and sees exactly what the connected account may see. Your own systems, such as an ERP or a booking system, connect through their API with Tool studio, or as an MCP server.
Connected tools: what the workspace already uses, what is ready to connect, and your own API. Example data.
How it works
Connect a tool
Open “Connected tools”, pick a tool and sign in with that provider.
Choose who uses it
Keep the connection personal, or share it with the whole workspace.
Stedia works in it
Stedia reads without asking, and every action that writes asks you first.
18 tools, built in
OutlookRead mail and events, draft, send and book
Microsoft TeamsRead channels and chats, post, set up meetings
GmailRead, draft, answer and send mail
SharePointSearch sites, libraries and lists, upload files
OneDriveSearch, read and download files, upload and share
ExcelFind workbooks, read cells, write and append rows
Google DriveFind, read and download files, upload and share
Google SheetsRead cells, write and append rows
Google DocsRead, write and comment on documents
Google CalendarCheck availability, propose times, book events
Google TasksRead, add and complete tasks
ShopifyRead orders and products, update products
SlackRead channels, post and reply under your name
And 4 more for development teams
Your own systems, connected
Tool studio: the time tracking system is published with four actions, accounting is still a draft. Example data.
MCP servers: the client portal, published with five actions. Example data.
In detail
The tools in the catalog
18 tools ship with Stedia, among them Outlook, Gmail, Microsoft Teams, SharePoint, OneDrive, Excel, Google Drive, Docs, Sheets, Calendar and Tasks, Shopify and Slack. Under “Connected tools”, the catalog groups them into connected, ready to connect and off for the workspace. Each tool’s page in the help center lists its actions and which of them ask first.
Personal or for the workspace
When you connect a tool, you choose who uses that sign-in. “Personal” stays yours. “Workspace” shares it with everyone, and they all act through that one account. So connect your mailbox as “Personal”. When a connection stops working, a notice names the tool, and “Fix connection” opens it.
The AI never sees your passwords
Stedia encrypts every sign-in and key before it saves it. The AI model never sees these passwords, tokens or keys: Stedia’s server calls the tool itself and passes the model only the result. To remove a connection for good, click “Disconnect” on the tool.
Tool studio for your own systems
With Tool studio, an admin connects one of your own systems, such as an ERP, a booking system or your accounting, through its API: “Add your own”, then “Import an API”. Pick up to 15 actions and mark each one that needs a person’s approval as “Asks first”. After publishing, it is connected like any other tool. Tool studio comes with Business and Enterprise.
MCP servers
If a service such as your client portal offers an MCP interface, a ready-made connection for AI assistants, it becomes a tool of its own: “Add your own”, then “Add an MCP server”. An owner or admin picks up to 25 of its actions and sets for each whether it asks first. If the server later rewrites an action, Stedia pauses it as “Changed” until an admin confirms the new text. MCP servers work on every plan.
What the workspace may use
Under Settings → Tools and knowledge, owners and admins decide what Stedia may reach: web search, image creation, each connected tool and each knowledge base. A tool switched off there is left out right away, even for people who connected it themselves. On Business and Enterprise you set this per team, and nothing is deleted when you switch something off.
Hosted in the EU, AI in the EU if you choose. Built in Austria, GDPR compliant.