Blooio

com.blooioPublished by blooio.comOfficial publisherv4.1.0Updated Nov 7, 2026

Send and receive iMessage, SMS, RCS, and WhatsApp, and manage contacts, chats, and numbers.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for the Blooio messaging API, letting an assistant send and receive iMessage, SMS, RCS and WhatsApp and manage contacts, chats and numbers.

What you can do
  • Send and receive messages across iMessage, SMS, RCS and WhatsApp
  • Manage channels, phone numbers, contacts, chats and groups
  • Handle calls, 10DLC registration, support tickets, webhooks and the event feed
  • Upload files for group icons, chat backgrounds and contact card avatars from a public URL
  • Read account info, channels and webhooks as resources, with starter prompts for common tasks
When to use it
Useful when an assistant should work inside a Blooio account: sending or checking messages on multiple channels, managing contacts and groups, or setting up webhooks and registrations. Each tool maps to one Blooio v4 API call, so it suits users who already have a Blooio organization.
Requirements
A remote endpoint at mcp.blooio.com; no local install. OAuth sign-in through a browser, choosing the Blooio organization and approving permissions, is required; clients without OAuth support can send a Blooio API key as an Authorization Bearer header instead.
Before you install
Tools act with the connected user's credentials and can send messages, change contacts, chats and groups, and register numbers, so writes reach real recipients. Sign-in grants access to a whole Blooio organization. File uploads take a public URL that the server downloads. Access can be revoked from the organization's installed apps.

Installation

In SourceWeft

  1. Open Blooio 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/com.blooio%2Fmcp/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": {
    "blooio": {
      "type": "http",
      "url": "https://mcp.blooio.com/v4"
    }
  }
}

README

Blooio MCP Server

A Model Context Protocol server for the Blooio v4 API. It lets Claude, ChatGPT, Cursor, and any other MCP client send and receive iMessage, SMS, RCS, and WhatsApp messages, and manage channels, numbers, contacts, chats, groups, calls, 10DLC registration, support tickets, webhooks, and the event feed.

It is a thin wrapper: every tool is one Blooio API call, made with the credentials of the person who connected.

Connect

Add this server URL to your MCP client:

https://mcp.blooio.com/v4

The client opens a browser window where you sign in to Blooio, choose the organization to connect, and approve the permissions. Access tokens refresh automatically; you can revoke access any time from your organization's installed apps in the Blooio dashboard.

If your client can't do OAuth, send a Blooio API key instead:

Authorization: Bearer bl_live_...

Tools

There is one tool per v4 API operation, generated from the published OpenAPI spec, so the tool set always matches the docs. Tool arguments are the operation's:

  • path parameters, in snake_case (/chats/{chatId} takes chat_id)
  • query parameters
  • request body fields, flattened to the top level
  • idempotencyKey, for operations that accept an Idempotency-Key header

Operations that upload a file (set_group_icon, set_chat_background, upload_contact_card_avatar) take a public URL; the server downloads it and uploads it to Blooio.

When a call fails, the API's error comes back as the tool result, so the model can read it and fix the call.

Resources (blooio://account/info, blooio://channels, blooio://webhooks) and a few starter prompts (send_quick_message, check_delivery, send_with_attachment, verify_contact, setup_webhook, start_group_chat) are also available.

How sign-in works

The server is an OAuth 2.1 authorization server for MCP clients: dynamic client registration, authorization code with PKCE (S256), and refresh tokens. It delegates the actual login to Blooio's OAuth:

  1. The MCP client registers at /oauth/register and opens /oauth/authorize.
  2. A confirmation page names the client and where it will be redirected, then hands off to Blooio's consent screen as the Blooio MCP app.
  3. Blooio redirects back to /oauth/callback, which only continues in the browser that confirmed step 2 (a short-lived __Host- cookie), so a consent link someone else started can't hand them your tokens. If the app is installed on several of the user's organizations, the server asks which one this connection should use.
  4. The client receives Blooio's tokens wrapped with that organization (bmcp_<organization_id>.<token>), so every tool call is pinned to the chosen organization. The server stores no long-lived tokens; refresh requests are forwarded to Blooio.

Discovery documents are served at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. Calls without valid credentials get 401 with a WWW-Authenticate header pointing at the latter.

Endpoints

EndpointPurpose
POST /v4MCP JSON-RPC (Streamable HTTP, JSON responses)
GET /v4/manifestTools, resources, and prompts as JSON
POST /v4/callOne tool call without JSON-RPC framing: { "tool": "...", "arguments": {...} }
ALL /v4/<path>Pass-through to https://api.blooio.com/v4/<path>
/oauth/*, /.well-known/*OAuth and discovery

Development

Requires Node 22+.

bash
npm installnpm test            # unit testsnpm start           # wrangler dev on http://localhost:8787

To run sign-in locally, create a Blooio app in the dashboard (Developers → Apps) with redirect URI http://localhost:8787/oauth/callback, put its client id in wrangler.toml as BLOOIO_OAUTH_CLIENT_ID, and its secret in .dev.vars:

BLOOIO_OAUTH_CLIENT_SECRET=blosec_...

Then point the MCP Inspector at http://localhost:8787/v4.

Updating the tools

src/operations.json is compiled from the OpenAPI spec. To regenerate it:

bash
npm run sync-spec -- https://docs.blooio.com/openapi.v4.json

License

Apache 2.0

Source: README.md at commit f0ad320

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v4.1.0LatestOct 31, 2026

Score

85% 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