AI agents

Give your agent hands. Keep the keys.

Esper speaks the Model Context Protocol out of the box. Your assistant gets real reach into your machines, and you keep the same guarantees you have: pairing, scoped permissions, visible presence, and a local log of everything.

AI agents

First-class MCP support. With guardrails.

Esper speaks the Model Context Protocol out of the box, so your AI assistant can reach your machines the same way you do: paired, permissioned, and encrypted. Never through anyone's cloud.

Claudeover MCPTerminal only

Is the NAS running out of space?

Connected to basement-nasDirect · encrypted
Ran df -hYou approved
Asked to view the screenBlocked · outside scope

You're fine. /srv has 412 GB free, 38% used. Nothing needs attention.

Agent visible on hostEvery call logged locally
Works with+ more

Your agent, hands on

Esper ships a built-in MCP server. An assistant like Claude can check on a server, run a command or read a screen for you, through your own connections.

Agents are devices too

An agent pairs like any other device and gets its own key, with permissions you scope down to exactly what it may touch. Revoking it takes one click.

Nothing happens silently

Sensitive actions ask on your screen first, the presence indicator shows when an agent is looking, and the panic key ends agent sessions too.

Every action on the record

Each tool call lands in the local audit log, so you can always see what your agent did, when, and on which machine.

Scopes

Every tool maps to a permission you grant.

An agent can only call what its device grant allows. Everything else fails cleanly, is logged, and never prompts the person on the other end.

ToolNeeds scope
list_devicesnone
session_statusnone
shellterminal
screenshotview
inputcontrol
file_read / file_writefiles
clipboardclipboard

Unattended access is a separate grant, given only at the host. An agent never gets it implicitly.

Setup

Wired up in two minutes.

One command registers Esper with your MCP client. The agent runs locally over stdio, gets its own device key on first start, and you approve its pairing on each machine like any other device.

  • Works with any MCP client: point it at esper mcp and you're done.
  • Everything stays local. The agent talks to Esper over stdio, and Esper talks to your machines over your own paths.
  • Scope it in the app: pick exactly which machines and permissions the agent gets, and change your mind any time.