> Yomates Help Center - all pages: https://yomates.ai/llms.txt

# MCP server

> Let Claude Code, Codex or another MCP client in a terminal give your agents work, or use the first agent's browser, canvas and apps itself.

## Turn on the MCP server

MCP (Model Context Protocol) lets an AI tool in a terminal, such as Claude Code, use Yomates' tools. You watch the work in Yomates as if the agent were doing it.

1. Click your name at the bottom of the agent list, then **Settings**.
2. Open **Developers**.
3. Turn on the **MCP server** switch.

A **Connect Claude Code or Codex** panel appears with a setup prompt and a **COPY SETUP PROMPT** button. The prompt holds the server's address, the token and the setup for each kind of client. The preview shows only the token's last six characters; the copy has all of it.

The switch is remembered, so the server starts with the app. It runs only while Yomates is open, and it listens on `127.0.0.1` only: it answers programs on this computer and nothing else on your network.

## Connect your terminal

::: tabs

@tab Claude Code

1. Click **COPY SETUP PROMPT**.
2. Paste it into Claude Code and send it. Claude Code runs a line of this shape:

```
claude mcp add --scope user --transport http leviosa http://127.0.0.1:19222/mcp --header "Authorization: Bearer YOUR_TOKEN"
```

@tab Codex

1. Click **COPY SETUP PROMPT**.
2. Paste it into Codex and send it. Codex adds the server's block to `~/.codex/config.toml`.

@tab Another client

Paste the setup prompt into the client's AI, or copy the prompt's `mcpServers` JSON block into the client's MCP settings. If it asks for the parts separately, the URL is `http://127.0.0.1:19222/mcp` over HTTP, and the token goes as a bearer token in the `Authorization` header.

:::

The server is named `leviosa`. If its tools load only after a restart, the AI tells you to restart it. Once they load, it calls `tools` to show the connection works.

## What a terminal can do

The server offers three tools:

- `message` says a line to any agent, as if you typed it in its chat, and brings back the reply. With no agent named, it goes to the first agent in your list.
- `tools` lists the first agent's own tools, such as its browser, canvas and connected apps.
- `call` runs one of them. To use another agent's tools, drag that agent to the top of the list.

Every call shows in Yomates as the agent's own work does: hands on its browser, the canvas it writes, a row in its chat. If you edit the agent or clear its chat, the next call uses the new session.

- **The agent's permissions apply.** A call the agent would need your OK for waits for it in that agent's chat. A refused call comes back with the reason the agent would get. See [Ask first or skip](/docs/approvals).
- **No shell commands.** The agent's shell tool is left out; your terminal has its own.
- **Your hands come first.** After you click **TAKE OVER** on the agent's browser, every call is refused until you click **HAND BACK**. See [Watch an agent work](/docs/browser).

> [!WARNING]
> A terminal's calls and the agent's own work aren't queued. Give the terminal an agent that isn't busy in its own chat, or both act on one browser at once.

## Keep the token safe

The token lets a program on this computer drive your agents, so treat it like a password.

- It's kept in `mcp.json` in the app's data folder and is never part of the cloud backup.
- To change it, turn the **MCP server** switch off and on again. Off deletes the file and the token and closes the server at once; on makes a new token. Copy the setup prompt again and update your clients.