The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Mu listing page.
Tools for agents.
Mu is an open-source runtime for agents, tools and services.
It includes Micro, a personal assistant that has access to all the tools and services.
Mu is a monolothic codebase: the runtime, services, archive, inbox and agent system all in one host. Services operate as building blocks for agents — mail, chat, news, video, search, markets, weather and more. Data gets archived locally so it stays searchable and becomes contextual memory. Services and the archive become tools for Micro and any other agents you create.
Micro is the first agent and the one you use for everything. It answers by default and can be reached from the web, email, SMS, WhatsApp or the CLI.
Mu comes with a unified inbox for mail, chat, SMS, WhatsApp, notes, tasks and agent activity, bringing communication and agent work into one place.
What's included:
Mu is the runtime. Micro is the first agent and the one people meet first.
Your own agents are the same shape: a name, an instruction, and the tools they may reach. Each has an address, so agent+yours@ reaches it from anywhere that can send mail, the same way agent@ reaches Micro.
Quick install guide for self hosting (let us know if it's broken).
Open http://localhost:8080. The first account you create is the admin.
Quite a few things need API keys, but here's some must haves.
| For | Set | Notes |
|---|---|---|
| AI models | ANTHROPIC_API_KEY, ATLASCLOUD_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY, or OPENAI_BASE_URL | free if you run Ollama locally |
| Web search | BRAVE_API_KEY | Brave has a free tier |
| Video | YOUTUBE_API_KEY | free quota |
Follow setup in CLI
Everything else — mail, Google sign-in, Stripe for payments, etc — is optional.
The binary is a client, and by default it calls https://micro.mu — the hosted Mu instance where Micro runs publicly. Running your own? Point it there:
Without that, mu news list on the machine you just installed calls the hosted instance rather than the one you are running. MU_URL and --url override per shell and per command.
Other ways to run it:
See the installation guide.
Every service is a mu subcommand
Every tool is a command: the service, then the method. The underscore form works too, so mu news list and mu news_list are the same call.
To authenticate
Run mu --help for the list — it reads the same catalogue the agent does.
To talk to Micro instead, use mu ask — it runs on the instance, so it needs your token and no model key of your own:
mu agent is the other direction and easy to reach for by mistake: it runs the agent here, on your machine, with your own model key, renting tools from an instance over x402 and paying per call. Same word in English, opposite ways round.
Every service has a HTTP endpoint, at /api/v1/<service>/<method>.
Authenticate with a token from /token as Authorization: Bearer, or with an OAuth client. A priced endpoint answers 402 without one, which an x402 client pays per call with no account at all.
For Tools via MCP use /mcp. See /tools for more info.
/ - talk to Micro/home — an overview of everything going on./inbox — the place to see chats, mail, tasks, etc./agents — your agents, and where you make a new one./services — /news, /weather, /markets, etc.Some files are embedded in the binary, so editing means rebuilding:
home/cards.json — home screen cardsservice/news/feeds.json — RSS news feedsservice/chat/prompts.json — chat topicsservice/video/channels.json — YouTube channelsservice/places/locations.json — saved locationsSee Install for every setting the code reads.
The rest lives in /admin/config on the server.
AGPL 3.0