Setup Unbo with OpenClaw

OpenClaw is an MCP-native agent runtime. Because Unbo speaks the same Model Context Protocol, connecting the two is almost entirely configuration — no custom integration code, and no IMAP credentials ever leave Unbo.

Pick an inbox

Choose the inbox OpenClaw should monitor — for example support@yourdomain.com. If you don’t have one yet, create it under Inboxes → New.

Grab the MCP endpoint

Every Unbo inbox is reachable through one MCP server. OpenClaw negotiates a scoped token over OAuth2 during connection, so there’s nothing to paste but the endpoint:

https://mcp.unbo.dev

Declare the tool

OpenClaw is configured in TOML. Add Unbo as a tool in your openclaw.toml, requesting read-only scopes.

openclaw.toml

[tools.unbo]
type = "mcp"
transport = "http"
url = "https://mcp.unbo.dev"

[tools.unbo.auth]
type = "oauth2"
scopes = ["inbox.read", "email.read"]

Connect and authorize

Run the connect command. OpenClaw opens Unbo’s consent screen; approve the scopes and the token is stored in your workspace credential store.

terminal

# Register Unbo with your OpenClaw workspace
openclaw connect unbo --url https://mcp.unbo.dev

# OpenClaw opens the OAuth consent flow in your browser and
# caches the granted token in its workspace credential store.

Test it

Ask OpenClaw something that requires reading the inbox:

terminal

openclaw ask "Summarise the unread emails in my support inbox
and flag anything that looks urgent."

OpenClaw

You have 5 unread messages in support@yourdomain.com. I’d flag one as urgent: a customer reporting a failed payout referencing invoice INV-2231. The rest are routine onboarding questions. Want me to draft a reply to the urgent one?

If OpenClaw answers from your live inbox like this, the connection is working. 🎉