MountDev Ops Integrations
How MountDev Ops Integrations works, page by page. Updated November 7, 2026
MountDev Ops Integrations documentation | Updated November 7, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 3,437 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
Tested Every Release
All 21 of Integrations's own automated checks run on every update, plus 36 screen tests whenever Integrations's screens change.
What they cover: Roles and permissions | AI agents and API keys
What Integrations Is
Integrations is the library of every outside service MountDev Ops works with, such as Stripe, Telnyx, Amazon SES, and Google's search tools. You browse the library, connect a service with your own key or sign-in, and see at a glance whether each connection is working, when it was last checked, and which apps use it. Your API keys, webhooks, automations, and inbound webhooks are here too.
Everything about your connections lives in your own account, in your own region: which services are connected, how each last checked, and the requests you filed. Each key is sealed with your account's own encryption key, is never shown again, and is never kept anywhere else. The platform has no key of its own for any of them.
In These Docs
- The Library: browse and search every integration, connect one, and what an assistant can and cannot do here.
- My Connections: health, the last check, which apps use each, replacing a key, and disconnecting with a warning of what will stop.
- Request an Integration: ask for a service that is not in the library, and what is sent.
- Services in the Library: each service, what it does, what it needs, and where to find its key.
- Integrations Settings: who can connect and disconnect, and how the old Settings, Connections addresses work.
Who Can Do What
- See the library and how each connection is doing (owners, admins, members, and anyone whose role allows it).
- Connect and disconnect integrations, and replace their keys (owners, admins, and anyone whose role allows managing connections).
- Your own AI assistant or an API key can read the library and the health, ask to connect a service, and disconnect one. It can never send or see a key: connecting waits for an owner or admin to say yes, and then for a person to add the key.