Connected MCP tools
When an agent works in Uniloom, on Home or in an automation, it reaches the MCP servers its own config declares, plus the apps you connected in Uniloom. Here, Uniloom reaches other servers. For the other direction, your agents reaching Uniloom, see Uniloom as an MCP server.
Servers from the agent's config#
Uniloom keeps no server list of its own. The agent's command-line tool loads the servers in its config, for the profile it runs under and the project's folder, and reports which ones connected. Connect → Agents sets the profile; an agent's dialog lists its servers and how each stands (An agent's dialog). Change a server in Toolkit or in the agent's own config.
Apps you connected in Uniloom#
An app connected in Connect → Integrations, such as Linear, Notion or Jira, can be read from every session, even when the agent's config has no server for it, while Uniloom is open. Uniloom's connected_tools tool lists the apps and their reading tools, and read_connected reads through one with Uniloom's own sign-in. Tools that change anything are never offered (MCP tool reference).
Last updated