smbCloud Mail & Auth

io.github.smbcloudXYZPublished by GitHub account smbcloudXYZv1.1.0Updated Oct 31, 2026

Email infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

smbCloud CLI exposes smbCloud mail, auth, deploy and GresIQ operations to an assistant, over a remote endpoint or a local stdio process.

What you can do
  • Send mail through the smbCloud mail app using an API key
  • Manage email infrastructure: domains, inbox routes and auth apps
  • Run deploys and other smbCloud account operations from the same account
  • Optionally expose mobile and TV automation tools (Xcode, ControlKit, CoreDevice, adb) with the automation scope
  • Mirror the same operations available through the REST API and the smb command line
When to use it
Useful when you already work with smbCloud for email infrastructure, authentication or deploys and want an assistant to run those operations without a browser, or when you want the same commands in a terminal, a CI job and an agent.
Requirements
Either the remote endpoint or a local install (npm package run with npx, or the .NET package run with dnx; also Homebrew, Cargo, pip, shell and prebuilt binaries). OAuth login is required; the mail_send tool additionally needs the SMB_MAIL_API_KEY secret, while other tools use the session from smb login.
Before you install
OAuth login and an API key are required, and the key is a secret that should be kept out of logs and shared configs. Tools can send email and run deploys, which change real account state. The automation scope adds device tooling for mobile and TV platforms.

Installation

In SourceWeft

  1. Open smbCloud Mail & Auth in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.smbcloudXYZ%2Fsmbcloud-cli/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "smbcloud-mail-auth": {
      "type": "http",
      "url": "https://api.smbcloud.xyz/v1/mcp"
    }
  }
}

README

[smbCloud Logo]

smbCloud CLI

smbCloud Mail, Auth, Deploy and GresIQ from your terminal, your scripts and your agents.

[Crates.io] [npm] [NuGet] [Homebrew] [PyPI] [MCP server] [CI] [Apache-2.0 License]

Every smbCloud capability works without a browser. You reach it through the REST API first, then through smb, then through its MCP server, and each one covers the same operations. smb is one binary with no runtime to install, so a person at a terminal, a CI job and an AI agent all run the same commands against the same account.

Install

sh
brew tap smbcloudXYZ/tap && brew trust --tap smbcloudXYZ/tap && brew install clinpm install -g @smbcloud/clicargo install smbcloud-cli

More ways, including .NET, pip, shell, PowerShell and pre-built binaries, are in docs/install.md.

Use it your way

  • In the terminal. smb login && smb init && smb deploy takes you from a fresh login to a first deploy. See interfaces.
  • In scripts and CI. smb --ci turns off prompts, so a missing answer fails fast instead of hanging. See CI mode.
  • With AI agents. smb --mcp serves the Model Context Protocol over stdio, and it is listed in the MCP Registry as io.github.smbcloudXYZ/smbcloud-cli. See MCP.
  • For mobile and TV automation. smb --mcp --scope automation exposes Xcode, ControlKit, CoreDevice and adb tools. See ControlKit.

Docs

Install, interfaces, CI, MCP, MCP Registry, ControlKit, AndroidKit, development. The index is docs/README.md.

Contributing

Read CONTRIBUTING.md to get started. Contributions are welcome.

License

Apache-2.0

Copyright

© 2026 Seto Elkahfi (smbCloud). Distributed by Splitfire AB.

Source: README.MD at commit e3fde5c

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

4
  1. v1.1.0LatestOct 31, 2026
  2. v1.0.0Oct 31, 2026
  3. v0.7.5Oct 20, 2026
  4. v0.5.2Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.