Skip to content

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/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
  • 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.

  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_tokenSuperOps API token
    • customer_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
  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 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
  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.

ActionWhat it doesEffectSame name in
superops.client_users.listList SuperOps client usersFetches a list of client usersreadcrm.contact.list177 connectors
superops.clients.listList SuperOps clientsFetches a list of clientsreadcrm.company.list162 connectors
superops.client_sites.listList SuperOps client sitesFetches a list of client sitesreadcrm.location.list48 connectors
superops.technicians.listList SuperOps techniciansFetches the list of techniciansreadidentity.user.list474 connectors
superops.client_users.createSuperOps client users: createCreates a new client userwritecrm.contact.create161 connectors
superops.clients.createSuperOps clients: createCreates a clientwritecrm.company.create142 connectors
superops.tickets.listList SuperOps ticketsFetches a list of ticketsreadservice.ticket.list56 connectors
superops.tasks.listList SuperOps tasksFetches a list of tasksreadwork.task.list122 connectors
superops.client_sites.createSuperOps client sites: createCreates a client sitewritecrm.location.create41 connectors
superops.invoices.listList SuperOps invoicesFetches a list of invoicesreadfinance.invoice.list101 connectors
superops.client_users.deleteSuperOps client users: deleteDeletes the records of an existing client userdestructivecrm.contact.delete147 connectors
superops.client_contracts.listList SuperOps client contractsFetches a list of client contractsreadservice.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.

  1. Readread

    Which SuperOps RMM+PSA invoices are more than 30 days overdue? Group them by customer with the total owed.

    callssuperops.invoices.list

  2. Writewrite

    SuperOps client users: create in SuperOps RMM+PSA. Show me exactly what you will send before you save it.

    callssuperops.client_users.create

  3. Across systemsread

    For each customer, how many invoices are in SuperOps RMM+PSA and how many tickets in HubSpot CRM?

    callssuperops.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, on crm.company · 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

Also mapped by other connectorsidentity.user 517crm.company 227crm.contact 192work.task 105finance.invoice 91service.ticket 62crm.location 49asset.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: deletesuperops.client_users.delete
  • SuperOps clients: deletesuperops.clients.delete
  • SuperOps client sites: deletesuperops.client_sites.delete
  • SuperOps technicians: deletesuperops.technicians.delete
  • SuperOps tickets: deletesuperops.tickets.delete
  • SuperOps assets: deletesuperops.assets.delete
  • SuperOps worklog entries: deletesuperops.worklog_entries.delete
  • SuperOps clients: trashsuperops.clients.trash
  • SuperOps fields: deletesuperops.fields.delete
  • SuperOps tickets: trashsuperops.tickets.trash
  • SuperOps assets: run scriptsuperops.assets.run_script
  • SuperOps kb articles: deletesuperops.kb_articles.delete
  • SuperOps it documents: deletesuperops.it_documents.delete
  • SuperOps kb collections: deletesuperops.kb_collections.delete
  • SuperOps client user associations: deletesuperops.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.

dosuperops.client_users.deleteconfirm_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: "[email protected]" },    { match: "superops.clients.delete", approver: "[email protected]" },    { match: "superops.client_sites.delete", approver: "[email protected]" }  ]}
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.

  • 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

