Document Homebrew CLI install

cli/index.mdx

@@ -1,11 +1,12 @@
 ---
 title: "CLI"
 description: "Install and configure the Sendmux CLI for management, mailbox, and sending workflows."
 keywords:
   [
     "Sendmux CLI",
     "@sendmux/cli",
     "sendmux",
+    "Homebrew",
     "profiles",
     "Management API",
     "Mailbox API",
@@ -13,7 +14,7 @@
   ]
 ---
 
 Use the `sendmux` CLI when you want terminal access to the same Management, Mailbox, and Sending API surfaces exposed by the SDKs.
 
 <Info>
   Sending and Mailbox commands require mailbox-scoped `smx_mbx_` keys.
@@ -22,7 +23,13 @@
 
 ## Install
 
-Install the CLI from npm.
+Install the CLI with Homebrew on macOS or Linux.
+
+```bash
+brew install sendmux/tap/sendmux
+```
+
+You can also install it from npm.
 
 ```bash
 npm install -g @sendmux/cli

guides/mcp.mdx

@@ -1,6 +1,6 @@
 ---
 title: "MCP"
 description: "Connect AI tools to Sendmux documentation and product tools."
 keywords:
   [
     "MCP",
@@ -11,16 +11,16 @@
   ]
 ---
 
 Sendmux has two MCP connections. Use Documentation MCP when you want an AI tool to search Sendmux docs. Use Product MCP when you want an agent to work with Sendmux tools you authorise.
 
 | Connection | Use it for | Server |
 | --- | --- | --- |
 | Documentation MCP | Search Sendmux guides and API references. | `https://sendmux.ai/docs/mcp` |
 | Product MCP | Use Management, Mailbox, and Sending tools. | `https://mcp.sendmux.ai/mcp` or the local `sendmux-mcp` package |
 
 <Info>
   Product MCP exposes a curated agent toolset, not every API endpoint. Use the
   SDKs, CLI, or API reference when you need full endpoint coverage.
 </Info>
 
 ## Documentation MCP
@@ -30,7 +30,7 @@
 <AccordionGroup>
   <Accordion title="Claude Code" description="Add the docs server over HTTP.">
     ```bash
     claude mcp add sendmux-docs --transport http https://sendmux.ai/docs/mcp
     ```
   </Accordion>
 
@@ -83,7 +83,7 @@
 | Management | Manage team resources such as domains, mailboxes, sending accounts, logs, metrics, billing, and webhooks. | Hosted grant with Management access, or an `smx_root_` key locally |
 | Sending | Send single or batch emails. | Hosted grant with Sending access, or an `smx_mbx_` key locally |
 
 Hosted Product MCP is the default when your client supports remote MCP with browser OAuth. It keeps Sendmux in the authorisation flow, avoids distributing manual API keys to agents, and shows only the tools allowed by the grant.
 
 | Setting | Value |
 | --- | --- |
@@ -91,7 +91,7 @@
 | Authorisation server | `https://app.sendmux.ai` |
 | Health check | `https://mcp.sendmux.ai/health` |
 
 When you connect, Sendmux asks you to choose a team, product surfaces, and mailbox access where relevant. Access tokens are short-lived. Refresh tokens rotate on use and can last up to 30 days unless the connection is disconnected or expires.
 
 <Note>
   If you grant more than one mailbox, start mailbox workflows with
@@ -178,9 +178,9 @@
     ```bash
     sendmux-mcp \
       --surfaces mailbox,management,sending \
       --mailbox-api-key smx_mbx_... \
       --management-api-key smx_root_... \
       --sending-api-key smx_mbx_...
     ```
   </Accordion>
 </AccordionGroup>
@@ -221,13 +221,13 @@
 
 <CardGroup cols={2}>
   <Card title="MCP clients" icon="plug" href="/guides/mcp-clients">
     Configure Sendmux MCP in Claude Code, Cursor, Codex, Gemini CLI, Qwen Code, Zed, and more.
   </Card>
   <Card title="SDKs" icon="code" href="/sdks">
     Use package-managed clients from application code.
   </Card>
   <Card title="CLI" icon="terminal" href="/cli">
-    Run the same product surfaces from your terminal.
+    Install the CLI with Homebrew or npm when you need terminal access.
   </Card>
   <Card title="API keys" icon="key" href="/guides/api-keys">
     Create scoped credentials for local MCP setups.

sdks/index.mdx

@@ -1,7 +1,7 @@
 ---
 title: "SDKs"
 sidebarTitle: "Overview"
 description: "Choose a Sendmux SDK package and the API surface it should use."
 keywords:
   [
     "SDKs",
@@ -16,12 +16,12 @@
   ]
 ---
 
 Sendmux SDKs give your application package-managed clients for the Sending, Mailbox, and Management APIs.
 
 Use an umbrella package when one application needs more than one API surface. Use a surface package when you want a smaller dependency for one job.
 
 <Info>
   Create the API key in Sendmux before you install a package. Sending and
   Mailbox clients use mailbox-scoped `smx_mbx_` keys. Management clients use
   team-scoped `smx_root_` keys.
 </Info>
@@ -40,7 +40,7 @@
 | --- | --- | --- |
 | TypeScript | `@sendmux/sdk` | `@sendmux/sending`, `@sendmux/mailbox`, `@sendmux/management` |
 | Python | `sendmux-sdk` | `sendmux-sending`, `sendmux-mailbox`, `sendmux-management` |
 | Go | `sendmux.ai/go` | `sending`, `mailbox`, `management`, and `sdk` subpackages |
 | PHP | `sendmux/sdk` | `sendmux/sending`, `sendmux/mailbox`, `sendmux/management` |
 | Ruby | `sendmux-sdk` | `sendmux-sending`, `sendmux-mailbox`, `sendmux-management` |
 
@@ -48,10 +48,10 @@
 
 <CardGroup cols={2}>
   <Card title="CLI" icon="terminal" href="/cli">
-    Run Sendmux management, mailbox, and sending commands from your terminal.
+    Install the Sendmux CLI with Homebrew or npm for terminal workflows.
   </Card>
   <Card title="MCP servers" icon="plug" href="/guides/mcp">
     Connect AI tools to Sendmux docs and authorised product tools.
   </Card>
 </CardGroup>