What is it?
What it is
mu is an open‑source platform that bundles over 30 real‑world services (mail, chat, news, video, markets, etc.) into a single, searchable archive. It lets you define agents—named AI assistants with custom prompts and tool permissions—communicate via web, email, XMPP, SMS, or CLI, and keep a unified inbox for all incoming threads.
Why it exists
To provide a ready‑to‑use, self‑hostable toolkit where agents can operate without code or deployment. By centralising services, archiving their data, and exposing them as interchangeable tools, mu lets users ask cross‑service questions, build tiny web apps, run shell commands, and interact with agents from any client, all while keeping data locally searchable and private.
Who should use it
Developers building AI agents who need a unified set of tools and servicesUsers wanting a self-hosted AI agent platform with privacy controlOrganizations looking to deploy their own agent infrastructure on-premiseDevelopers integrating AI capabilities via MCP (Model Context Protocol)Users wanting a unified inbox for email, chat, SMS, and agent conversationsSelf-hosted enthusiasts comfortable with Docker and CLI toolingTeams needing customizable AI agents with granular tool access control
Who should avoid it
Non-technical users seeking a plug-and-play managed solutionOrganizations unwilling to comply with AGPL-3.0 open-source license requirementsUsers wanting zero-configuration setup with no API key managementThose requiring enterprise support contracts and SLA guaranteesCasual users who prefer managed SaaS over self-hosted infrastructure
Stars over time
No change stars in the last 1 day
How it works
A quick walkthrough in plain English
How mu works in 4 steps
Step 1 of 4
Something triggers the flow
A schedule, webhook, or manual click tells mu to start.
Features
Advantages
- Single platform for multiple communication channels and services
- No-code agent creation - define by name, prompt, and tool selection only
- Multiple access methods: web, CLI, API, MCP, IMAP email client
- Self-hosting option gives full data control
- Cross-service queries supported (Archive search across all services)
- Built-in agents (Micro for general, Code for development)
- Local data archival makes all communications searchable
- Token-based authentication for clients
- x402 payment integration for pay-per-call usage
- Many services work without API keys
- Free hosted instance available at micro.mu
- Configuration via quota.json for custom pricing
- Real-time transit data for London (TfL)
Disadvantages
- AGPL 3.0 license has copyleft requirements for modifications
- Most useful features require paid API keys (Anthropic, OpenRouter, Brave, YouTube)
- Some tools incur costs per use (browser, shell, SMS, text processing)
- Shell tool requires Docker installation
- Geographically limited services (UK: food hygiene, Environment Agency floods, National Rail trains)
- Transit feeds need manual configuration for non-London areas
- Self-hosting requires significant setup and maintenance
- Browser tool is expensive due to Chromium execution
- Privacy considerations when using hosted instance
- SMS service has per-segment pricing with daily caps
- Hosted version may not meet enterprise compliance requirements
Installation
native
curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh mu --serve Or from source: git clone https://github.com/micro/mu cd mu && go install mu --serve
compose
git clone https://github.com/micro/mu && cd mu docker compose up
FAQ
How do I install mu?
Run `curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh` then start the server with `mu --serve`. You can also clone the repo and use Docker (`docker compose up`) or build from source with `go install`.
How do I create a custom agent?
Go to `/agents` on the web, give the agent a name and a standing instruction, and choose which services it may use. Leaving the services list empty grants access to all services you can reach.
How do I authenticate API or CLI calls?
Create a token at `/token`. For HTTP API calls, include the token in the `Authorization` header as `Bearer <token>`. For the CLI, set the `MU_TOKEN` environment variable or run `mu login` and paste the token.
How do I connect mu to an MCP client?
For clients with a config file (e.g., Cursor), add a server entry with URL `https://micro.mu/mcp` and set the `Authorization` header to `Bearer ${env:MU_TOKEN}`. For Claude Desktop, use Settings → Connectors → Add custom connector, paste the same URL, and it will sign in automatically.
How do I pay for priced endpoints?
Priced endpoints return HTTP 402. An x402 client can pay per call without an account. You can also set up a wallet on Base using the `wallet_address` and `wallet_balance` tools; a client pays for a call when it receives a 402.
Featured in Videos
YouTube tutorials and walkthroughs for mu
Alternatives
Similar projects ranked by category, topics, and text overlap.
