Mu packages everyday internet capabilities behind one MCP endpoint for agents

Introduction

Mu, a project surfaced on Hacker News, presents itself as a tool layer for AI agents. Instead of wiring an agent to separate servers for web search, news, mail, weather, files, calendar and contacts, Mu puts these capabilities behind one MCP endpoint. The project lists 67 tools and offers both a hosted instance at micro.mu and a self-hosted version based on the same Go binary.

Key points

• One MCP endpoint for many tools: An agent can point to https://micro.mu/mcp and access capabilities such as web search, page fetching, news, markets, weather, places, video, mail, storage, files, calendar, contacts, image generation and search, publishing, app building and more.
• “Real tools,” not only wrappers: Mu emphasizes that it runs several components itself, including an SMTP mail server with DKIM, a feed aggregator, a search index, an app sandbox and a wallet. In that model, mail_inbox reads an actual inbox and db_create writes to real storage.
• Multiple surfaces from one registry: The same service declarations can appear over MCP, inside the built-in agent, in the custom agent tool picker, as CLI subcommands and through the app SDK. Adding a service is intended to update these surfaces without repeated integration work.
• Authentication and usage costs: MCP clients that support the authorization spec can sign in through the instance’s authorization server. Other clients may use a Personal Access Token. Reading the instance’s own content is included, while calls that require a model or paid third-party service draw from the user’s balance.
• Open source and self-hostable: Mu is released under AGPL-3.0. Operators can run their own instance, configure an AI provider such as Claude, Atlas Cloud, or a local OpenAI-compatible endpoint, and manage environment settings for search, weather, mail, Google sign-in and other services.

Why it matters

Mu points to a broader shift in agent infrastructure: tool access is moving from scattered API glue toward a service surface that is discoverable, authenticated, metered and potentially self-hosted. MCP provides the common protocol boundary, while Mu’s registry-driven architecture tries to keep the Web app, CLI, agent tools and app SDK aligned.

For developers, the appeal is practical. A working agent often needs more than a chat model: it needs to search, read, store files, send mail, check schedules and act across user-owned data. Mu bundles these everyday internet functions into a single operational layer, making it closer to a personal internet workspace for agents than a narrow tool catalog.

The same scope also raises the stakes. Mail, contacts, files and calendar data are sensitive, and tools that let an agent act on behalf of a user require careful authorization boundaries, auditability and cost controls. Mu’s open-source and self-hosted options give teams room to inspect and adapt the system, but production use would still require serious security and permission design.

Source: Hacker News