Using the app

Integrations

Integrations connect the chat and agents to external services and programs, for example GitHub or a memory server. You set them up once on the Integrations page, then choose in Access who uses them. Every action asks you first.

What they areAdding oneTools and confirmationsIn the chat and in agentsPrivacyOld MCP serversComing soon

What they are

An integration is an MCP server (Model Context Protocol): an open standard for giving models external tools, such as memory, calendars, databases and web services. There are two kinds:

KindHow it works
On this PCA program HotMoE starts on your computer. Data stays on the PC, except what the program itself sends over the network.
Remote (online)An online service at an https:// address. The model's requests and the answers go over the internet and through the service provider. In the lists it has the ONLINE tag.

Integrations are yours, not a single agent's: like email accounts, you set them up once and then tick them where you want to use them.

Adding an integration

  1. Open the Integrations page from the bar on the left and choose Add integration.
  2. Fill in the fields (see the table below).
  3. Press Connect and show the tools. The app saves, connects to the server and lists its tools.
  4. Choose the tools to turn on, then tick the integration where you want to use it: in the chat or in an agent (see below).
FieldWhat it is for
NameHow you recognize it in the lists. In the chat it is also the name of its role.
What it is forOne sentence, with verbs for what it does (for example: "the user's GitHub: issues, pull requests, code review"). The chat uses it to know when these tools are needed; if empty, it uses the tool names.
Where it runsOn this PC or Remote (online).
CommandOn this PC. The program to start with its arguments, as in the server's documentation: for example npx -y @modelcontextprotocol/server-memory.
Keys and variablesOn this PC, optional. The environment variables the server wants, for example GITHUB_TOKEN. Values are saved encrypted and never shown again: to change one, type the new value; leave the field empty to keep the saved one.
AddressRemote. The service address, starting with https://.
Sign-inRemote. None, Token (personal key) or Sign in with the browser (OAuth).

Sign in with the browser (OAuth)

With OAuth, Connect and show the tools opens the browser to sign in to the service. HotMoE never sees your password: it only saves the permission, encrypted, and renews it by itself.

If the sign-in expires, the chat does not open the browser by itself: it shows a note asking you to sign in again from the Integrations page.

If a program is missing

Many integrations on the PC start with npx (Node.js), uvx (uv) or Docker. If the program is not installed, the page tells you before trying to connect, with a Where to get it link.

Tools and confirmations

  • After connecting, under Tools, each tool of the server appears with a switch.
  • By default only the tools the server declares read-only are on (marked read-only). Turn on the others if you want the model to be able to change things too.
  • Every call to a tool still asks you first, showing you the data it is about to receive.
  • Always allow applies to the single tool, not to the whole integration. You revoke it in Access › Permissions (for an agent, in its editor).
  • Every call goes to the Log, including the ones you denied. They cannot be undone.

In the chat and in agents

An integration you set up does nothing until you tick it:

  • In the chat: in Access, section Integrations, tick the ones the chat can use.
  • In an agent: in the agent editor, section Integrations.

Next to the checkboxes, the Set them up on the Integrations page link brings you here, to add or change one.

In the chat, each ticked integration is a role, like Files, Email or Screen, named after the integration. The chat activates it only when the request is about that service, and only then does the model receive its tools. Local models have little context: this way it doesn't fill up with tools that aren't needed.

If the chat doesn't use it

The chat decides by looking at the What it is for field. If it doesn't activate the integration when it should, make that sentence more precise, with verbs for what it does.

Privacy

  • On this PC: data stays on your computer, except what the program itself sends over the network.
  • Remote: the model's requests and the answers go over the internet to the service provider. Connect it only if you trust it.
  • The chat header tells you. Normally, next to the model, it reads "· local, nothing leaves your PC". When you tick a remote integration, it becomes "· also uses online services:" followed by their names.
  • Variable values, tokens and sign-in permissions are saved encrypted and never shown again.
Caution

An integration on the PC is an external program that runs with your permissions, outside the granted folders. Only add integrations you trust. See also Privacy and security.

Old MCP servers in agents

Before, MCP servers were added inside each agent, in the MCP servers section of the editor. Those servers became integrations automatically: you find them on the Integrations page, already ticked in the agents that used them. The same server in several agents became a single integration.

Coming soon

Coming soon
  • A catalog of ready-made integrations, added with one click: GitHub, Browser (Playwright), Notion, Calendar (Google/Microsoft), Database (SQLite/PostgreSQL), Google Drive, Slack.

HotMoE is a Virsion project. This guide describes the app as it is today: what is still on the way is marked as such.