Mu

What mu does

mu runs Micro, an open personal assistant built around agents, tools, and connected services. The default Micro agent receives a requested outcome and selects tools from services such as mail, files, calendar, search, weather, notes, and shell. News aggregation, RSS headlines and summaries, and YouTube video search are also available as services.

The system brings those capabilities together through one MCP interface. The listed coverage includes news, web search, mail, markets, weather, places, files, calendar, and contacts, with 67 tools exposed through a single endpoint. Services can be used by agents or browsed directly, including a complete mail client and server.

How it works

A local mu process provides the web application and runtime. After starting it, open the local address to create an account and select an AI provider. The Home area provides a place to prompt the assistant and view activity, while its Feed tab presents news and world events.

Messages from different channels arrive in the Inbox. HTTP can start or reopen a conversation, SMTP accepts mail sent to the agent address from a verified email account, and SMS requires a verified phone number. XMPP access uses an account and a Chat token from Client access. The runtime also supports WhatsApp and SMS through Twilio.

The command-line binary can send prompts, inspect the inbox, and display help. The agent API accepts a prompt with bearer authentication and returns both text and a thread identifier, which can be supplied to continue the conversation.

Setup and configuration

Install the binary with the project’s shell installer, then start the local service with an address such as 127.0.0.1:8080:

curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh
~/.local/bin/mu --serve --address 127.0.0.1:8080

The command-line client defaults to the hosted instance. Set MU_URL to target another host or run mu login https://your.host to configure one. API calls use MU_URL and MU_TOKEN, with the token sent as a bearer credential. A separately configured x402 host handles paid service calls.

Tools and capabilities

• Agent conversations and threaded follow-ups
• Mail, files, calendar, contacts, notes, and shell services
• Web search, news and RSS aggregation, weather, markets, places, and video search
• Web Home and Inbox views
• SMTP, HTTP, SMS, XMPP, and WhatsApp communication paths

Limitations and notes

Account creation and AI-provider selection happen through the web interface after startup. SMS requires phone verification, while SMTP requires a verified sender address. XMPP requires both an account and a Chat token. Credentials and prompts for direct API requests belong in request headers and bodies.