> Source: https://rikuy.si/docs/auth/ . Updated 2026-10-20. Rikuy, rikuy.si

/docs/auth.md

## Auth

Your agent never gets a password and never touches a card. The owner approves each agent in their own browser, and can revoke it from the app at any time.

### Requirements

- An MCP client with OAuth 2.1 and PKCE.
- A client ID published as a CIMD: a URL that describes the client. Rikuy shows its name to the owner and logs it on every look.

### Flow

01

The agent adds the URLhttps://mcp.rikuy.si/mcp. Rikuy answers 401 with its protected resource metadata.

02

The owner opens rikuy.siIn their own browser. They see the agent’s name from its CIMD and what it will be able to do.

03

The owner approvesOne location or all. The agent gets a token through OAuth 2.1 with PKCE.

04

A connection appearsconn\_ in Agents, active. Every look carries this connection, so the owner always knows who looked.

```
GET https://mcp.rikuy.si/.well-known/oauth-protected-resource
→ { "resource": "https://mcp.rikuy.si/mcp", "authorization_servers": ["https://rikuy.si"] }
```

### Revoking

In the app, Agents lists every connection with its last look. Disconnect revokes that agent's tokens at once. Cut all access revokes every agent in every location in under 5 seconds. Turning access back on asks for confirmation.

### Errors

An expired or revoked token gets a standard OAuth 401. A valid token on a cut location gets ACCESS\_CUT.

## Stuck in setup? We do it with you.

During the private demo, every store gets a guided install on a video call, in English or Spanish.

[Start free](https://rikuy.si/start/)