Mu MCP
Open runtime for personal assistants with a 67-tool MCP server: news, search, mail, calendar, files and contacts
- 439 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- The connection opens the assistant's mail, calendar, contacts and files to the agent, and some tools send data to external services
- The access token and paid calls through x402 spend credits and give access to the account
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/micro-muDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The connection opens the assistant's mail, calendar, contacts and files to the agent, and some tools send data to external services
- The access token and paid calls through x402 spend credits and give access to the account
This is third-party code. Review the repository files before installing.
What it does
Mu is an open runtime for personal assistants: agents, connected services, accounts, permissions and persistent history gathered in one Go binary. The general-purpose assistant is called Micro, and other agents can have their own instructions and permitted tools. Services supply mail, calendar, contacts, information, media and storage, and agents carry out requests on top of them. The Mu MCP server lives on a single endpoint: on the hosted instance it is `https://micro.mu/mcp`, on your own it is the `/mcp` path. The MCP registry lists 67 tools: news, web search, mail, markets, weather, places, files, calendar and contacts. A client connects with a token and the OAuth issuer address comes from the `MU_DOMAIN` variable. In parallel there is REST at `/api/v1/<service>/<method>`, the `mu ask` CLI and a web console. Paid service calls are possible through a separately configured x402 host.
Who it is for. People who run a personal assistant on their own server and want to open its mail, calendar and files to external agents through one address.
Good fit when
- An agent combines news, weather and upcoming meetings into a morning digest through one connection
- The assistant's mail and contacts have to be read from Claude Code without opening the web console
- Your own Mu instance runs on a home server so data does not go to someone else's host
- One `/mcp` address is needed for several external agents with different permissions
Not a fit when
- A narrow server for a single service is enough: 67 tools behind one address clutter the agent's choice
- The agent must not get access to mail and files: the connection opens those services
- You need a frozen specification: the registry version is 1.0.0 and the project changes actively
Example request
Connect to Mu, show what needs my attention in the inbox and add tomorrow's meetings from the calendar to a short summaryMCP
- Transport
- http
- Authentication
- OAuth
Environment variables
MU_DOMAIN- Public domain for the OAuth issuer MCP clients discover; set when running behind a proxy
Limitations
Documentation of the tool set is brief: the MCP registry names 67 tools and a list of areas, while the full list sits in the server's own discovery and refreshes when the client reconnects. The hosted micro.mu instance takes data from connected services, and with self-hosting model providers and connected services still receive the data needed for the operations you enable. The license is AGPL-3.0 and there is a separate `LICENSING.md` file. Installation goes through a `curl` script followed by running `mu --serve`.
How to disable. Remove the server from the client (`claude mcp remove mu`) and revoke the token in Mu; stop your own instance by closing the `mu` process.
FAQ
What is the Mu MCP server address?
`https://micro.mu/mcp` on the hosted instance and the `/mcp` path on your own host for a self-hosted one. The transport is Streamable HTTP.
How do I install Mu myself?
Run `curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh`, then `~/.local/bin/mu --serve --address 127.0.0.1:8080`. The web console opens where you create an account and pick a model provider.
How do I ask the assistant without MCP?
Through REST: a request to `$MU_URL/agent` with an `Authorization: Bearer $MU_TOKEN` header and a `{"prompt": "..."}` body, or the `mu ask "..."` command.
What does the MU_DOMAIN variable do?
It sets the public domain: the OAuth issuer that MCP clients discover, return URLs and mail depend on it. Set it when Mu runs behind a proxy.
What clients does Mu have?
A web console and PWA, an Android app, a separate React and TypeScript client and the `mu-cli` CLI with `login`, `ask` and `chat` commands.
Discussion
No questions or reviews yet.
Related
MCP serversA local MCP server for Mac and Windows that lets an agent work with mail, messengers, calendars and files.
A Mattermost MCP server: an agent reads, searches and posts messages, threads and files in your workspace, with 39 tools.
The official Kibela MCP server searches, reads and edits notes, folders and comments of your wiki straight from an assistant chat
MCP email server over IMAP and SMTP: an agent searches, reads, sorts and sends mail across several mailboxes
An MCP server that gives the agent access to mail, calendar, OneDrive files and Power Automate flows through Microsoft Graph
An MCP server giving agents a mailbox: send mail, read recent messages, auto setup for QQ, 163, Outlook and enterprise mail.
README in short
The text describes Mu as a runtime for personal assistants with agents, services, accounts and memory, shows a layer diagram with the MUCP protocol and explains the purpose without an ad feed. Next come installation, clients (API, CLI, web, Android) and links to the documentation.