Miss Blue : dedicated business messaging with project-scoped tools

One capability list, two interfaces

The documentation describes mb as the terminal interface and mb mcp as the model-facing interface to the same capabilities. Sending, reading threads, inspecting delivery state and managing webhooks appear in the published list. This helps a team inspect the available actions before connecting an assistant.

The API key restricts access to its project. Device login can instead cover selected workspaces or projects; a workspace grant includes projects added later. Those are different scopes, and the latter deserves deliberate review.

Choose the credential before the client

A project key is the clearer starting point for a narrowly assigned worker. Person-level activity reports require a signed-in person rather than a project key, according to the CLI reference. Do not grant broad account access simply to make every advertised tool work.

The current reference says mb logout deletes the local saved token but does not yet revoke the session on the server. A team should have a credential response plan and ask the provider about revocation before distributing logins.

A business line is still a real sender

MCP makes actions available; it does not establish that an agent should execute them automatically. Add recipient checks and an approval boundary in the client or application, especially for a first outbound message.

The free sandbox and paid dedicated line serve different stages. Confirm actual line selection, message direction and handoff to an operator before leaving test traffic.

The decision in one sentence

Choose Miss Blue when dedicated business messaging with project-scoped tools matches the task and its documented limits fit your client.