| 1 | # smbCloud MCP server |
| 2 | |
| 3 | Gives the agent access to your smbCloud account: mail domains and inbox routes, |
| 4 | auth apps, projects, tenants, and deploys. |
| 5 | |
| 6 | ## 1. Sign in |
| 7 | |
| 8 | The server reuses the session that the `smb` CLI stores on disk, so sign in once |
| 9 | from a terminal: |
| 10 | |
| 11 | ```sh |
| 12 | npx -y @smbcloud/cli login |
| 13 | ``` |
| 14 | |
| 15 | Any tool other than `mail_send` works off that session. Nothing else to configure. |
| 16 | |
| 17 | ## 2. Optional: a mail API key |
| 18 | |
| 19 | `mail_send` sends real email, so it needs a Mail app API key rather than your |
| 20 | user session. Create one in the smbCloud dashboard and put it in the settings |
| 21 | below as `mail_api_key` — it is passed to the server as `SMB_MAIL_API_KEY`. |
| 22 | |
| 23 | ## Settings |
| 24 | |
| 25 | - `scope` — which tool profile to expose. `cloud` (default) serves smbCloud |
| 26 | resources; `automation` serves the mobile and TV device tools instead. |
| 27 | - `environment` — `production` (default) or `dev`. |
| 28 | - `mail_api_key` — the `smb_mail_...` key described above. |
| 29 | |
| 30 | If you already have `smb` installed natively (Homebrew, cargo, or the install |
| 31 | script), set `command.path` to its location and the extension will use that |
| 32 | binary instead of downloading the npm package. |