Who is in the catalog
The catalog lists vendors that run their MCP server themselves and let Stedia sign in directly. Pick one, and the server is filled in for you, so nobody has to look up an address. You can still add any other MCP server by hand.
More tools via MCP
Connect new tools, and you still decide what Stedia may do.
For 29 vendors such as Notion, DeepL and Stripe, the connection is already prepared. You choose up to 25 actions per vendor, and by default anything that changes something waits for your approval. If the vendor changes an action later, Stedia pauses it until an admin confirms it.
How it works
- Pick the vendor
Under “Connected tools”, in “More tools via MCP”, for example “Add Notion”.
- Sign in and choose actions
You sign in with the vendor and choose up to 25 of its actions.
- Publish
Everyone in the workspace connects it like any other tool and uses it in chat, assistants and schedules.
29 vendors, ready to connect
NotionSearch, read and write pages and databases
monday.comRead and update boards, items and updates
ClickUpFind, create and update tasks, lists and docs
AirtableRead and change records in your bases
MiroRead boards and add content to them
DeepLTranslate and rephrase text
ZapierRun the actions you set up in Zapier
StripeLook up customers, payments and invoices
PayPalCreate invoices and look up transactions
WebflowRead and edit pages and CMS collections
WixManage site content, store products and bookings
Jira and ConfluenceSearch and update Jira issues and Confluence pages
CalendlyLook up event types and bookings, share scheduling links
KlaviyoRead profiles, lists and campaign results
MakeRun the scenarios you built in Make
JotformRead forms and their submissions
RampLook up transactions, cards and reimbursements
WordPress.comRead and edit posts, pages and site settings- And 11 more for development teams
In detail
You choose the actions
Stedia reads what the server offers, and you choose up to 25 actions. For each one you set whether Stedia asks first and whether its output counts as untrusted. Both stay on unless you change them.
Checked before it goes live
Before you publish, the review shows how many actions there are, which of them ask first and which another tool already covers. Nothing from the catalog goes live on its own.
When the vendor changes something
A vendor can rewrite an action at any time. Stedia compares every action with what you approved, pauses a changed one as “Changed” and shows the old and new text side by side until an admin confirms it.
Everyone signs in for themselves
Each member signs in to the vendor with their own account, and Stedia sees only what that account sees. Credentials are stored encrypted, and the AI never sees them.
On every plan
MCP servers work on Pro, Business and Enterprise. Owners and admins see the catalog. For Jira and Confluence, your Atlassian admin has to allow Stedia first, and the catalog tells you how.
Hosted in the EU, AI in the EU if you choose. Built in Austria, GDPR compliant.
More on EU sovereigntyRelated
Give Stedia
its first task.
Your unpaid invoices, for example. Free for 14 days, then cancel any month.