Send iMessages, RCS, and SMS from Cursor. The Blooio plugin connects your Cursor agents and chat to the Blooio v2 API and the hosted Blooio MCP server, and bundles skills, rules, and an agent that know the API surface end-to-end.
Blooio gives you programmatic access to iMessage, RCS, and SMS from a real Apple ID on a real Mac. The plugin makes it trivial to wire that up from Cursor — both for one-off automation and for building production integrations.
- MCP server —
mcp.jsonregisters the hosted Blooio MCP athttps://mcp.blooio.com/v4. After you setBLOOIO_API_KEY, Cursor exposesme,send_message,get_message,get_message_status,cancel_message,contact_capabilities,webhook_get, andwebhook_setas agent tools. - Skills — task-scoped guidance the agent loads on demand:
blooio-mcp-setup— install and verify the Blooio MCP in Cursorblooio-api— auth, base URL, error codes, idempotency, plan limitsblooio-messaging— send, multipart, attachments, effects, polls, reactions, typing, read receiptsblooio-webhooks— subscribe, sign, replay, debug deliveryblooio-contacts-groups— contacts, capabilities, groups, group icons, members
- Rules —
blooio-api-conventionsis always-applied guidance the agent follows when it touches Blooio code (E.164, idempotency keys, structured error codes, never logging the API key). - Agent —
blooio-integration-builderfor designing/reviewing a full Blooio integration in your codebase. - Command —
/blooio-quickstartwalks a fresh project from "no key" to "first delivered iMessage" in one prompt.
- Open the Cursor Marketplace panel.
- Search Blooio and click Install.
- The MCP server, skills, rules, agent, and command are all activated automatically.
If you only want the MCP (not the agent guidance), use the one-click deeplink from the Blooio MCP integration page:
cursor://anysphere.cursor-deeplink/mcp/install?name=blooio-mcp&config=eyJ1cmwiOiJodHRwczovL21jcC5ibG9vaW8uY29tL3Y0In0=
git clone https://github.com/blooio/blooio-cursor-plugin.git ~/.cursor/plugins/local/blooioThen Developer: Reload Window in Cursor.
The MCP authenticates with a Bearer token. Get one from the Blooio dashboard → Settings → API Keys, then export it before launching Cursor:
export BLOOIO_API_KEY="bl_live_..."mcp.json references it as ${BLOOIO_API_KEY} so the key never lives in your repo.
If you'd rather scope the key to one workspace, put it in a workspace-level
.envand start Cursor from a shell that loaded it, or use Cursor's MCP secret UI to override theAuthorizationheader for that server.
Ask the agent: "Use the Blooio MCP to call me and confirm my account works."
Expected: a JSON blob with your organization_id, your devices, and valid: true. If you get 401, your key isn't being passed — recheck the env var.
Once installed, you can ask the agent things like:
- "Send an iMessage to +15551234567 saying 'deploy succeeded' with a confetti effect."
- "List all webhooks on my Blooio account, then create one pointing at
https://example.com/hooks/blooioformessageevents." - "Build me a TypeScript helper that wraps
POST /chats/{chatId}/messageswith idempotency and retries." - "Inspect the last 20 inbound messages and tell me which contacts haven't replied in 7+ days."
The agent will pick up the relevant skill (blooio-messaging, blooio-webhooks, etc.) automatically.
- Cursor IDE (any recent build with MCP support)
- The hosted MCP also works from ChatGPT Agent Builder, Claude Desktop, Cline, and any MCP client implementing the 2024-11-05 spec — see blooio.com/integrations/mcp.
- API & dashboard: blooio.com
- Docs: blooio.com/integrations/api, blooio.com/integrations/mcp
- Email: support@blooio.com
- iMessage: text us
MIT — see LICENSE.