Glonce

Mu bundles 67 real internet services behind one MCP endpoint

toolsThe Glonce editorsHacker News🔥65Glonce rating65Impact60Novelty65Relevance85Surprise50Players55Credibility85
Mu bundles 67 real internet services behind one MCP endpoint

A Show HN post by GitHub user asim introduces Mu, a project that exposes 67 tools behind one MCP endpoint: news, web search, mail, markets, weather, video, places, images, files, calendar and contacts. Connecting once gives an agent all 67, instead of an operator wiring up a separate server for each capability.

The project's central claim is that these are real tools rather than thin wrappers over someone else's API. Mu runs its own mail server (SMTP with DKIM), feed aggregator, search index, app sandbox and wallet. The README states that mail_inbox reads a real inbox and db_create writes to real storage, framing the tools as the instance's own capabilities rather than a catalogue of other products.

The same product ships two ways: hosted at micro.mu, or self-hosted as a single Go binary, open source under AGPL-3.0. Setup for the hosted version needs no pasted API key: the first MCP call returns a 401 pointing at the instance's own authorization server, and the client walks the user through sign-in while keeping the token itself. The README says this follows the MCP authorization spec, which Claude Desktop and Cursor both already support; a client that does not can instead generate a Personal Access Token and send it as a Bearer header.

Architecturally, each capability area is a service, a Go package with typed handlers registered in-process behind a Go Micro registry, described as the single source of truth: a service declares itself once and the declaration surfaces everywhere, MCP, the built-in agent, custom agents in a tool picker, the CLI, and apps via an SDK call. The README frames this as making extension a matter of adding one element rather than wiring N separate integrations.

Account-scoped tools, mail, storage, index, images, events, files and contacts, require a signed-in caller, and mail_send always does, which the project says stops an unaccountable caller from spending a domain's reputation. Calls that cost the operator money to run, a model call or a paid third party, draw credits from the caller's balance; the README does not state pricing figures in the text itself, only that per-call costs are browsable on the site. An LLM, Claude, Atlas Cloud (DeepSeek), or a local Ollama or OpenAI-compatible endpoint, calls the services as tools, composes answers, and keeps per-user memory across sessions. Sign-in supports username and password, a passkey (WebAuthn), or Google. The agent is also reachable from Discord and Telegram for questions, markets and news. Running a self-hosted instance makes the operator the one who gets paid when others call the tools.

Key facts

  • Mu exposes 67 tools, covering news, web search, mail, markets, weather, video, places, images, files, calendar and contacts, behind a single MCP endpoint.
  • The project runs its own infrastructure (mail server with DKIM, feed aggregator, search index, app sandbox, wallet) rather than wrapping third-party APIs.
  • It ships as the same product either hosted at micro.mu or self-hosted as one Go binary, open source under AGPL-3.0.
  • MCP setup needs no pasted API key: a 401 on the first call triggers sign-in via the MCP authorization spec, which Claude Desktop and Cursor already support.
  • Account-scoped tools like mail_send require a signed-in caller, and paid calls (model calls, paid third parties) draw credits from the caller's balance.

Why it matters

Most agent tool integrations mean wiring up a separate MCP server per service. Mu's pitch is consolidation: one endpoint, 67 tools, backed by infrastructure the project actually operates (its own mail server, search index, feed aggregator) rather than a set of API wrappers relabeled as tools. It also builds in an authorization flow, the MCP authorization spec, so a client like Claude Desktop or Cursor can sign a user in without an API key ever being pasted into a config file.

Who it affects

Developers building or configuring agents that need broad internet access, mail, search, calendar, market data, and similar, without standing up a separate integration for each one. It also affects anyone who chooses to self-host: the README states that running your own instance makes you the operator, and anyone paying to call the tools pays you.

How to use it

Add the hosted MCP endpoint (https://micro.mu/mcp) to a client such as Claude Desktop or Cursor; the first call returns a 401 that starts sign-in, and the client keeps the resulting token. Clients without MCP authorization support can generate a Personal Access Token at /token and send it as a Bearer header. Every tool is also a CLI subcommand under the mu binary, which can run the full server (mu --serve) or be self-hosted via a shell install script, Docker Compose, or building from source with go install. Self-hosting requires configuring an AI provider (Claude, Atlas Cloud, or a local Ollama or OpenAI-compatible endpoint) during a one-time admin setup. The text does not state dollar pricing for hosted use; it says costs per call are browsable at micro.mu/tools, and that calls costing the operator money draw credits from the caller's balance.

How solid is it

The claims come from the project's own README on a Show HN post, not from independent testing or third-party review. The architectural description, a Go Micro registry where each service self-declares and surfaces automatically to MCP, the CLI, the built-in agent and an SDK, is specific and includes a code sample, which supports the claim that the tools are integrated into one binary rather than assembled from external wrappers. At the time of this dossier the post had 47 points and 14 comments on Hacker News, indicating early-stage community attention rather than established, widespread adoption.

Risks and caveats

The source is the project's own documentation, so claims about running "real" infrastructure rather than wrappers, and about security properties like unaccountable callers being unable to send mail, are the project's self-description and have not been independently verified here. No pricing tiers, user counts, funding, or team information appear in the text. AGPL-3.0 licensing means a modified self-hosted version run as a service must have its source shared, a real obligation for anyone who forks and redistributes it.

“Real tools, not wrappers. Most things offering an agent tools are a thin layer over somebody else's API. Mu runs the mail server (SMTP with DKIM), the feed aggregator, the search index, the app sandbox and the wallet it hands you.”

— Mu project README