Connectors · MSP & PSA

ConnectWise ScreenConnect MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to ConnectWise ScreenConnect and the rest of your systems. It gives your agent 12 ConnectWise ScreenConnect actions (5 reads, 5 writes and 2 that wait for a confirmation) and holds the ConnectWise ScreenConnect credential itself, so the agent never does. It paces ConnectWise ScreenConnect's limits and records every call.

Connect ConnectWise ScreenConnect free See 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

12actionsin one signed file
5readlook, never change
5writecreate and update
2wait for a yesdestructive, confirmed first

Set up

Connect ConnectWise ScreenConnect 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 ConnectWise ScreenConnect.
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.
- auth_secretRESTfulAuthenticationSecret — the random string set in the RESTful API Manager extension's settings (sent as…
- hostWhere your ConnectWise ScreenConnect lives: your host
```
account { op: "connections.requirements", service: "screenconnect" }
# free: exactly what to paste, and what is found for you
```

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: "screenconnect.sessions.get" }# get a session · read · 1 upstream callcheck { action: "screenconnect.sessions.send_message", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

ConnectWise ScreenConnect 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: auth_secret
Setup fields: host
Limits we pace to: 120 calls a minute, per connection
API covered: RESTful API Manager 1.0.8, at your ConnectWise ScreenConnect instance's API base URL, which you enter when connecting
Built from: ConnectWise ScreenConnect's documentation, read 6 October 2026docs.connectwise.com docs.connectwise.com docs.connectwise.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 5 of 5 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 1, so ask can line ConnectWise ScreenConnect up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in ConnectWise ScreenConnect.

12 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

5readlook, never change
5writecreate and update
2destructivewait for a confirmation

Sessions
12
5 read · 5 write · 2 destructive
Query sessions with a filter expression · Send a chat message to a session · Find sessions by one property · Get a session

Top actions

The ConnectWise ScreenConnect API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 2 of ConnectWise ScreenConnect's 4 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`screenconnect.sessions.filter`Query sessions with a filter expression	List every session matching a session-group filter expression, e.g. CustomProperty1 = 'Acme' AND GuestOperatingSystemName LIKE 'Server'.	read	this connector
`screenconnect.sessions.send_message`Send a chat message to a session	Post a chat message into a session; the guest sees it in the client's chat.	write	`comm.message.send`25 connectors
`screenconnect.sessions.search`Find sessions by one property	List sessions where one property (a custom property such as company, the machine name, the logged-on user, the OS) equals or is LIKE a value. Builds the…	read	this connector
`screenconnect.sessions.create`Create a session	Create a Support, Meeting or Access session, optionally public or protected by a join code, with its custom property values. Returns the created session.	write	this connector
`screenconnect.session_notes.create`Add a note to a session	Add a note to a session's history (shown on its Notes tab). Needs extension version 1.0.6 or later.	write	this connector
`screenconnect.sessions.send_command`Run a command on a session's machine	Queue a shell command (cmd by default; prefix #!ps for PowerShell, #!sh for shell) to run on the guest machine as SYSTEM/root. Irreversible: it executes on…	destructive	this connector

Try it

Prompts to paste into Claude.

Each one names the ConnectWise ScreenConnect actions it will call, so you know what it reads and what it changes before you send it.

Readread
Which ConnectWise ScreenConnect devices have not checked in for a week?
callsscreenconnect.sessions.filter
Writewrite
Send a chat message to a session in ConnectWise ScreenConnect. Show me exactly what you will send before you save it.
callsscreenconnect.sessions.send_message

Governance for ConnectWise ScreenConnect

Destructive actions wait for a yes.

2 ConnectWise ScreenConnect actions are destructive. These are all of them:

Run a command on a session's machinescreenconnect.sessions.send_command
Run a toolbox item on a session's machinescreenconnect.sessions.send_toolbox_item

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.

doscreenconnect.sessions.send_commandconfirm_policy: human

Run a command on a session's machine?

intent: the user asked me to run a command on a session's machine

run suspended · waiting for a named person · key screenconnect-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "screenconnect-agent",  allowed_actions: ["screenconnect.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "screenconnect.sessions.send_command", approver: "[email protected]" },    { match: "screenconnect.sessions.send_toolbox_item", approver: "[email protected]" }  ]}

Illustrative. Scoped to ConnectWise ScreenConnect only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What ConnectWise ScreenConnect costs on actionlake.

Every ConnectWise ScreenConnect action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call ConnectWise ScreenConnect 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 12 ConnectWise ScreenConnect actions
12actions pageeach page of a long list is one call
5reads 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 ConnectWise ScreenConnect action.

12 actions by area: the id your agent calls, what it does, and its effect.

Sessions12

screenconnect.session_notes.createAdd a note to a sessionwrite
screenconnect.sessions.createCreate a sessionwrite
screenconnect.sessions.filterQuery sessions with a filter expressionread
screenconnect.sessions.find_by_nameList sessions with a nameread
screenconnect.sessions.getGet a sessionread
screenconnect.sessions.get_detailsGet a session's detailsread
screenconnect.sessions.searchFind sessions by one propertyread
screenconnect.sessions.send_commandRun a command on a session's machinedestructive
screenconnect.sessions.send_messageSend a chat message to a sessionwrite
screenconnect.sessions.send_toolbox_itemRun a toolbox item on a session's machinedestructive
screenconnect.sessions.update_custom_propertiesSet a session's custom propertieswrite
screenconnect.sessions.update_nameRename a sessionwrite

Questions

The ConnectWise ScreenConnect MCP server, answered.

Is there a ConnectWise ScreenConnect MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 12 ConnectWise ScreenConnect actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by ConnectWise ScreenConnect.

What do I need to connect ConnectWise ScreenConnect?

RESTfulAuthenticationSecret — the random string set in the RESTful API Manager extension's settings (sent as…. Plus your host. The free call account { op: "connections.requirements", service: "screenconnect" } lists exactly what to paste.

Can an AI agent delete or change things in ConnectWise ScreenConnect?

Only if its key allows it, and only with an explicit confirmation. 2 ConnectWise ScreenConnect actions are destructive, including run a command on a session's machine and run a toolbox item on a session's machine. 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 ConnectWise ScreenConnect API limit?

actionlake paces every call to the limits in the ConnectWise ScreenConnect service file: 120 calls a minute per connection. Repeated reads are answered from cache (5 ConnectWise ScreenConnect actions can be), which never reaches ConnectWise ScreenConnect.

What does a ConnectWise ScreenConnect action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (12 ConnectWise ScreenConnect actions page). Cache hits, searches, dry runs and calls ConnectWise ScreenConnect 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 ConnectWise ScreenConnect API does it cover?

The RESTful API Manager 1.0.8 at your ConnectWise ScreenConnect instance's API base URL, which you enter when connecting. It is built from ConnectWise ScreenConnect's documentation as read on 6 October 2026. 12 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my ConnectWise ScreenConnect data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, 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 ConnectWise ScreenConnect 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 ConnectWise ScreenConnect today.