Provides web search via the Brave Search API, enabling agents to search the web and fetch clean page text.
Allows interaction with the agent from Discord via commands like /agent, /news, /markets, /weather, and more.
Allows sign-in with Google OAuth, providing authentication for the web app.
Can use local Ollama models as the AI provider for the agent, enabling private and offline operation.
Can use OpenAI or any OpenAI-compatible endpoint as the AI provider for the agent.
Aggregates news from RSS feeds, providing tools to list, read, and search articles across configured feeds.
Allows interaction with the agent from Telegram via commands like /agent, /ask, /news, and more.
Supports passkey/WebAuthn authentication for passwordless sign-in.
Provides video search and listing from curated YouTube channels, without ads or recommendations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mu what's the weather in San Francisco?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The runtime for Micro, a personal assistant.
A place to view and do things e.g prompt, see what's happening, etc.
Related MCP server: hidrix-tools
Connect from various places and it all goes in one inbox.
Protocol | Info |
HTTP | Start a conversation or reopen one from Inbox. |
SMTP | Send a message to |
SMS | Verify your phone number in Account, then text the configured number. |
XMPP | Connect with your account and a Chat token from Client access, then message the agent. |
Micro is the default agent. Agents have instructions and a set of tools. Services provide those tools: mail, files, calendar, search, weather, notes, shell, and more. You ask for an outcome; the agent chooses the tools.
Work can run in the background and return its result to the originating conversation. Task records live in service/tasks. Agents own the daily brief and delivery logic, while service/events schedules it and Work tracks each occurrence.
Complete standalone services that agents can use as tools or you can browse with. For example a complete Mail client and server. Web search via brave. News aggregation, headlines and summary via RSS. Video search via YouTube. All behind one MCP interface.
curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh
mu setup
mu --serveOpen http://localhost:8080. Initial administrator setup depends on the instance's bootstrap configuration; see the installation guide.
Configure an AI provider with mu setup, or use the settings below.
From source:
git clone https://github.com/micro/mu
cd mu
go install
mu setup
mu --serveOr run docker compose up from the checkout. See the
installation guide for domains, TLS, mail, messaging,
sandbox configuration, and deployment.
The binary acts as a client. It defaults to the hosted instance; set
MU_URL or use mu login https://your.host for your own server.
mu ask "What needs my attention?"
mu inbox list
mu helpcurl "$MU_URL/agent" \
-H "Authorization: Bearer $MU_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"prompt":"What needs my attention?"}'The response includes text and thread; send the thread identifier
back to continue. Requests and credentials belong in request bodies and headers.
A separately configured x402 host provides paid service calls.
This server cannot be deployed
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Pocket Agent (aipocketagent.com) MCP server — read tools for personas, apps, and product info.
Hosted MCP server for live public-data APIs and Skills for AI agents.
Your agent needs live data — a competitor's traffic, who to contact there, what people are saying, what Google and ChatGPT answer about you, a company's filings. Normally that is six vendor accounts, six sets of keys and six SDKs. This is one URL. **What you can ask for** • "How much traffic does stripe.com get, where does it come from, and who competes for the same keywords?" • "Find 20 Series-B fintech companies in Germany and the heads of marketing there, with emails." • "Does ChatGPT mention our brand when someone asks for the best CRM — and what does it cite?" • "What is X saying about $NVDA today, and what did the stock actually do?" • "Search the web for this, then scrape the three best pages into markdown." **How to use it** Point any MCP client at https://mcp.aisa.one/mcp and sign in with OAuth — there is no key to create or paste. Then just ask: the agent calls search to find the right operation and use to run it. **Why this rather than the source** 26 sources behind one account and one bill — DataForSEO, Semrush, Ahrefs, Similarweb, Apollo, X/Twitter, Instagram, Reddit, Pinterest, YouTube, Tavily, Exa, Perplexity, Firecrawl, CoinGecko, Kalshi, Polymarket, AgentMail and more, 580+ operations. tools/list returns five tools, not 580, so the introduction does not eat your context window. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** One slice at a time: https://mcp.aisa.one/seo/mcp · /finance/mcp · /social/mcp · /search/mcp · /sales/mcp · /mail/mcp · /gtm/mcp, or a single provider like /twitter-api/mcp. Same account, fewer tools listed, and search still reaches everything. Full list at https://mcp.aisa.one/servers
