> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hired.tools/llms.txt
> Use this file to discover all available pages before exploring further.

# Account and connection tools

> Six tools for finding out who a connection belongs to, and for managing the wiring itself without opening a browser.

"Add this to my work laptop" and "kill the one I pasted in a chat by mistake" are things
you can just say.

<Warning>
  `list_connections` deliberately never returns tokens. They are credentials, they would
  sit in a transcript forever, and the only place anyone needs to see one is the client
  they are pasting it into. `create_connection` and `rotate_connection` **do** return one,
  because handing it over is the point of them — treat what comes back like a password.
</Warning>

Prefer `rotate_connection` over `delete_connection` when the client is still in use and
only the URL has leaked: rotating keeps the row and its name, and kills the old address the
moment it returns. It also clears the last-used stamp, and the list is ordered by last use —
so a rotated connection drops to the bottom until the client calls in on the new URL, which
is a useful way to see whether anyone actually pasted it.

[Connecting an assistant →](/connect)

<Note>
  The descriptions below are quoted **verbatim** from what the server sends a connected
  assistant, which is why they address it rather than you. They are reproduced rather than
  rewritten so this page cannot drift from what your assistant actually receives.
</Note>

### `whoami`

*Who am I connected as*

The account this connection belongs to: name, email, role, and whether it can administer the instance. Every other tool acts as this person and can only see their data.

No arguments.

### `list_connections`

*List AI connections*

Every assistant wired to this workspace: what it is called, which client it was set up for, when it last called in and from what. Reach for it to answer 'which of these am I still using?' or before rotating something — the ids come back here. Tokens deliberately do not: they are credentials, they would sit in this transcript forever, and the only place a person needs to see one is the client they are pasting it into. `isThisOne` marks the connection you are calling through right now.

No arguments.

### `create_connection`

*Connect another assistant*

Mint a new connection URL so a second client — the laptop's editor, a phone app, a terminal — can reach this workspace too. Returns the URL and the exact steps for that client, so you can hand somebody a copy-paste answer to 'how do I add this to Cursor?'. Give every client its own rather than sharing one: that is what lets a single laptop be disconnected later without breaking everything else. The URL is a credential with full read and write over this person's brain, resumes and pipeline — say so when you hand it over, and never post it anywhere it will be stored.

| Argument | Type   |                                                                                                                                                                 |
| -------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `client` | string | Which client it is for: claude \| claude-code \| chatgpt \| cursor \| vscode \| windsurf \| generic-http \| stdio-bridge \| raw. Sets the setup steps returned. |
| `name`   | string | What to call it in the list, e.g. 'Cursor — work laptop'. Defaults to the client's name.                                                                        |

### `rename_connection`

*Rename a connection*

Change what a connection is called in the list. Names are for the person, not the machine — 'Cursor — old laptop' is what makes it obvious later which one to revoke. Get the id from list\_connections.

**Overwrites or deletes.**

| Argument | Type   |                              |
| -------- | ------ | ---------------------------- |
| `id`     | string | **required** — Connection id |
| `name`   | string | **required** — The new name  |

### `rotate_connection`

*Issue a new token for a connection*

Kill a connection's URL and issue a fresh one on the same row, keeping its name and place in the list. This is the answer to 'I sold that laptop' or 'I pasted the URL in a chat by mistake' — the old address stops working the moment this returns, and nothing else is affected. It also means the client that was using it goes dark until somebody pastes the new URL in, so say that before doing it. Returns the new URL; treat it like the password it is.

**Overwrites or deletes.**

| Argument | Type   |                                                      |
| -------- | ------ | ---------------------------------------------------- |
| `id`     | string | **required** — Connection id, from list\_connections |

### `delete_connection`

*Disconnect an assistant*

Remove a connection for good. Its URL stops working immediately and cannot be brought back — a replacement is a new connection with a new URL. Prefer rotate\_connection when the client is still in use and only the URL has leaked. Check list\_connections first: deleting the one you are calling through ends this session mid-conversation.

**Overwrites or deletes.**

| Argument | Type   |                                                      |
| -------- | ------ | ---------------------------------------------------- |
| `id`     | string | **required** — Connection id, from list\_connections |