See pricing

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: createwrite
  • superops.alerts.listList SuperOps alertsread
  • superops.alerts.list_for_assetSuperOps alerts: list for assetread
  • superops.alerts.resolveSuperOps alerts: resolvewrite
  • superops.asset_class_custom_fields.listList SuperOps asset class custom fieldsread
  • superops.asset_custom_fields.listList SuperOps asset custom fieldsread
  • superops.assets.activitySuperOps assets: activityread
  • superops.assets.assign_device_categorySuperOps assets: assign device categorywrite
  • superops.assets.by_third_party_endpointsSuperOps assets: by third party endpointsread
  • superops.assets.deleteSuperOps assets: deletedestructive
  • superops.assets.disksSuperOps assets: disksread
  • superops.assets.getGet SuperOps assetsread
  • superops.assets.listList SuperOps assetsread
  • superops.assets.patch_statusSuperOps assets: patch statusread
  • superops.assets.patchesSuperOps assets: patchesread
  • superops.assets.run_scriptSuperOps assets: run scriptdestructive
  • superops.assets.softwareSuperOps assets: softwareread
  • superops.assets.summarySuperOps assets: summaryread
  • superops.assets.updateSuperOps assets: updatewrite
  • superops.assets.user_logSuperOps assets: user logread
  • superops.business_functions.listList SuperOps business functionsread
  • superops.client_contracts.createSuperOps client contracts: createwrite
  • superops.client_contracts.getGet SuperOps client contractsread
  • superops.client_contracts.listList SuperOps client contractsread
  • superops.client_contracts.updateSuperOps client contracts: updatewrite
  • superops.client_custom_fields.createSuperOps client custom fields: createwrite
  • superops.client_custom_fields.getGet SuperOps client custom fieldsread
  • superops.client_custom_fields.listList SuperOps client custom fieldsread
  • superops.client_sites.createSuperOps client sites: createwrite
  • superops.client_sites.deleteSuperOps client sites: deletedestructive
  • superops.client_sites.getGet SuperOps client sitesread
  • superops.client_sites.listList SuperOps client sitesread
  • superops.client_sites.updateSuperOps client sites: updatewrite
  • superops.client_stages.listList SuperOps client stagesread
  • superops.client_user_associations.createSuperOps client user associations: createwrite
  • superops.client_user_associations.deleteSuperOps client user associations: deletedestructive
  • superops.client_user_associations.listList SuperOps client user associationsread
  • superops.client_user_associations.updateSuperOps client user associations: updatewrite
  • superops.client_users.createSuperOps client users: createwrite
  • superops.client_users.deleteSuperOps client users: deletedestructive
  • superops.client_users.getGet SuperOps client usersread
  • superops.client_users.listList SuperOps client usersread
  • superops.client_users.updateSuperOps client users: updatewrite
  • superops.clients.createSuperOps clients: createwrite
  • superops.clients.create_v1SuperOps clients: create v1write
  • superops.clients.deleteSuperOps clients: deletedestructive
  • superops.clients.getGet SuperOps clientsread
  • superops.clients.listList SuperOps clientsread
  • superops.clients.restoreSuperOps clients: restorewrite
  • superops.clients.trashSuperOps clients: trashdestructive
  • superops.clients.updateSuperOps clients: updatewrite
  • superops.designations.listList SuperOps designationsread
  • superops.device_categories.listList SuperOps device categoriesread
  • superops.fields.createSuperOps fields: createwrite
  • superops.fields.deleteSuperOps fields: deletedestructive
  • superops.fields.getGet SuperOps fieldsread
  • superops.fields.get_manySuperOps fields: get manyread
  • superops.fields.list_for_moduleSuperOps fields: list for moduleread
  • superops.fields.updateSuperOps fields: updatewrite
  • superops.holiday_lists.listList SuperOps holiday listsread
  • superops.impacts.listList SuperOps impactsread
  • superops.invoice_items.listList SuperOps invoice itemsread
  • superops.invoices.createSuperOps invoices: createwrite
  • superops.invoices.getGet SuperOps invoicesread
  • superops.invoices.listList SuperOps invoicesread
  • superops.invoices.updateSuperOps invoices: updatewrite
  • superops.it_document_categories.listList SuperOps it document categoriesread
  • superops.it_documents.createSuperOps it documents: createwrite
  • superops.it_documents.deleteSuperOps it documents: deletedestructive
  • superops.it_documents.getGet SuperOps it documentsread
  • superops.it_documents.listList SuperOps it documentsread
  • superops.it_documents.updateSuperOps it documents: updatewrite
  • superops.kb_articles.createSuperOps kb articles: createwrite
  • superops.kb_articles.deleteSuperOps kb articles: deletedestructive
  • superops.kb_articles.updateSuperOps kb articles: updatewrite
  • superops.kb_collections.createSuperOps kb collections: createwrite
  • superops.kb_collections.deleteSuperOps kb collections: deletedestructive
  • superops.kb_collections.updateSuperOps kb collections: updatewrite
  • superops.kb_items.getGet SuperOps kb itemsread
  • superops.kb_items.listList SuperOps kb itemsread
  • superops.notes.createSuperOps notes: createwrite
  • superops.notes.updateSuperOps notes: updatewrite
  • superops.offered_items.listList SuperOps offered itemsread
  • superops.payment_methods.listList SuperOps payment methodsread
  • superops.payment_terms.listList SuperOps payment termsread
  • superops.priorities.listList SuperOps prioritiesread
  • superops.requester_roles.listList SuperOps requester rolesread
  • superops.resolution_codes.listList SuperOps resolution codesread
  • superops.scripts.listList SuperOps scriptsread
  • superops.scripts.list_by_typeSuperOps scripts: list by typeread
  • superops.service_catalog_items.createSuperOps service catalog items: createwrite
  • superops.service_catalog_items.getGet SuperOps service catalog itemsread
  • superops.service_catalog_items.listList SuperOps service catalog itemsread
  • superops.service_catalog_items.updateSuperOps service catalog items: updatewrite
  • superops.service_categories.createSuperOps service categories: createwrite
  • superops.service_categories.listList SuperOps service categoriesread
  • superops.service_items.createSuperOps service items: createwrite
  • superops.service_items.getGet SuperOps service itemsread
  • superops.service_items.listList SuperOps service itemsread
  • superops.slas.listList SuperOps slasread
  • superops.tasks.createSuperOps tasks: createwrite
  • superops.tasks.getGet SuperOps tasksread
  • superops.tasks.listList SuperOps tasksread
  • superops.taxes.createSuperOps taxes: createwrite
  • superops.taxes.getGet SuperOps taxesread
  • superops.taxes.listList SuperOps taxesread
  • superops.teams.listList SuperOps teamsread
  • superops.technician_groups.listList SuperOps technician groupsread
  • superops.technician_roles.listList SuperOps technician rolesread
  • superops.technicians.createSuperOps technicians: createwrite
  • superops.technicians.deleteSuperOps technicians: deletedestructive
  • superops.technicians.listList SuperOps techniciansread
  • superops.technicians.updateSuperOps technicians: updatewrite
  • superops.ticket_categories.createSuperOps ticket categories: createwrite
  • superops.ticket_categories.listList SuperOps ticket categoriesread
  • superops.ticket_causes.createSuperOps ticket causes: createwrite
  • superops.ticket_causes.listList SuperOps ticket causesread
  • superops.ticket_conversations.createSuperOps ticket conversations: createwrite
  • superops.ticket_conversations.listList SuperOps ticket conversationsread
  • superops.ticket_custom_fields.createSuperOps ticket custom fields: createwrite
  • superops.ticket_custom_fields.getGet SuperOps ticket custom fieldsread
  • superops.ticket_custom_fields.listList SuperOps ticket custom fieldsread
  • superops.ticket_notes.createSuperOps ticket notes: createwrite
  • superops.ticket_notes.listList SuperOps ticket notesread
  • superops.ticket_statuses.createSuperOps ticket statuses: createwrite
  • superops.ticket_statuses.listList SuperOps ticket statusesread
  • superops.tickets.createSuperOps tickets: createwrite
  • superops.tickets.deleteSuperOps tickets: deletedestructive
  • superops.tickets.getGet SuperOps ticketsread
  • superops.tickets.listList SuperOps ticketsread
  • superops.tickets.restoreSuperOps tickets: restorewrite
  • superops.tickets.trashSuperOps tickets: trashdestructive
  • superops.tickets.updateSuperOps tickets: updatewrite
  • superops.unmonitored_assets.createSuperOps unmonitored assets: createwrite
  • superops.unmonitored_assets.getGet SuperOps unmonitored assetsread
  • superops.unmonitored_assets.listList SuperOps unmonitored assetsread
  • superops.unmonitored_assets.updateSuperOps unmonitored assets: updatewrite
  • superops.urgencies.listList SuperOps urgenciesread
  • superops.work_statuses.listList SuperOps work statusesread
  • superops.worklog_entries.createSuperOps worklog entries: createwrite
  • superops.worklog_entries.deleteSuperOps worklog entries: deletedestructive
  • superops.worklog_entries.listList SuperOps worklog entriesread
  • superops.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.