# holaOS [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/holaboss-ai/holaOS  
**GitHub Stars:** 11358  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/holaos

## Description
Open-source agentic workspace enterprises can make their own. Connect the systems you already run — 100+ integrations, MCP, chat tools, apps, browser, local files — with shared memory. Any agent (Claude Code, Codex), any model, or BYOK. Set up in clicks, not months. Local-first: your data never leaves your machines.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/holaboss-ai/holaOS), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

```sh
curl -fsSL https://raw.githubusercontent.com/holaboss-ai/holaOS/refs/heads/main/scripts/install.sh | bash -s -- --launch
```

## Documentation

## What holaOS does

holaOS combines agents, applications, integrations, chat systems, local files, browser access, models, skills, and shared memory in a desktop workspace. Agents can work beside live application interfaces instead of returning only chat transcripts. An app can be installed from the in-workspace marketplace, connected to a URL, or paired with an MCP server.

The workspace is intended for teams whose operational context is spread across systems such as Slack, Feishu, DingTalk, WeChat, Gmail, Notion, GitHub, and Linear. Connections can be reused by agents in the same workspace, while access is granted per tool and scope.

## How it works

holaOS runs as an Electron desktop application with support for macOS on Apple Silicon and Intel, Windows, and Linux. Agents can operate interactive app surfaces while a person watches the work, takes control, or continues using the interface manually. UI actions such as clicks, typed text, and opened pages become available as agent context.

MCP support allows users to add external Model Context Protocol servers, either their own or community servers installed through the workspace. Skills package repeatable workflows, and combos can group skills and integrations into one installation. Agents can share tools, skills, apps, and memory across sessions.

Memory, embeddings, workspace files, and session history are stored locally as plain files. This lets users read and edit memory directly and continue work across agents and sessions. The workspace can also connect built-in or user-provided model endpoints, including OpenAI- and Anthropic-compatible providers.

## Setup and configuration

Install holaOS as a desktop application on macOS, Windows, or Linux. After starting the workspace, add applications and integrations from its marketplace, connect chat tools or MCP servers, and approve the scopes each agent may access. A HolaApp can also point to a URL and an MCP server for locally available use.

The model setup supports built-in models through one account as well as bring-your-own-key configurations for OpenAI, Anthropic, and compatible endpoints. Agents available in the workspace include Claude Code, Codex, and the built-in holaOS agent.

## Tools and capabilities

- Connect external MCP servers to provide additional agent tools.
- Add integrations for services including Gmail, Notion, Slack, GitHub, and Linear.
- Read approved conversations from Slack, Feishu, DingTalk, and WeChat.
- Operate signed-in browsers for browsing, clicking, and extracting information.
- Work with local files and save reports, spreadsheets, and presentations as `.docx`, `.xlsx`, and `.pptx` files.
- Store shared memory locally across agents and sessions.
- Run workflows on schedules or triggers.
- Use skills and combos to package repeatable workflows and integrations.

## Limitations and notes

holaOS is designed for local desktop use, with support listed for macOS, Windows, and Linux. Agents do not automatically receive access to connected tools: users approve connections, reads, and file actions. The product supports external MCP servers, but those servers remain separate components that must be supplied or installed.

The project is distributed under a Modified Apache 2.0 license. Model availability, provider costs, and access behavior depend on whether built-in models or user-managed provider keys are used.

_Full upstream README: https://allmcps.com/mcp/holaos/readme_

