micro/mu

mu

Tools for agents. News, mail, search, weather, markets, video, places, files, contacts, calendar and your own documents, as tools an agent can use via one MCP server and token — also includes a web app for humans.

Install

curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh
mu --serve

Open http://localhost:8080. The first account you create is the admin.

It runs with no configuration. A few things need an API key.

Follow setup in CLI

mu setup        # pick an AI provider, paste a key
mu --serve

Everything else — mail and DKIM, Google sign-in, Stripe, x402 — is optional, and configurable from /admin/env once you are signed in as admin.

Other ways to run it:

# Docker
git clone https://github.com/micro/mu && cd mu
docker compose up

# From source
git clone https://github.com/micro/mu
cd mu && go install
mu --serve

See the installation guide.

Connect an agent

Cursor, and clients with a config file. Create a token at /token:

{
  "mcpServers": {
    "mu": {
      "url": "https://micro.mu/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MU_TOKEN}"
      }
    }
  }
}

Claude Desktop. Settings → Connectors → Add custom connector, and paste https://micro.mu/mcp. It registers itself, opens a browser and asks you to sign in — no token needed. Pasting the URL into claude_desktop_config.json will not work: that file only takes local command-line servers.

Anything else. It is JSON-RPC over HTTP POST:

curl -X POST https://micro.mu/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Scope the connection to the services you need:

https://micro.mu/mcp?tools=news,web,mail

See micro.mu/tools for all the tools. See Help for the protocol.

Tools

Here are the tools

Open an issue to request a tool.

App

The server includes a web app. A home screen renders each service at a glance — headlines, prices, weather, unread mail — and the agent sits inline to act on what you are looking at. Apps run sandboxed, in an opaque origin, and reach the platform through a fixed set of operations rather than your session.

Sign in with a username and password, a passkey (WebAuthn), or Google.

CLI

Every tool is a mu subcommand. The same binary runs the server (mu --serve) and the CLI.

mu news list                            # latest headlines
mu news search "ai safety"              # search news
mu web search "claude code"             # search the web
mu markets list --category stocks       # live prices
mu agent "what is the btc price?"       # run the full agent
mu weather forecast --lat 51.5 --lon -0.12
mu docs list --collection notes         # your own documents
mu x402                                 # paying per call: config, and your key
mu help                                 # full tool list

Every tool in the table above 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.

The CLI is registry-driven — a tool added to the server automatically becomes a CLI command.

mu login                  # opens /token in your browser, paste the PAT back
mu config set token xxx   # or set it directly
export MU_TOKEN=xxx       # or use the environment

Run mu --help for the list — it reads the same catalogue the agent does.

Agent

The same binary is also an agent. mu agent brings your own model and your own wallet, reads its tools from a running instance, and pays per call — no account on that instance and no signup.

# 1. A model. The tools are rented; the thinking is yours.
export ANTHROPIC_API_KEY=sk-ant-...     # or OPENROUTER_API_KEY
                                        # or OPENAI_BASE_URL for Ollama etc.

# 2. A wallet. Created for you on first run, or make it yourself:
mu x402 key new                         # prints an address; send USDC on Base
                                        # to it. No ETH — you never pay gas.

# 3. Ask.
mu agent                                # a conversation
mu agent "what happened in markets today?"

model: anthropic/claude-sonnet-4-6
117 tools from https://micro.mu
wallet: 0x4160a863… (1.27 USDC)

> what are the top news headlines today?
· news_list
…
> of those, which matters most for markets?
… answered with no tool call, and no charge

Reading the catalogue is free, so it works before the wallet holds anything — only priced tools need funds. What a run spent is read back off the chain when it ends, not totted up from what the agent believes it authorised.

--server points it at any x402 instance; a name from X402_SERVERS works too. --seed uses a different key.

Discord & Telegram

Talk to the agent from Discord or Telegram — questions, markets, news, all from chat. Join the Discord

Every tool is a command on both, in the same two-word shape as the CLI: /news list, /markets list category:stocks, /prayer times. Discord gets one slash command per service with the methods as subcommands; on Telegram you type /news list. Both also take /agent <question> for anything that needs composing, and /usage for your own stats.

Setup for both is in Install.

Credits & Payments

A person tops up by card and spends one credit balance. A credit is 1p.

An agent can pay with USDC over x402 and never sign up. A priced call with no credentials answers 402 Payment Required naming the price and where to send it. The payment is the identity.

To write an agent that pays, see examples/x402-agent — a standalone module that imports none of this. It uses the x402 Foundation SDK, so the same file pays any x402 server.

To watch it work, mu is its own client too. Put a funded Base wallet's key in ~/.mu/keys/wallet.seed:

mu x402 call web_search query="x402"   # 402 → signs → pays → returns the result

Self-host with neither Stripe nor x402 and nothing is metered: every tool is free.

Configuration

Customise feeds, prompts and cards by editing JSON files:

• service/news/feeds.json — RSS news feeds
• service/chat/prompts.json — chat topics
• home/cards.json — home screen cards
• service/video/channels.json — YouTube channels
• service/places/locations.json — saved locations

See Install for every setting the code reads.

Documentation

Three pages, and they are the site's: About, Help for connecting an agent, and Install for running your own. The live tool catalogue is at /tools — it is generated from what the instance runs, so it cannot go stale.

For the code, Architecture.

License

AGPL 3.0