MCP server

claude mcp add --transport http unrent https://mcp.unrent.dev/mcp

Other clients: add an HTTP MCP server with the URL https://mcp.unrent.dev/mcp. The client discovers sign-in on its own. It must speak revision 2026-07-28; older clients that send initialize get an error naming the supported version.

On first use your browser opens app.unrent.dev. You choose one organisation and the scopes to grant; the page shows how the client described itself, marked unverified.

Your current role is checked on every call, so demoting or removing a member takes effect at once. There is no tool that creates or deletes anything; services are created by a person in the console.

1. 01

   The agent asks

   A change tool returns status: "approval_required" with a job_id, the job’s SHA-256 digest and an approve_url.

2. 02

   A person reviews

   The approval page is drawn from the signed job (kind, server, resource, parameters), never from text the agent wrote, and names the app that asked.

3. 03

   Approve with a passkey

   The approver signs that digest. Only then is the job delivered to the server. With the two-person rule on, the member whose agent asked cannot approve it.

4. 04

   Follow it

   The agent polls get_job until succeeded or failed. A job nobody approves expires after 10 minutes.

Clients that support URL elicitation get the approval link as an input_required result and can wait for it.

get_logs returns a summary by default (levels, distinct messages with counts); raw: true adds up to 64 KiB of lines. Control characters, escape sequences and credentials are stripped, and the result says that log text is untrusted.

Settings → Connected apps lists each connected app, who connected it, its scopes and when it was last used. Members revoke their own; admins and owners can revoke anyone’s. Access tokens last 1 hour; each refresh token works once.