Skip to content
All documentation

Devices and tokens

Video

Devices, tokens and safety

2:58 · in English, with subtitlesVideo page · All video tutorials
Chapters (6)

A device in OnlyMCP is anything that holds access to your account. This page says what that covers, what a token is, which of these count towards the limit of your plan, and how to give a token fewer rights or a date on which it ends.

What a device is

Each of these has one row under Sessions and devices in the dashboard, and each can be revoked on its own:

  • a browser session, where you are signed in on the website;
  • a command line login, made by onlymcp login on one machine;
  • an access token, the omk_ key you paste into a client;
  • a connected app, a chat app or another client you let in through an OAuth sign-in.

What a token is

An access token starts with omk_ and goes into the header of a client that cannot sign in by itself. It is shown once, right after you create it: OnlyMCP stores only a fingerprint of it, so a lost token cannot be shown again, only replaced.

Make one token per client and name it after the client, such as Cursor or Claude Code. The list under Manage tokens then tells you what each one is for, and revoking one stops only that client. On a client page under Connect, the button New token for that client does this in one click: it names the token after the client, gives it full rights and 365 days.

What counts towards the limit

Your plan allows a number of connected clients, shown in the dashboard as, for example, 2 of 3 connected clients. These count:

  • command line logins,
  • tokens that are not revoked and have not expired,
  • connected apps.

Browser sessions do not count. Free allows three connected clients; the other plans are on the pricing page. When the limit is full, a new token or app is refused with a message. Remove one you no longer use, or replace the oldest unused one with one click on the same page.

Rights of a token

A token made without a choice has full access. The token form offers four presets:

PresetWhat the token may do
Full accessEverything your account may do, including the tools of the servers you connected.
Read onlyOnly the tools that read: listing, reading and searching memory, skills and agents. Nothing is changed.
Memory onlyThe memory tools, reading and writing. No skills, no agents, no connected servers.
No connected serversEvery OnlyMCP tool, but no tool of a connected server.

A client that uses a token with fewer rights is shown only the tools the token may call. If an agent calls another one anyway, it gets this answer: This token may not call memory_write: its scope is read. Create a token with more rights under Connect. A sign-in through OAuth, as chat apps use it, always has full access.

Expiry and the reminder mail

The token form starts at 90 days. You can choose never, one hour, 24 hours, 30, 90 or 365 days, or a date up to ten years ahead. A token that expires stops working on that day and no longer counts towards the limit.

Seven days before a token expires, OnlyMCP sends you one mail that names the token and the date, and the list shows Expires in 3 days instead of the date. A token made for fewer than seven days gets no mail, and neither does a revoked one. To replace a token that is about to expire, create a new one under Connect, put it into the client, and revoke the old one.

Where to revoke

  • Under Sessions and devices, every row has Revoke. A revoked token stops working at once; a revoked app has to be connected again.
  • Under Connect, Manage tokens lists the tokens with their rights and dates.

The command line login as a device

onlymcp login signs a machine in through your browser and counts as one device, with the machine's name. onlymcp logout ends that session on the server, so the machine no longer counts.

npx onlymcp login npx onlymcp logout