--- title: "Peplink InControl 2 MCP server for AI agents - actionlake" description: "Give Claude 375 Peplink InControl 2 actions through one MCP server: group docker scripts. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/peplink-incontrol-2 updated: 2026-10-23 --- Connectors · MSP & PSA # Peplink InControl 2 MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Peplink InControl 2 and the rest of your systems. It gives your agent 375 Peplink InControl 2 actions (255 reads, 99 writes and 21 that wait for a confirmation) and holds the Peplink InControl 2 credential itself, so the agent never does. It paces Peplink InControl 2's limits and records every call. [Connect Peplink InControl 2 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: "peplink_incontrol2.organizations.list", intent: "check which Peplink InControl 2 account is connected" } # Get accessible organization list · read · 1 upstream call ``` - 375 actions in one signed file - 255 read look, never change - 99 write create and update - 21 wait for a yes destructive, confirmed first Set up ## Connect Peplink InControl 2 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 Peplink InControl 2. OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key. - `client_id` InControl 2 Client ID: in InControl click your email address (top right), scroll to Client Applications, New Client,… - `client_secret` Client Secret of the same InControl 2 client application ``` account { op: "connections.requirements", service: "peplink_incontrol2" } # 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: "peplink_incontrol2.organizations.list" } # get accessible organization list · read · 1 upstream call check { action: "peplink_incontrol2.groups.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Peplink InControl 2 at a glance **Sign-in** OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. **You provide** `client_id` `client_secret` **Limits we pace to** 20 calls a second, per connection **API covered** InControl 2 REST API (api.ic.peplink.com/rest)`api.ic.peplink.com` **Built from** Peplink InControl 2's documentation, read 23 October 2026[peplink.com](https://www.peplink.com/ic2-api-doc/) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 245 of 255 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 3, so ask can line Peplink InControl 2 up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Peplink InControl 2. 375 actions in 315 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **255** read look, never change - **99** write create and update - **21** destructive wait for a confirmation 1. ### Group docker scripts 4 1 read · 2 write · 1 destructive Create docker scripts · Get docker scripts · Update docker scripts · Get docker scripts 2. ### Group firewall rule sets 4 1 read · 2 write · 1 destructive Create firewall rule set · Get simple firewall rule settings · Update firewall rule set · Delete firewall rule settings 3. ### Group grouped mac 4 1 read · 2 write · 1 destructive Create Grouped MAC Addresses · Get Grouped MAC Addresses · Update Group MAC Address · Delete Group MAC Addresses 4. ### Group settings admins 4 1 read · 1 write · 2 destructive Get group admin users · Update group admin users · Add group admin users · Delete group admin users 5. ### Group sim pools 4 1 read · 2 write · 1 destructive Create SIM pool profiles · Get SIM pool profiles · Update SIM pool profiles · Delete SIM pool profiles 6. ### Group starlink pools 4 1 read · 2 write · 1 destructive Create Starlink pool profiles · Get Starlink pool profiles · Update SIM pool profiles · Delete Starlink pool profiles 7. ### Group vlan config 4 1 read · 2 write · 1 destructive Create a VLAN network settings · Get VLAN network settings in a group · Update a VLAN network settings · Delete a VLAN network settings 8. ### Settings admins 4 1 read · 1 write · 2 destructive Get organization admin users · Update organization admin users · Add organization admin users · Delete organization admin users **112 more areas · 343 actions** - Sim pools **4** - Starlink pools **4** - Group device tags **3** - Group ssid settings **3** - Delete devices **2** - Device client **2** - Device CP guest **2** - Device devapi **2** - Device loc **2** - Device oobm settings **2** - Device ssid profiles **2** - Device tags **2** - Esim pool devices **2** - Esim pool iccid **2** - Esim pool settings **2** - Group bulk config **2** - Group client **2** - Group CP guest **2** - Group CP guest by user id **2** - Group device ip settings **2** - Group docker scripts log **2** - Group grouped networks **2** - Group move devices **2** - Group SP default **2** - Group ssid profiles **2** - Group wifi management **2** - Grouped networks **2** - Groups **2** - Move devices **2** - SP default **2** - Ads survey **1** - Bandwidth per device **1** - Bandwidth per device CSV **1** - Device **1** - Device air monitor **1** - Device air monitor chutil **1** - Device air monitor dates **1** - Device air probe performance test **1** - Device air probe performance test list **1** - Device availability **1** - Device availability CSV **1** - Device bandwidth **1** - Device cellular tower scan profiles **1** - Device cellular tower scan result **1** - Device cellular tower scan results **1** - Device cellular tower scan results by report id **1** - Device cellular tower scan results dates **1** - Device cellular tower scan run **1** - Device client captive portal access logs **1** - Device client daily usages **1** - Device client daily vlan usages **1** - Device client hourly usages **1** - Device client hourly vlan usages **1** - Device client usage summary **1** - Device config backup **1** - Device config backup target convert **1** - Device conn test reports **1** - Device content blocking log **1** - Device content blocking log dates **1** - Device convert targets **1** - Device CP **1** - Device CP by CP id **1** - Device CP captive portal user **1** - Device CP client type **1** - Device CP guest session **1** - Device CP guest status **1** - Device CP import guest **1** - Device CP usage portal list **1** - Device CP usage report **1** - Device custom portals **1** - Device daily client count **1** - Device daily client list **1** - Device dpi daily **1** - Device dpi hourly **1** - Device event log **1** - Device event log archive list **1** - Device event log types **1** - Device external portal usages **1** - Device firewall log **1** - Device firewall log dates **1** - Device GPS availability **1** - Device hmi display **1** - Device hourly client count **1** - Device hourly client list **1** - Device info **1** - Device info by field **1** - Device iot port **1** - Device iot reports **1** - Device ipsec history **1** - Device ipsec history profile names **1** - Device mediafast usages **1** - Device name **1** - Device note **1** - Device online history **1** - Device oobm links **1** - Device oobm settings copy **1** - Device pepvpn connection availability monthly **1** - Device pepvpn status **1** - Device pepvpn status V2 **1** - Device pepvpn tunnel stat **1** - Device pepvpn tunnel stat V2 **1** - Device pepvpn usages **1** - Device pepvpn usages CSV **1** - Device poe usage daily **1** - Device poe usage daily CSV **1** - Device poe usage hourly **1** - Device poe usage hourly CSV **1** - Device poe usage monthly **1** - Device poe usage monthly CSV **1** - Device radio support **1** - Device reader log **1** - 196 smaller areas **196** Top actions ## The Peplink InControl 2 API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 6 of Peplink InControl 2's 6 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `peplink_incontrol2.groups.list` Get an organization's group list | Get an organization's group list. | read | `crm.location.list` 48 connectors | | `peplink_incontrol2.devices.list` Get an organization's device list. | Get an organization's device list. | read | `device.endpoint.list` 65 connectors | | `peplink_incontrol2.group.get` Get a group's information | Get a group's information. | read | `crm.location.get` 42 connectors | | `peplink_incontrol2.device.get` Get a device's details. | Get a device's details. | read | `device.endpoint.get` 57 connectors | | `peplink_incontrol2.user_me.get` Get your user information | Get your user information. | read | `identity.current_user.get` 307 connectors | | `peplink_incontrol2.organizations.list` Get accessible organization list | Get accessible organization list. | read | `platform.tenant.list` 70 connectors | | `peplink_incontrol2.groups.create` Create a group | Create a group. | write | this connector | | `peplink_incontrol2.group_devices.list` Get a group's device list. | Get a group's device list. | read | this connector | | `peplink_incontrol2.sn.get` Get a device's details | Get a device's details. | read | this connector | | `peplink_incontrol2.sim_pools.create` Create SIM pool profiles | Create SIM pool profiles. | write | this connector | | `peplink_incontrol2.esim_topup.create` Topup Devices | Topup Devices. | write | this connector | | `peplink_incontrol2.sim_pools.delete` Delete SIM pool profiles | Delete SIM pool profiles. | destructive | this connector | Try it ## Prompts to paste into Claude. Each one names the Peplink InControl 2 actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Peplink InControl 2 devices have not checked in for a week? calls `peplink_incontrol2.devices.list` 2. Write write Create a group in Peplink InControl 2. Show me exactly what you will send before you save it. calls `peplink_incontrol2.groups.create` Governance for Peplink InControl 2 ## Destructive actions wait for a yes. 21 Peplink InControl 2 actions are destructive. These are all of them: - Delete SIM pool profiles `peplink_incontrol2.sim_pools.delete` - Delete Device Tags `peplink_incontrol2.device_tags.delete` - Add organization admin users `peplink_incontrol2.settings_admins.add` - Delete devices from an organization `peplink_incontrol2.delete_devices.delete` - Delete Starlink pool profiles `peplink_incontrol2.starlink_pools.delete` - Delete SIM pool profiles `peplink_incontrol2.group_sim_pools.delete` - Delete organization admin users `peplink_incontrol2.settings_admins.delete` - Remove Devices `peplink_incontrol2.esim_pool_devices.delete` - Delete Device Tags `peplink_incontrol2.group_device_tags.delete` - Delete Group MAC Addresses `peplink_incontrol2.group_grouped_mac.delete` - Delete a VLAN network settings `peplink_incontrol2.group_vlan_config.delete` - Delete a master configuration `peplink_incontrol2.group_clone_config.delete` - Add group admin users `peplink_incontrol2.group_settings_admins.add` - Delete an SSID profile `peplink_incontrol2.group_ssid_settings.delete` - Get docker scripts `peplink_incontrol2.group_docker_scripts.delete` - Delete Starlink pool profiles `peplink_incontrol2.group_starlink_pools.delete` - Delete group admin users `peplink_incontrol2.group_settings_admins.delete` - Disconnect group captive portal guest user sessions (deletion is asynchronous) `peplink_incontrol2.group_cp_guest_session.delete` - Disconnect device captive portal guest user sessions (deletion is asynchronous) `peplink_incontrol2.device_cp_guest_session.delete` - Get docker scripts log `peplink_incontrol2.group_docker_scripts_log.delete` - Delete firewall rule settings `peplink_incontrol2.group_firewall_rule_sets.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 peplink_incontrol2.sim_pools.delete confirm_policy: **human** Delete SIM pool profiles? **intent:** the user asked me to delete SIM pool profiles run suspended · waiting for a named person · key _peplink-incontrol2-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "peplink-incontrol2-agent", allowed_actions: ["peplink_incontrol2.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "peplink_incontrol2.sim_pools.delete", approver: "lead@example.com" }, { match: "peplink_incontrol2.device_tags.delete", approver: "lead@example.com" }, { match: "peplink_incontrol2.settings_admins.add", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Peplink InControl 2 only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Peplink InControl 2 costs on actionlake. Every Peplink InControl 2 action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Peplink InControl 2 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 375 Peplink InControl 2 actions - 375 actions page each page of a long list is one call - 245 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 Peplink InControl 2 action. 375 actions by area: the id your agent calls, what it does, and its effect. **Group docker scripts 4** - `peplink_incontrol2.group_docker_scripts.create` Create docker scripts write - `peplink_incontrol2.group_docker_scripts.delete` Get docker scripts destructive - and 2 more in this area **Group firewall rule sets 4** - `peplink_incontrol2.group_firewall_rule_sets.create` Create firewall rule set write - `peplink_incontrol2.group_firewall_rule_sets.delete` Delete firewall rule settings destructive - and 2 more in this area **Group grouped mac 4** - `peplink_incontrol2.group_grouped_mac.create` Create Grouped MAC Addresses write - `peplink_incontrol2.group_grouped_mac.delete` Delete Group MAC Addresses destructive - and 2 more in this area **Group settings admins 4** - `peplink_incontrol2.group_settings_admins.add` Add group admin users destructive - `peplink_incontrol2.group_settings_admins.delete` Delete group admin users destructive - and 2 more in this area **Group sim pools 4** - `peplink_incontrol2.group_sim_pools.create` Create SIM pool profiles write - `peplink_incontrol2.group_sim_pools.delete` Delete SIM pool profiles destructive - and 2 more in this area **Group starlink pools 4** - `peplink_incontrol2.group_starlink_pools.create` Create Starlink pool profiles write - `peplink_incontrol2.group_starlink_pools.delete` Delete Starlink pool profiles destructive - and 2 more in this area **Group vlan config 4** - `peplink_incontrol2.group_vlan_config.create` Create a VLAN network settings write - `peplink_incontrol2.group_vlan_config.delete` Delete a VLAN network settings destructive - and 2 more in this area **Settings admins 4** - `peplink_incontrol2.settings_admins.add` Add organization admin users destructive - `peplink_incontrol2.settings_admins.delete` Delete organization admin users destructive - and 2 more in this area **Sim pools 4** - `peplink_incontrol2.sim_pools.create` Create SIM pool profiles write - `peplink_incontrol2.sim_pools.delete` Delete SIM pool profiles destructive - and 2 more in this area **Starlink pools 4** - `peplink_incontrol2.starlink_pools.create` Create Starlink pool profiles write - `peplink_incontrol2.starlink_pools.delete` Delete Starlink pool profiles destructive - and 2 more in this area **Group device tags 3** - `peplink_incontrol2.group_device_tags.create` Add Device Tags write - `peplink_incontrol2.group_device_tags.delete` Delete Device Tags destructive - and 1 more in this area **Group ssid settings 3** - `peplink_incontrol2.group_ssid_settings.create` Create an SSID profile with a subset of settings write - `peplink_incontrol2.group_ssid_settings.delete` Delete an SSID profile destructive - and 1 more in this area **Delete devices 2** - `peplink_incontrol2.delete_devices.delete` Delete devices from an organization destructive - `peplink_incontrol2.delete_devices.get` Get status for delete devices from an organization read **Device client 2** - `peplink_incontrol2.device_client.get` Get a client's information in device level read - `peplink_incontrol2.device_client.list` Get a device's live client list read **Device CP guest 2** - `peplink_incontrol2.device_cp_guest.create` Insert device captive portal guest user info write - `peplink_incontrol2.device_cp_guest.update` Update device captive portal guest user info write **Device devapi 2** - `peplink_incontrol2.device_devapi.create` Execute device API for POST request endpoint write - `peplink_incontrol2.device_devapi.get` Execute device API for GET request endpoint read **Device loc 2** - `peplink_incontrol2.device_loc.list` Get a device's location read - `peplink_incontrol2.device_loc.update` Update a device's GPS location. write **Device oobm settings 2** - `peplink_incontrol2.device_oobm_settings.get` Get device InTouch settings and profiles read - `peplink_incontrol2.device_oobm_settings.update` Update device InTouch settings and profiles write **Device ssid profiles 2** - `peplink_incontrol2.device_ssid_profiles.get` Get a device's SSID profiles read - `peplink_incontrol2.device_ssid_profiles.update` Enable or disable a device level SSID profile write **Device tags 2** - `peplink_incontrol2.device_tags.create` Add Device Tags write - `peplink_incontrol2.device_tags.delete` Delete Device Tags destructive **Esim pool devices 2** - `peplink_incontrol2.esim_pool_devices.create` Add Devices write - `peplink_incontrol2.esim_pool_devices.delete` Remove Devices destructive **Esim pool iccid 2** - `peplink_incontrol2.esim_pool_iccid.create` Add ICCIDs write - `peplink_incontrol2.esim_pool_iccid.get` Get ICCIDs details from FSC redis read **Esim pool settings 2** - `peplink_incontrol2.esim_pool_settings.get` Get Pooled Plan Settings read - `peplink_incontrol2.esim_pool_settings.update` Update Pooled Plan Settings write **Group bulk config 2** - `peplink_incontrol2.group_bulk_config.create` Create a master configuration write - `peplink_incontrol2.group_bulk_config.update` Update a master configuration write **Group client 2** - `peplink_incontrol2.group_client.get` Get a client's information in group level read - `peplink_incontrol2.group_client.list` Get a group's live clients list read **Group CP guest 2** - `peplink_incontrol2.group_cp_guest.create` Insert group captive portal guest user info write - `peplink_incontrol2.group_cp_guest.update` Update group captive portal guest user info write **Group CP guest by user id 2** - `peplink_incontrol2.group_cp_guest_by_user_id.create` Create a captive portal guest user with the given username (user_id) write - `peplink_incontrol2.group_cp_guest_by_user_id.update` Update an existing captive portal guest user (user_id). Only the fields provided are changed write **Group device ip settings 2** - `peplink_incontrol2.group_device_ip_settings.get` Get device IP settings read - `peplink_incontrol2.group_device_ip_settings.update` Save device IP settings write **Group docker scripts log 2** - `peplink_incontrol2.group_docker_scripts_log.delete` Get docker scripts log destructive - `peplink_incontrol2.group_docker_scripts_log.get` Get docker scripts log read **Group grouped networks 2** - `peplink_incontrol2.group_grouped_networks.get` Get grouped networks read - `peplink_incontrol2.group_grouped_networks.update` Update named networks write Group move devices **2** Group SP default **2** Group ssid profiles **2** Group wifi management **2** Grouped networks **2** Groups **2** Move devices **2** SP default **2** Ads survey **1** Bandwidth per device **1** Bandwidth per device CSV **1** Device **1** Device air monitor **1** Device air monitor chutil **1** Device air monitor dates **1** Device air probe performance test **1** Device air probe performance test list **1** Device availability **1** Device availability CSV **1** Device bandwidth **1** Device cellular tower scan profiles **1** Device cellular tower scan result **1** Device cellular tower scan results **1** Device cellular tower scan results by report id **1** Device cellular tower scan results dates **1** Device cellular tower scan run **1** Device client captive portal access logs **1** Device client daily usages **1** Device client daily vlan usages **1** Device client hourly usages **1** Device client hourly vlan usages **1** Device client usage summary **1** Device config backup **1** Device config backup target convert **1** Device conn test reports **1** Device content blocking log **1** Device content blocking log dates **1** Device convert targets **1** Device CP **1** Device CP by CP id **1** Device CP captive portal user **1** Device CP client type **1** Device CP guest session **1** Device CP guest status **1** Device CP import guest **1** Device CP usage portal list **1** Device CP usage report **1** Device custom portals **1** Device daily client count **1** Device daily client list **1** Device dpi daily **1** Device dpi hourly **1** Device event log **1** Device event log archive list **1** Device event log types **1** Device external portal usages **1** Device firewall log **1** Device firewall log dates **1** Device GPS availability **1** Device hmi display **1** Device hourly client count **1** Device hourly client list **1** Device info **1** Device info by field **1** Device iot port **1** Device iot reports **1** Device ipsec history **1** Device ipsec history profile names **1** Device mediafast usages **1** Device name **1** Device note **1** Device online history **1** Device oobm links **1** Device oobm settings copy **1** Device pepvpn connection availability monthly **1** Device pepvpn status **1** Device pepvpn status V2 **1** Device pepvpn tunnel stat **1** Device pepvpn tunnel stat V2 **1** Device pepvpn usages **1** Device pepvpn usages CSV **1** Device poe usage daily **1** Device poe usage daily CSV **1** Device poe usage hourly **1** Device poe usage hourly CSV **1** Device poe usage monthly **1** Device poe usage monthly CSV **1** Device radio support **1** Device reader log **1** 196 smaller areas **196** This index shows a sample of each area. All 375 actions, with their inputs and prices, are in the [catalogue](https://actionlake.com/console/catalogue), which a free sandbox key can search. Questions ## The Peplink InControl 2 MCP server, answered. **Is there a Peplink InControl 2 MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 375 Peplink InControl 2 actions across group docker scripts, group firewall rule sets, group grouped mac and group settings admins, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Peplink InControl 2. **What do I need to connect Peplink InControl 2?** InControl 2 Client ID: in InControl click your email address (top right), scroll to Client Applications, New Client,… and Client Secret of the same InControl 2 client application. The free call account { op: "connections.requirements", service: "peplink_incontrol2" } lists exactly what to paste. **Can an AI agent delete or change things in Peplink InControl 2?** Only if its key allows it, and only with an explicit confirmation. 21 Peplink InControl 2 actions are destructive, including delete SIM pool profiles, delete Device Tags and add organization admin users. 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 Peplink InControl 2 API limit?** actionlake paces every call to the limits in the Peplink InControl 2 service file: 20 calls a second per connection. Repeated reads are answered from cache (245 Peplink InControl 2 actions can be), which never reaches Peplink InControl 2. **What does a Peplink InControl 2 action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (375 Peplink InControl 2 actions page). Cache hits, searches, dry runs and calls Peplink InControl 2 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 Peplink InControl 2 API does it cover?** The InControl 2 REST API (api.ic.peplink.com/rest) at api.ic.peplink.com. It is built from Peplink InControl 2's documentation as read on 23 October 2026. 375 actions in 315 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Peplink InControl 2 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 Peplink InControl 2 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 Peplink InControl 2 Shares the most action names with - [Veeam Service Provider Console 5](https://actionlake.com/connectors/veeam-service-provider-console) - [N-able N-central 4](https://actionlake.com/connectors/n-able-n-central) - [Auvik 3](https://actionlake.com/connectors/auvik) - [Admin By Request 2](https://actionlake.com/connectors/admin-by-request) - [Ubiquiti UniFi Site Manager API 2](https://actionlake.com/connectors/ubiquiti-unifi-site-manager-api) - [Crayon CloudIQ 2](https://actionlake.com/connectors/crayon-cloudiq) Joins with, on shared entities - [Microsoft 365 Users 2](https://actionlake.com/connectors/microsoft-365-users) - [JumpCloud 2](https://actionlake.com/connectors/jumpcloud) - [Yext 2](https://actionlake.com/connectors/yext) - [Google Workspace Directory 2](https://actionlake.com/connectors/google-workspace-directory) - [Slack 1](https://actionlake.com/connectors/slack) - [Gusto 1](https://actionlake.com/connectors/gusto) 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 Peplink InControl 2; the name is the vendor's own. Counts are from the Peplink InControl 2 service file, version 1.0.0. ## Give your agent Peplink InControl 2 today. [Connect Peplink InControl 2 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/peplink-incontrol-2 More: https://actionlake.com/llms.txt