Integrations Permissions for Connections
Part of the MountDev Ops Integrations documentation. Updated November 7, 2026
MountDev Ops Integrations documentation | Updated November 7, 2026
These are the permissions a connection can hold in Integrations. Each one is a single action. Pick only what the connection needs. A connection acts as the member who made it and never does more than that member could.
| Permission id | Level | What it does | Inputs |
|---|---|---|---|
integrations.connect | Write | Ask to connect an integration | service (required) |
integrations.disconnect | Write | Disconnect an integration: its saved key is removed and the apps that used it stop | id (required) |
integrations.health | Read | See how each connection is doing: working, needs attention, and when it was last checked | none |
integrations.list | Read | See every integration, whether it is connected, and how it is doing | none |
Ask to Connect an Integration
Permission integrations.connect | Write | MCP tool integrations_connect (action integrations.connect)
POST /account/api/v1/actions/integrations.connect
{"service":"Example"}Disconnect an Integration: Its Saved Key Is Removed and the Apps That Used It Stop
Permission integrations.disconnect | Write | MCP tool integrations_disconnect (action integrations.disconnect)
POST /account/api/v1/actions/integrations.disconnect
{"id":1}See How Each Connection Is Doing: Working, Needs Attention, and When It Was Last Checked
Permission integrations.health | Read | MCP tool integrations_health (action integrations.health)
POST /account/api/v1/actions/integrations.health
{}See Every Integration, Whether It Is Connected, and How It Is Doing
Permission integrations.list | Read | MCP tool integrations_list (action integrations.library)
POST /account/api/v1/actions/integrations.list
{}