--- title: "SuperOps RMM+PSA MCP server for AI agents - actionlake" description: "Give Claude 143 SuperOps RMM+PSA actions through one MCP server: client users, clients. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/superops-rmm-psa updated: 2026-10-23 --- Connectors · MSP & PSA # SuperOps RMM+PSA MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to SuperOps RMM+PSA and the rest of your systems. It gives your agent 143 SuperOps RMM+PSA actions (78 reads, 50 writes and 15 that wait for a confirmation) and holds the SuperOps RMM+PSA credential itself, so the agent never does. It paces SuperOps RMM+PSA's limits and records every call. [Connect SuperOps RMM+PSA free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "superops.client_users.list", intent: "check which SuperOps RMM+PSA account is connected" } # List SuperOps client users · read · 1 upstream call ``` - 143 actions in one signed file - 78 read look, never change - 50 write create and update - 15 wait for a yes destructive, confirmed first Set up ## Connect SuperOps RMM+PSA in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect SuperOps RMM+PSA. Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_token` SuperOps API token - `customer_subdomain` Your SuperOps subdomain (the `acme` in acme.superops.ai) - `host` Where your SuperOps RMM+PSA lives: your host ``` account { op: "connections.requirements", service: "superops" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "superops.client_users.list" } # list superops client users · read · 1 upstream call check { action: "superops.client_users.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` SuperOps RMM+PSA at a glance **Sign-in** Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_token` `customer_subdomain` **Setup fields** `host` **Limits we pace to** 800 calls a minute, per connection **API covered** SuperOps API msp, at your SuperOps RMM+PSA instance's API base URL, which you enter when connecting **Built from** SuperOps RMM+PSA's documentation, read 23 October 2026[developer.superops.com](https://developer.superops.com/msp) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 78 of 78 reads, for up to an hour; a write clears what it affects **Shared entities** 9, so ask can line SuperOps RMM+PSA up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in SuperOps RMM+PSA. 143 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest. - **78** read look, never change - **50** write create and update - **15** destructive wait for a confirmation 1. ### PSA RMM 143 78 read · 50 write · 15 destructive List SuperOps client users · List SuperOps clients · List SuperOps client sites · List SuperOps technicians Top actions ## The SuperOps RMM+PSA API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 47 of SuperOps RMM+PSA's 47 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `superops.client_users.list` List SuperOps client users | Fetches a list of client users | read | `crm.contact.list` 177 connectors | | `superops.clients.list` List SuperOps clients | Fetches a list of clients | read | `crm.company.list` 162 connectors | | `superops.client_sites.list` List SuperOps client sites | Fetches a list of client sites | read | `crm.location.list` 48 connectors | | `superops.technicians.list` List SuperOps technicians | Fetches the list of technicians | read | `identity.user.list` 474 connectors | | `superops.client_users.create` SuperOps client users: create | Creates a new client user | write | `crm.contact.create` 161 connectors | | `superops.clients.create` SuperOps clients: create | Creates a client | write | `crm.company.create` 142 connectors | | `superops.tickets.list` List SuperOps tickets | Fetches a list of tickets | read | `service.ticket.list` 56 connectors | | `superops.tasks.list` List SuperOps tasks | Fetches a list of tasks | read | `work.task.list` 122 connectors | | `superops.client_sites.create` SuperOps client sites: create | Creates a client site | write | `crm.location.create` 41 connectors | | `superops.invoices.list` List SuperOps invoices | Fetches a list of invoices | read | `finance.invoice.list` 101 connectors | | `superops.client_users.delete` SuperOps client users: delete | Deletes the records of an existing client user | destructive | `crm.contact.delete` 147 connectors | | `superops.client_contracts.list` List SuperOps client contracts | Fetches a list of client contracts | read | `service.contract.list` 23 connectors | Try it ## Prompts to paste into Claude. Each one names the SuperOps RMM+PSA actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which SuperOps RMM+PSA invoices are more than 30 days overdue? Group them by customer with the total owed. calls `superops.invoices.list` 2. Write write SuperOps client users: create in SuperOps RMM+PSA. Show me exactly what you will send before you save it. calls `superops.client_users.create` 3. Across systems read For each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in HubSpot CRM? calls `superops.invoices.list` `hubspot_crm.tickets.list` Across your systems ## SuperOps RMM+PSA, joined to the rest of your business. One `ask` fetches from SuperOps RMM+PSA and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - For each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in HubSpot CRM? `superops.invoices.list` + `hubspot_crm.tickets.list`, on `crm.company` · [HubSpot CRM](https://actionlake.com/connectors/hubspot-crm) - For each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in ServiceNow? `superops.invoices.list` + `servicenow_table.incidents.list`, on `crm.company` · [ServiceNow](https://actionlake.com/connectors/servicenow) Also mapped by other connectors `identity.user` **517** `crm.company` **227** `crm.contact` **192** `work.task` **105** `finance.invoice` **91** `service.ticket` **62** `crm.location` **49** `asset.asset` **40** ask ``` ask { intent: "for each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in HubSpot CRM", steps: [ { action: "superops.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 }, { action: "hubspot_crm.tickets.list", as: "tix", input: {}, limit: 100, max_pages: 5 }, { join: { left: "inv", right: "tix", on: "crm.company", group_by: "inv.company_name", select: ["inv.company_name", "count(inv.id) as invoices", "count(tix.id) as tickets"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. Governance for SuperOps RMM+PSA ## Destructive actions wait for a yes. 15 SuperOps RMM+PSA actions are destructive. These are all of them: - SuperOps client users: delete `superops.client_users.delete` - SuperOps clients: delete `superops.clients.delete` - SuperOps client sites: delete `superops.client_sites.delete` - SuperOps technicians: delete `superops.technicians.delete` - SuperOps tickets: delete `superops.tickets.delete` - SuperOps assets: delete `superops.assets.delete` - SuperOps worklog entries: delete `superops.worklog_entries.delete` - SuperOps clients: trash `superops.clients.trash` - SuperOps fields: delete `superops.fields.delete` - SuperOps tickets: trash `superops.tickets.trash` - SuperOps assets: run script `superops.assets.run_script` - SuperOps kb articles: delete `superops.kb_articles.delete` - SuperOps it documents: delete `superops.it_documents.delete` - SuperOps kb collections: delete `superops.kb_collections.delete` - SuperOps client user associations: delete `superops.client_user_associations.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do superops.client_users.delete confirm_policy: **human** SuperOps client users: delete? **intent:** the user asked me to superOps client users: delete run suspended · waiting for a named person · key _superops-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "superops-agent", allowed_actions: ["superops.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "superops.client_users.delete", approver: "lead@example.com" }, { match: "superops.clients.delete", approver: "lead@example.com" }, { match: "superops.client_sites.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to SuperOps RMM+PSA only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What SuperOps RMM+PSA costs on actionlake. Every SuperOps RMM+PSA action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call SuperOps RMM+PSA refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 143 SuperOps RMM+PSA actions - 26 actions page each page of a long list is one call - 78 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every SuperOps RMM+PSA action. 143 actions by area: the id your agent calls, what it does, and its effect. **PSA RMM 143** - `superops.alerts.create` SuperOps alerts: create write - `superops.alerts.list` List SuperOps alerts read - `superops.alerts.list_for_asset` SuperOps alerts: list for asset read - `superops.alerts.resolve` SuperOps alerts: resolve write - `superops.asset_class_custom_fields.list` List SuperOps asset class custom fields read - `superops.asset_custom_fields.list` List SuperOps asset custom fields read - `superops.assets.activity` SuperOps assets: activity read - `superops.assets.assign_device_category` SuperOps assets: assign device category write - `superops.assets.by_third_party_endpoints` SuperOps assets: by third party endpoints read - `superops.assets.delete` SuperOps assets: delete destructive - `superops.assets.disks` SuperOps assets: disks read - `superops.assets.get` Get SuperOps assets read - `superops.assets.list` List SuperOps assets read - `superops.assets.patch_status` SuperOps assets: patch status read - `superops.assets.patches` SuperOps assets: patches read - `superops.assets.run_script` SuperOps assets: run script destructive - `superops.assets.software` SuperOps assets: software read - `superops.assets.summary` SuperOps assets: summary read - `superops.assets.update` SuperOps assets: update write - `superops.assets.user_log` SuperOps assets: user log read - `superops.business_functions.list` List SuperOps business functions read - `superops.client_contracts.create` SuperOps client contracts: create write - `superops.client_contracts.get` Get SuperOps client contracts read - `superops.client_contracts.list` List SuperOps client contracts read - `superops.client_contracts.update` SuperOps client contracts: update write - `superops.client_custom_fields.create` SuperOps client custom fields: create write - `superops.client_custom_fields.get` Get SuperOps client custom fields read - `superops.client_custom_fields.list` List SuperOps client custom fields read - `superops.client_sites.create` SuperOps client sites: create write - `superops.client_sites.delete` SuperOps client sites: delete destructive - `superops.client_sites.get` Get SuperOps client sites read - `superops.client_sites.list` List SuperOps client sites read - `superops.client_sites.update` SuperOps client sites: update write - `superops.client_stages.list` List SuperOps client stages read - `superops.client_user_associations.create` SuperOps client user associations: create write - `superops.client_user_associations.delete` SuperOps client user associations: delete destructive - `superops.client_user_associations.list` List SuperOps client user associations read - `superops.client_user_associations.update` SuperOps client user associations: update write - `superops.client_users.create` SuperOps client users: create write - `superops.client_users.delete` SuperOps client users: delete destructive - `superops.client_users.get` Get SuperOps client users read - `superops.client_users.list` List SuperOps client users read - `superops.client_users.update` SuperOps client users: update write - `superops.clients.create` SuperOps clients: create write - `superops.clients.create_v1` SuperOps clients: create v1 write - `superops.clients.delete` SuperOps clients: delete destructive - `superops.clients.get` Get SuperOps clients read - `superops.clients.list` List SuperOps clients read - `superops.clients.restore` SuperOps clients: restore write - `superops.clients.trash` SuperOps clients: trash destructive - `superops.clients.update` SuperOps clients: update write - `superops.designations.list` List SuperOps designations read - `superops.device_categories.list` List SuperOps device categories read - `superops.fields.create` SuperOps fields: create write - `superops.fields.delete` SuperOps fields: delete destructive - `superops.fields.get` Get SuperOps fields read - `superops.fields.get_many` SuperOps fields: get many read - `superops.fields.list_for_module` SuperOps fields: list for module read - `superops.fields.update` SuperOps fields: update write - `superops.holiday_lists.list` List SuperOps holiday lists read - `superops.impacts.list` List SuperOps impacts read - `superops.invoice_items.list` List SuperOps invoice items read - `superops.invoices.create` SuperOps invoices: create write - `superops.invoices.get` Get SuperOps invoices read - `superops.invoices.list` List SuperOps invoices read - `superops.invoices.update` SuperOps invoices: update write - `superops.it_document_categories.list` List SuperOps it document categories read - `superops.it_documents.create` SuperOps it documents: create write - `superops.it_documents.delete` SuperOps it documents: delete destructive - `superops.it_documents.get` Get SuperOps it documents read - `superops.it_documents.list` List SuperOps it documents read - `superops.it_documents.update` SuperOps it documents: update write - `superops.kb_articles.create` SuperOps kb articles: create write - `superops.kb_articles.delete` SuperOps kb articles: delete destructive - `superops.kb_articles.update` SuperOps kb articles: update write - `superops.kb_collections.create` SuperOps kb collections: create write - `superops.kb_collections.delete` SuperOps kb collections: delete destructive - `superops.kb_collections.update` SuperOps kb collections: update write - `superops.kb_items.get` Get SuperOps kb items read - `superops.kb_items.list` List SuperOps kb items read - `superops.notes.create` SuperOps notes: create write - `superops.notes.update` SuperOps notes: update write - `superops.offered_items.list` List SuperOps offered items read - `superops.payment_methods.list` List SuperOps payment methods read - `superops.payment_terms.list` List SuperOps payment terms read - `superops.priorities.list` List SuperOps priorities read - `superops.requester_roles.list` List SuperOps requester roles read - `superops.resolution_codes.list` List SuperOps resolution codes read - `superops.scripts.list` List SuperOps scripts read - `superops.scripts.list_by_type` SuperOps scripts: list by type read - `superops.service_catalog_items.create` SuperOps service catalog items: create write - `superops.service_catalog_items.get` Get SuperOps service catalog items read - `superops.service_catalog_items.list` List SuperOps service catalog items read - `superops.service_catalog_items.update` SuperOps service catalog items: update write - `superops.service_categories.create` SuperOps service categories: create write - `superops.service_categories.list` List SuperOps service categories read - `superops.service_items.create` SuperOps service items: create write - `superops.service_items.get` Get SuperOps service items read - `superops.service_items.list` List SuperOps service items read - `superops.slas.list` List SuperOps slas read - `superops.tasks.create` SuperOps tasks: create write - `superops.tasks.get` Get SuperOps tasks read - `superops.tasks.list` List SuperOps tasks read - `superops.taxes.create` SuperOps taxes: create write - `superops.taxes.get` Get SuperOps taxes read - `superops.taxes.list` List SuperOps taxes read - `superops.teams.list` List SuperOps teams read - `superops.technician_groups.list` List SuperOps technician groups read - `superops.technician_roles.list` List SuperOps technician roles read - `superops.technicians.create` SuperOps technicians: create write - `superops.technicians.delete` SuperOps technicians: delete destructive - `superops.technicians.list` List SuperOps technicians read - `superops.technicians.update` SuperOps technicians: update write - `superops.ticket_categories.create` SuperOps ticket categories: create write - `superops.ticket_categories.list` List SuperOps ticket categories read - `superops.ticket_causes.create` SuperOps ticket causes: create write - `superops.ticket_causes.list` List SuperOps ticket causes read - `superops.ticket_conversations.create` SuperOps ticket conversations: create write - `superops.ticket_conversations.list` List SuperOps ticket conversations read - `superops.ticket_custom_fields.create` SuperOps ticket custom fields: create write - `superops.ticket_custom_fields.get` Get SuperOps ticket custom fields read - `superops.ticket_custom_fields.list` List SuperOps ticket custom fields read - `superops.ticket_notes.create` SuperOps ticket notes: create write - `superops.ticket_notes.list` List SuperOps ticket notes read - `superops.ticket_statuses.create` SuperOps ticket statuses: create write - `superops.ticket_statuses.list` List SuperOps ticket statuses read - `superops.tickets.create` SuperOps tickets: create write - `superops.tickets.delete` SuperOps tickets: delete destructive - `superops.tickets.get` Get SuperOps tickets read - `superops.tickets.list` List SuperOps tickets read - `superops.tickets.restore` SuperOps tickets: restore write - `superops.tickets.trash` SuperOps tickets: trash destructive - `superops.tickets.update` SuperOps tickets: update write - `superops.unmonitored_assets.create` SuperOps unmonitored assets: create write - `superops.unmonitored_assets.get` Get SuperOps unmonitored assets read - `superops.unmonitored_assets.list` List SuperOps unmonitored assets read - `superops.unmonitored_assets.update` SuperOps unmonitored assets: update write - `superops.urgencies.list` List SuperOps urgencies read - `superops.work_statuses.list` List SuperOps work statuses read - `superops.worklog_entries.create` SuperOps worklog entries: create write - `superops.worklog_entries.delete` SuperOps worklog entries: delete destructive - `superops.worklog_entries.list` List SuperOps worklog entries read - `superops.worklog_entries.update` SuperOps worklog entries: update write Questions ## The SuperOps RMM+PSA MCP server, answered. **Is there a SuperOps RMM+PSA MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 143 SuperOps RMM+PSA actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by SuperOps RMM+PSA. **What do I need to connect SuperOps RMM+PSA?** SuperOps API token and your SuperOps subdomain (the `acme` in acme.superops.ai). Plus your host. The free call account { op: "connections.requirements", service: "superops" } lists exactly what to paste. **Can an AI agent delete or change things in SuperOps RMM+PSA?** Only if its key allows it, and only with an explicit confirmation. 15 SuperOps RMM+PSA actions are destructive, including superOps client users: delete, superOps clients: delete and superOps client sites: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my SuperOps RMM+PSA API limit?** actionlake paces every call to the limits in the SuperOps RMM+PSA service file: 800 calls a minute per connection. Repeated reads are answered from cache (78 SuperOps RMM+PSA actions can be), which never reaches SuperOps RMM+PSA. **What does a SuperOps RMM+PSA action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (26 SuperOps RMM+PSA actions page). Cache hits, searches, dry runs and calls SuperOps RMM+PSA refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which SuperOps RMM+PSA API does it cover?** The SuperOps API msp at your SuperOps RMM+PSA instance's API base URL, which you enter when connecting. It is built from SuperOps RMM+PSA's documentation as read on 23 October 2026. 143 actions in 1 area, each one in the signed service file (version 1.0.0). **Can I combine SuperOps RMM+PSA with my other systems?** Yes. ask joins SuperOps RMM+PSA to HubSpot CRM or ServiceNow on the same customer and returns the answer rather than every row. SuperOps RMM+PSA maps crm.company, which 227 other connectors also map. **Does actionlake keep my SuperOps RMM+PSA data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your SuperOps RMM+PSA credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like SuperOps RMM+PSA Shares the most action names with - [Gorelo 32](https://actionlake.com/connectors/gorelo) - [Accelo 28](https://actionlake.com/connectors/accelo) - [Autotask 21](https://actionlake.com/connectors/autotask) - [Rev.io 20](https://actionlake.com/connectors/rev-io) - [TP-Link Omada Open API 14](https://actionlake.com/connectors/tp-link-omada-open-api) - [Veeam Service Provider Console 14](https://actionlake.com/connectors/veeam-service-provider-console) Joins with, on shared entities - [ServiceTitan 9](https://actionlake.com/connectors/servicetitan) - [ServiceNow 7](https://actionlake.com/connectors/servicenow) - [ERPNext (Frappe) 7](https://actionlake.com/connectors/erpnext-frappe) - [Microsoft Dynamics 365 7](https://actionlake.com/connectors/microsoft-dynamics-365) - [Zuper 7](https://actionlake.com/connectors/zuper) - [Odoo 6](https://actionlake.com/connectors/odoo) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by SuperOps RMM+PSA; the name is the vendor's own. Counts are from the SuperOps RMM+PSA service file, version 1.0.0. ## Give your agent SuperOps RMM+PSA today. [Connect SuperOps RMM+PSA free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/superops-rmm-psa More: https://actionlake.com/llms.txt