← Back to directory
L

LobsterAI

Community
NetEase Youdao's open-source desktop AI agent for office work — an MCP client/host, not an MCP server itself
GitHub source repository ↗
★ 5.8k Stars Category · Other Very popular
50FMRS · D
Reliability
5/20
Security and permissions
10/20
Maintenance
13/20
Documentation
14/20
Setup experience
8/20

The source material describes LobsterAI as an open-source desktop AI agent application (an MCP client/host), not an MCP server that other clients connect to; no evidence of an MCP server manifest, tool list, transport, or install configuration was found, so this profile focuses on its actual functionality, permissions, and risks as a desktop automation tool.

Read the FMRS scoring method →

LobsterAI is an open-source desktop Agent application from NetEase Youdao (Electron-based, macOS and Windows) that operates in a real desktop environment — local files, terminal commands, browser workflows, documents, spreadsheets, slides — and can be remotely controlled via IM channels such as WeChat, WeCom, Feishu/Lark, DingTalk, and Telegram. Its product/session layer is called Cowork, running on the OpenClaw execution runtime underneath. The README states LobsterAI can connect to external Model Context Protocol (MCP) servers as tools/data sources, storing user-configured servers locally and syncing enabled ones into OpenClaw — meaning LobsterAI itself acts as an MCP client/host, not as a server that exposes MCP tools. No MCP server manifest, tool list, transport, or install configuration for consuming LobsterAI as an MCP server is present in the source material, so those fields are left empty rather than guessed.

Tools

The tool list has not been reviewed yet.

Setup

The source material does not describe an install configuration for connecting to this project as an MCP server from another client. The repository itself is installed as a desktop application: download the macOS/Windows installer from the official site or GitHub Releases, or clone the repo and run npm install with Node.js >=24.15.0 <25; first development run uses npm run electron:dev:openclaw, subsequent runs use npm run electron:dev (renderer dev server at http://localhost:5175).

Fit and risk

Best for

  • Users who want a desktop-grade AI agent that can directly operate local files, terminal, and browser workflows
  • Users who want to remotely trigger desktop Agent tasks via WeChat, Feishu, DingTalk, Telegram, or similar IM channels
  • Users needing office automation for documents, spreadsheets, slides, video, and web research
  • Developers comfortable with Electron/React/TypeScript who want to build from source or use official installers

Not for

  • Users who need an MCP server that a standard MCP client (e.g. Claude Desktop) can connect to directly — no such server manifest or tool definitions are provided in this repository
  • Users needing a headless or server-side deployment — this project only ships as a macOS/Windows desktop application
  • Users who want a narrow, single-purpose tool integration without granting broad file, terminal, and network permissions

Required permissions

  • Local file system read/write
  • Terminal command execution
  • Browser automation
  • Network access
  • IM channel binding and messaging (WeChat, WeCom, DingTalk, Feishu/Lark, QQ, Telegram, Discord, NetEase IM, NetEase Bee, POPO, email)
  • Local SQLite storage (lobsterai.sqlite under Electron userData)

Risks and side effects

  • The app requires broad, sensitive permissions (file operations, terminal, network); the README notes sensitive actions are permission-gated and logged, but users must still review approval prompts carefully to avoid data loss or exposure
  • Remote control via IM channels means commands can trigger desktop actions from linked messaging accounts — compromise of a bound account/channel could lead to unauthorized local execution
  • Packaging bundles the OpenClaw runtime and, on Windows, a portable Python runtime, expanding the local attack surface
  • This project is not maintained by the MCP protocol owner and is not a conventional MCP server; anyone wanting standard MCP-protocol integration should verify exposed behavior directly, as the source material gives no such details

Troubleshooting

  1. Verify Node.js version meets >=24.15.0 <25
  2. First run requires `npm run electron:dev:openclaw` to build/pin the OpenClaw runtime; subsequent runs can use `npm run electron:dev`
  3. Force a runtime rebuild with the `OPENCLAW_FORCE_BUILD=1` environment variable if needed
  4. Point to a custom OpenClaw checkout via the `OPENCLAW_SRC` environment variable
  5. Check that permission prompts for sensitive actions (file, terminal, network) are being approved correctly
  6. Inspect gateway logs under `userData/openclaw` for runtime issues
  7. In source-build mode, confirm the renderer dev server is running at http://localhost:5175

Use cases

Turn an Excel-based inventory workflow into a local inventory/sales system
Build a visual dashboard from a local data file and summarize growth drivers
Research a market and generate a presentation deck
Open an ads dashboard daily, check spend/conversion anomalies, and summarize causes
Turn a folder of resumes into a screening sheet against a job description
Set up scheduled tasks like a daily news digest at a fixed time

Supported clients

Supported clients have not been confirmed yet.