The Library
Part of the MountDev Ops Integrations documentation. 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.
What You See
The Library lists every integration the platform offers, one row each: its name, what it does, what it needs (a key or a sign-in), which apps use it, and whether you have connected it. The pill says Working, Needs Attention, Not Checked, or Not Connected. Read the guide opens that service's section in Services in the Library. The list comes from action integrations.library.
Search the list by name or by what it does. What It Does keeps one kind (take payments, phone and text, send email, search and speed, host and protect websites, customer support, or AI). Used By keeps the integrations that one app uses. With nothing matching, the page says so and points to Request an Integration.
Connect
Connect (or Sign In, for a service that works by sign-in) on a connection opens a pop up that says what the service does, where to find its key, and which apps use it. Paste the key and select Connect. The key is checked for its shape, sealed with your own account's encryption key, and saved. It is never shown again, to anyone, and is never put in a log, an email, an address, or an answer (action integrations.save). Stripe and Zoho Desk have a few more steps, which their pop ups walk through.
A key that does not look right is refused beside the button, in plain words, before anything is saved. Owners, admins, and anyone whose role allows managing connections see Connect. Everyone else can browse the library, and the page says who to ask.
A link or a migrator has Open instead, which goes to its own screen. Open needs no key of its own.
Through an Assistant or the API
Your own AI assistant, or a connection you made in Connections, can read the library (action integrations.library, tool integrations_list) and ask to connect a service (action integrations.connect, tool integrations_connect). Asking waits for an owner or admin to say yes in the workspace. Saying yes does not connect anything and no key passes through the assistant: the service shows "An assistant asked to connect this" on the Library until a person adds its key or signs in. Nothing the assistant can read or send ever holds a key.
New Integrations
Each integration is declared by an app in its own manifest: its name, its group, its kind, what it does, what it needs, which apps use it, the permission that connects it, and its docs. The groups are described there too, with a name, a one-line summary, and an icon. The Library builds itself from those declarations, so a new integration appears as soon as it is live, with nothing else to change.