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.
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/mcpdo { action: "superops.client_users.list", intent: "check which SuperOps RMM+PSA account is connected"}# List SuperOps client users · read · 1 upstream call- 143actionsin one signed file
- 78readlook, never change
- 50writecreate and update
- 15wait for a yesdestructive, confirmed first
Set up
Connect SuperOps RMM+PSA in three steps.
- 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 - 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_tokenSuperOps API tokencustomer_subdomainYour SuperOps subdomain (the `acme` in acme.superops.ai)hostWhere your SuperOps RMM+PSA lives: your host
account { op: "connections.requirements", service: "superops" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "superops.client_users.list" }# list superops client users · read · 1 upstream callcheck { 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_tokencustomer_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 2026developer.superops.com
- 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.
- 78readlook, never change
- 50writecreate and update
- 15destructivewait for a confirmation
PSA RMM
14378 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.listList SuperOps client users | Fetches a list of client users | read | crm.contact.list177 connectors |
superops.clients.listList SuperOps clients | Fetches a list of clients | read | crm.company.list162 connectors |
superops.client_sites.listList SuperOps client sites | Fetches a list of client sites | read | crm.location.list48 connectors |
superops.technicians.listList SuperOps technicians | Fetches the list of technicians | read | identity.user.list474 connectors |
superops.client_users.createSuperOps client users: create | Creates a new client user | write | crm.contact.create161 connectors |
superops.clients.createSuperOps clients: create | Creates a client | write | crm.company.create142 connectors |
superops.tickets.listList SuperOps tickets | Fetches a list of tickets | read | service.ticket.list56 connectors |
superops.tasks.listList SuperOps tasks | Fetches a list of tasks | read | work.task.list122 connectors |
superops.client_sites.createSuperOps client sites: create | Creates a client site | write | crm.location.create41 connectors |
superops.invoices.listList SuperOps invoices | Fetches a list of invoices | read | finance.invoice.list101 connectors |
superops.client_users.deleteSuperOps client users: delete | Deletes the records of an existing client user | destructive | crm.contact.delete147 connectors |
superops.client_contracts.listList SuperOps client contracts | Fetches a list of client contracts | read | service.contract.list23 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.
- Readread
Which SuperOps RMM+PSA invoices are more than 30 days overdue? Group them by customer with the total owed.
calls
superops.invoices.list - Writewrite
SuperOps client users: create in SuperOps RMM+PSA. Show me exactly what you will send before you save it.
calls
superops.client_users.create - Across systemsread
For each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in HubSpot CRM?
calls
superops.invoices.listhubspot_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, oncrm.company· HubSpot CRMFor each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in ServiceNow?
superops.invoices.list+servicenow_table.incidents.list, oncrm.company· ServiceNow
identity.user 517crm.company 227crm.contact 192work.task 105finance.invoice 91service.ticket 62crm.location 49asset.asset 40ask { 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"] } } ]}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.
SuperOps client users: delete?
intent: the user asked me to superOps client users: delete
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: "[email protected]" }, { match: "superops.clients.delete", approver: "[email protected]" }, { match: "superops.client_sites.delete", approver: "[email protected]" } ]}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.
- 1upstream call per actionall 143 SuperOps RMM+PSA actions
- 26actions pageeach page of a long list is one call
- 78reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every SuperOps RMM+PSA action.
143 actions by area: the id your agent calls, what it does, and its effect.
PSA RMM143
superops.alerts.createSuperOps alerts: createwritesuperops.alerts.listList SuperOps alertsreadsuperops.alerts.list_for_assetSuperOps alerts: list for assetreadsuperops.alerts.resolveSuperOps alerts: resolvewritesuperops.asset_class_custom_fields.listList SuperOps asset class custom fieldsreadsuperops.asset_custom_fields.listList SuperOps asset custom fieldsreadsuperops.assets.activitySuperOps assets: activityreadsuperops.assets.assign_device_categorySuperOps assets: assign device categorywritesuperops.assets.by_third_party_endpointsSuperOps assets: by third party endpointsreadsuperops.assets.deleteSuperOps assets: deletedestructivesuperops.assets.disksSuperOps assets: disksreadsuperops.assets.getGet SuperOps assetsreadsuperops.assets.listList SuperOps assetsreadsuperops.assets.patch_statusSuperOps assets: patch statusreadsuperops.assets.patchesSuperOps assets: patchesreadsuperops.assets.run_scriptSuperOps assets: run scriptdestructivesuperops.assets.softwareSuperOps assets: softwarereadsuperops.assets.summarySuperOps assets: summaryreadsuperops.assets.updateSuperOps assets: updatewritesuperops.assets.user_logSuperOps assets: user logreadsuperops.business_functions.listList SuperOps business functionsreadsuperops.client_contracts.createSuperOps client contracts: createwritesuperops.client_contracts.getGet SuperOps client contractsreadsuperops.client_contracts.listList SuperOps client contractsreadsuperops.client_contracts.updateSuperOps client contracts: updatewritesuperops.client_custom_fields.createSuperOps client custom fields: createwritesuperops.client_custom_fields.getGet SuperOps client custom fieldsreadsuperops.client_custom_fields.listList SuperOps client custom fieldsreadsuperops.client_sites.createSuperOps client sites: createwritesuperops.client_sites.deleteSuperOps client sites: deletedestructivesuperops.client_sites.getGet SuperOps client sitesreadsuperops.client_sites.listList SuperOps client sitesreadsuperops.client_sites.updateSuperOps client sites: updatewritesuperops.client_stages.listList SuperOps client stagesreadsuperops.client_user_associations.createSuperOps client user associations: createwritesuperops.client_user_associations.deleteSuperOps client user associations: deletedestructivesuperops.client_user_associations.listList SuperOps client user associationsreadsuperops.client_user_associations.updateSuperOps client user associations: updatewritesuperops.client_users.createSuperOps client users: createwritesuperops.client_users.deleteSuperOps client users: deletedestructivesuperops.client_users.getGet SuperOps client usersreadsuperops.client_users.listList SuperOps client usersreadsuperops.client_users.updateSuperOps client users: updatewritesuperops.clients.createSuperOps clients: createwritesuperops.clients.create_v1SuperOps clients: create v1writesuperops.clients.deleteSuperOps clients: deletedestructivesuperops.clients.getGet SuperOps clientsreadsuperops.clients.listList SuperOps clientsreadsuperops.clients.restoreSuperOps clients: restorewritesuperops.clients.trashSuperOps clients: trashdestructivesuperops.clients.updateSuperOps clients: updatewritesuperops.designations.listList SuperOps designationsreadsuperops.device_categories.listList SuperOps device categoriesreadsuperops.fields.createSuperOps fields: createwritesuperops.fields.deleteSuperOps fields: deletedestructivesuperops.fields.getGet SuperOps fieldsreadsuperops.fields.get_manySuperOps fields: get manyreadsuperops.fields.list_for_moduleSuperOps fields: list for modulereadsuperops.fields.updateSuperOps fields: updatewritesuperops.holiday_lists.listList SuperOps holiday listsreadsuperops.impacts.listList SuperOps impactsreadsuperops.invoice_items.listList SuperOps invoice itemsreadsuperops.invoices.createSuperOps invoices: createwritesuperops.invoices.getGet SuperOps invoicesreadsuperops.invoices.listList SuperOps invoicesreadsuperops.invoices.updateSuperOps invoices: updatewritesuperops.it_document_categories.listList SuperOps it document categoriesreadsuperops.it_documents.createSuperOps it documents: createwritesuperops.it_documents.deleteSuperOps it documents: deletedestructivesuperops.it_documents.getGet SuperOps it documentsreadsuperops.it_documents.listList SuperOps it documentsreadsuperops.it_documents.updateSuperOps it documents: updatewritesuperops.kb_articles.createSuperOps kb articles: createwritesuperops.kb_articles.deleteSuperOps kb articles: deletedestructivesuperops.kb_articles.updateSuperOps kb articles: updatewritesuperops.kb_collections.createSuperOps kb collections: createwritesuperops.kb_collections.deleteSuperOps kb collections: deletedestructivesuperops.kb_collections.updateSuperOps kb collections: updatewritesuperops.kb_items.getGet SuperOps kb itemsreadsuperops.kb_items.listList SuperOps kb itemsreadsuperops.notes.createSuperOps notes: createwritesuperops.notes.updateSuperOps notes: updatewritesuperops.offered_items.listList SuperOps offered itemsreadsuperops.payment_methods.listList SuperOps payment methodsreadsuperops.payment_terms.listList SuperOps payment termsreadsuperops.priorities.listList SuperOps prioritiesreadsuperops.requester_roles.listList SuperOps requester rolesreadsuperops.resolution_codes.listList SuperOps resolution codesreadsuperops.scripts.listList SuperOps scriptsreadsuperops.scripts.list_by_typeSuperOps scripts: list by typereadsuperops.service_catalog_items.createSuperOps service catalog items: createwritesuperops.service_catalog_items.getGet SuperOps service catalog itemsreadsuperops.service_catalog_items.listList SuperOps service catalog itemsreadsuperops.service_catalog_items.updateSuperOps service catalog items: updatewritesuperops.service_categories.createSuperOps service categories: createwritesuperops.service_categories.listList SuperOps service categoriesreadsuperops.service_items.createSuperOps service items: createwritesuperops.service_items.getGet SuperOps service itemsreadsuperops.service_items.listList SuperOps service itemsreadsuperops.slas.listList SuperOps slasreadsuperops.tasks.createSuperOps tasks: createwritesuperops.tasks.getGet SuperOps tasksreadsuperops.tasks.listList SuperOps tasksreadsuperops.taxes.createSuperOps taxes: createwritesuperops.taxes.getGet SuperOps taxesreadsuperops.taxes.listList SuperOps taxesreadsuperops.teams.listList SuperOps teamsreadsuperops.technician_groups.listList SuperOps technician groupsreadsuperops.technician_roles.listList SuperOps technician rolesreadsuperops.technicians.createSuperOps technicians: createwritesuperops.technicians.deleteSuperOps technicians: deletedestructivesuperops.technicians.listList SuperOps techniciansreadsuperops.technicians.updateSuperOps technicians: updatewritesuperops.ticket_categories.createSuperOps ticket categories: createwritesuperops.ticket_categories.listList SuperOps ticket categoriesreadsuperops.ticket_causes.createSuperOps ticket causes: createwritesuperops.ticket_causes.listList SuperOps ticket causesreadsuperops.ticket_conversations.createSuperOps ticket conversations: createwritesuperops.ticket_conversations.listList SuperOps ticket conversationsreadsuperops.ticket_custom_fields.createSuperOps ticket custom fields: createwritesuperops.ticket_custom_fields.getGet SuperOps ticket custom fieldsreadsuperops.ticket_custom_fields.listList SuperOps ticket custom fieldsreadsuperops.ticket_notes.createSuperOps ticket notes: createwritesuperops.ticket_notes.listList SuperOps ticket notesreadsuperops.ticket_statuses.createSuperOps ticket statuses: createwritesuperops.ticket_statuses.listList SuperOps ticket statusesreadsuperops.tickets.createSuperOps tickets: createwritesuperops.tickets.deleteSuperOps tickets: deletedestructivesuperops.tickets.getGet SuperOps ticketsreadsuperops.tickets.listList SuperOps ticketsreadsuperops.tickets.restoreSuperOps tickets: restorewritesuperops.tickets.trashSuperOps tickets: trashdestructivesuperops.tickets.updateSuperOps tickets: updatewritesuperops.unmonitored_assets.createSuperOps unmonitored assets: createwritesuperops.unmonitored_assets.getGet SuperOps unmonitored assetsreadsuperops.unmonitored_assets.listList SuperOps unmonitored assetsreadsuperops.unmonitored_assets.updateSuperOps unmonitored assets: updatewritesuperops.urgencies.listList SuperOps urgenciesreadsuperops.work_statuses.listList SuperOps work statusesreadsuperops.worklog_entries.createSuperOps worklog entries: createwritesuperops.worklog_entries.deleteSuperOps worklog entries: deletedestructivesuperops.worklog_entries.listList SuperOps worklog entriesreadsuperops.worklog_entries.updateSuperOps worklog entries: updatewrite
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.
Give your agent SuperOps RMM+PSA today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.