Connectors · MSP & PSA

Admin By Request MCP server for AI agents.

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

Connect Admin By Request 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

22actionsin one signed file
16readlook, never change
2writecreate and update
4wait for a yesdestructive, confirmed first

Set up

Connect Admin By Request 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 Admin By Request.
API key. 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_keyAdmin By Request API key: portal > Settings > Tenant Settings > Data > API KEYS > Add New
- hostWhere your Admin By Request lives: your host
```
account { op: "connections.requirements", service: "admin_by_request" }
# 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: "admin_by_request.inventory.list" }# inventory: list · read · 1 upstream callcheck { action: "admin_by_request.inventory.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Admin By Request at a glance

Sign-in: API key. 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_key
Setup fields: host
Limits we pace to: 100,000 calls a day and 10 a second, per connection
API covered: Public API, at your Admin By Request instance's API base URL, which you enter when connecting
Built from: Admin By Request's documentation, read 23 October 2026docs.adminbyrequest.com adminbyrequest.com adminbyrequest.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 14 of 16 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 1, so ask can line Admin By Request up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Admin By Request.

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

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

Endpoint privilege
22
16 read · 2 write · 4 destructive
Inventory: list · Inventory: get · Inventory: delete · Auditlog: delta

Top actions

The Admin By Request API, shaped for agents.

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

Action	What it does	Effect	Same name in
`admin_by_request.inventory.list`Inventory: list	Lists computers in the inventory with user, OS, hardware, network and location details.	read	`device.endpoint.list`65 connectors
`admin_by_request.inventory.get`Inventory: get	Returns one computer's inventory by computer id.	read	`device.endpoint.get`57 connectors
`admin_by_request.inventory.delete`Inventory: delete	Deletes a computer from the inventory by id.	destructive	`device.endpoint.delete`35 connectors
`admin_by_request.auditlog.list`Auditlog: list	Lists audit log entries (Run As Admin and Admin Session usage, approvals, denials) in ascending id order, last 30 days by default.	read	this connector
`admin_by_request.requests.list`Requests: list	Lists elevation requests (Run As Admin, Admin Session, Server Session) awaiting or past approval, e.g.	read	this connector
`admin_by_request.auditlog.delta`Auditlog: delta	Returns audit log entries changed since the last call (new, approved, used...) plus timeNow; feed timeNow back as delta_time next time.	read	this connector
`admin_by_request.requests.get`Requests: get	Returns one elevation request.	read	this connector
`admin_by_request.requests.approve`Requests: approve	Approves a pending elevation request; the end user is notified.	write	this connector
`admin_by_request.inventory.set_owner`Inventory: set owner	Sets the device owner of a computer.	write	this connector
`admin_by_request.inventory.get_by_name`Inventory: get by name	Returns one computer's inventory by computer name.	read	this connector
`admin_by_request.events.list`Events: list	Lists security events (local admin changes, blocked executions, break-glass use, installs...) in ascending id order, last 30 days by default.	read	this connector
`admin_by_request.events.list_for_user`Events: list for user	Lists events for one user (account or full name).	read	this connector

Try it

Prompts to paste into Claude.

Each one names the Admin By Request actions it will call, so you know what it reads and what it changes before you send it.

Readread
Which Admin By Request devices have not checked in for a week?
callsadmin_by_request.inventory.list
Writewrite
Requests: approve in Admin By Request. Show me exactly what you will send before you save it.
callsadmin_by_request.requests.approve

Governance for Admin By Request

Destructive actions wait for a yes.

4 Admin By Request actions are destructive. These are all of them:

Inventory: deleteadmin_by_request.inventory.delete
Inventory: clear owneradmin_by_request.inventory.clear_owner
Inventory: delete by nameadmin_by_request.inventory.delete_by_name
Requests: denyadmin_by_request.requests.deny

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.

doadmin_by_request.inventory.deleteconfirm_policy: human

Inventory: delete?

intent: the user asked me to inventory: delete

run suspended · waiting for a named person · key admin-by-request-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "admin-by-request-agent",  allowed_actions: ["admin_by_request.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "admin_by_request.inventory.delete", approver: "[email protected]" },    { match: "admin_by_request.inventory.clear_owner", approver: "[email protected]" },    { match: "admin_by_request.inventory.delete_by_name", approver: "[email protected]" }  ]}

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

Cost

What Admin By Request costs on actionlake.

Every Admin By Request action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Admin By Request 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 22 Admin By Request actions
22actions pageeach page of a long list is one call
14reads 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 Admin By Request action.

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

Endpoint privilege22

admin_by_request.auditlog.deltaAuditlog: deltaread
admin_by_request.auditlog.getAuditlog: getread
admin_by_request.auditlog.listAuditlog: listread
admin_by_request.auditlog.list_for_computerAuditlog: list for computerread
admin_by_request.auditlog.list_for_userAuditlog: list for userread
admin_by_request.events.getEvents: getread
admin_by_request.events.listEvents: listread
admin_by_request.events.list_for_computerEvents: list for computerread
admin_by_request.events.list_for_userEvents: list for userread
admin_by_request.inventory.clear_ownerInventory: clear ownerdestructive
admin_by_request.inventory.deleteInventory: deletedestructive
admin_by_request.inventory.delete_by_nameInventory: delete by namedestructive
admin_by_request.inventory.getInventory: getread
admin_by_request.inventory.get_by_nameInventory: get by nameread
admin_by_request.inventory.listInventory: listread
admin_by_request.inventory.set_ownerInventory: set ownerwrite
admin_by_request.pin_codes.getPin codes: getread
admin_by_request.pin_codes.get_by_namePin codes: get by nameread
admin_by_request.requests.approveRequests: approvewrite
admin_by_request.requests.denyRequests: denydestructive
admin_by_request.requests.getRequests: getread
admin_by_request.requests.listRequests: listread

Questions

The Admin By Request MCP server, answered.

Is there an Admin By Request MCP server for Claude?

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

What do I need to connect Admin By Request?

Admin By Request API key: portal > Settings > Tenant Settings > Data > API KEYS > Add New. Plus your host. The free call account { op: "connections.requirements", service: "admin_by_request" } lists exactly what to paste.

Can an AI agent delete or change things in Admin By Request?

Only if its key allows it, and only with an explicit confirmation. 4 Admin By Request actions are destructive, including inventory: delete, inventory: clear owner and inventory: delete by name. 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 Admin By Request API limit?

actionlake paces every call to the limits in the Admin By Request service file: 100,000 calls a day and 10 a second per connection. Repeated reads are answered from cache (14 Admin By Request actions can be), which never reaches Admin By Request.

What does an Admin By Request action cost?

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

The public API at your Admin By Request instance's API base URL, which you enter when connecting. It is built from Admin By Request's documentation as read on 23 October 2026. 22 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Admin By Request 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 Admin By Request 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 Admin By Request today.