iBlueText

com.ibluetextPublished by ibluetext.comOfficial publisherv1.0.2Updated Nov 7, 2026

Send iMessage, SMS and WhatsApp from a dedicated line, run text campaigns and read replies.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant send iMessage, SMS and WhatsApp from a dedicated iBlueText line, run text campaigns, and read replies and lead data.

What you can do
  • Send single iMessage, SMS or WhatsApp messages with attachments, effects, quote-replies and scheduling, and add tapback reactions
  • Create and manage bulk campaigns with merge fields, check campaign status and pause campaigns
  • Check which phone numbers are iPhones and track lookup results
  • Read conversations and transcripts with lead scores, manage contacts, quick answers and sequences
  • Manage reply webhooks, run SMS verification and create SMS-Verify widget sites
  • Check account balance and available lines
When to use it
Useful when an assistant should handle customer texting end to end: one-off messages, outreach campaigns, WhatsApp follow-ups, or pulling replies and lead scores into a conversation. It fits sales and support teams that already run texting on an iBlueText line.
Requirements
A remote Streamable HTTP endpoint with OAuth sign-in (no API key) for hosted clients, or the local npm package run via npx with an IBT_API_KEY environment variable for the larger tool set. An iBlueText account with an active line and credits is needed for paid actions; network access to the iBlueText service is required.
Before you install
Sending messages, campaigns, WhatsApp messages and verifications contacts real people and is flagged as destructive; clients may prompt before running. Paid actions fail with HTTP 402 when credits or an active line are missing, so sending costs money. The local package requires an IBT_API_KEY secret, which is sent only to the fixed iBlueText API address. Opt-out (STOP) rules and per-line daily new-contact limits apply, and WhatsApp numbers are rate-limited by warm-up rules.

Installation

In SourceWeft

  1. Open iBlueText 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.ibluetext%2Fibluetext/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": {
    "ibluetext": {
      "type": "http",
      "url": "https://ibluetext.com/mcp"
    }
  }
}

README

iBlueText MCP server

[M8ven Verified]

[mcptry]

[iBlueText MCP server]

Text your customers from your AI assistant. iBlueText sends real blue-bubble iMessage, SMS and WhatsApp from a dedicated iBlueText line, and checks which numbers are iPhones. This MCP server gives Claude, ChatGPT, Cursor and any other MCP client native tools for it: send one message or a whole campaign, read replies and lead scores, manage contacts, sequences and quick answers, and check which numbers are iPhones.

There are two ways to connect.

1. Hosted (ChatGPT, Claude, no API key)

Server URL: https://ibluetext.com/mcp (Streamable HTTP, OAuth sign-in)

  • Claude: Settings › Connectors › Add custom connector › paste the URL › Connect, then sign in to iBlueText and click Allow.
  • ChatGPT: Settings › Apps (Developer mode) › create an app with the URL, then sign in and Allow.
  • Any remote-MCP client: use the URL; the client discovers OAuth from /.well-known/oauth-protected-resource.

22 tools with plain verb names (send_message, create_campaign, check_iphones, list_conversations, ...). Full list and example prompts: https://ibluetext.com/ai-assistants

2. Local package with an API key (developers, 28 tools)

  1. Create an API key at https://ibluetext.com/portal/integrations.php
  2. Add this to your MCP client config (for example Claude Desktop claude_desktop_config.json):
json
{  "mcpServers": {    "ibluetext": {      "command": "npx",      "args": ["-y", "ibluetext-mcp"],      "env": { "IBT_API_KEY": "sk-ibt-your_key_here" }    }  }}

Claude Code: claude mcp add ibluetext --env IBT_API_KEY=sk-ibt-... -- npx -y ibluetext-mcp

The package adds SMS verification, verify-widget sites and reply webhooks to the hosted tool set.

Tools

Account: ibt_balance · ibt_lines

Lookup: ibt_lookup (which numbers are iPhones; waits for results) · ibt_lookup_status

Send: ibt_send (one iMessage/SMS; channel, attachments, effects, quote-reply, scheduling) · ibt_send_status · ibt_react (tapbacks)

Campaigns: ibt_campaign_create (a whole list: iMessage, SMS, auto-detect or WhatsApp, with {merge} fields) · ibt_campaigns · ibt_campaign_status · ibt_campaign_pause

WhatsApp: ibt_whatsapp_send · ibt_whatsapp_status · ibt_whatsapp_numbers (warm-up, today's limit, reply rate, health)

Contacts & CRM: ibt_conversations (transcripts + lead score) · ibt_conversation_ai · ibt_quick_answers / ibt_quick_answer_set · ibt_contact / ibt_contact_update · ibt_contacts · ibt_sequences / ibt_sequence_enroll

Webhooks: ibt_webhooks / ibt_webhooks_set

Verification: ibt_verify_start / ibt_verify_check · ibt_create_site (SMS-Verify widget)

Notes

  • Paid actions return HTTP 402 when the account is out of credits or has no active line. The tool result is flagged payment_required: true; a person adds credits or a line in the iBlueText dashboard.
  • Opt-outs (STOP) and each line's daily new-contact limit always apply.
  • WhatsApp numbers warm up from 10 new conversations on day 1 to 300/day by day 21; someone who never replied gets at most 3 messages; under 15% replies over 7 days halves the daily limit. Open with a question like "Hey, is this {first_name}?".
  • Local dev: IBT_API_KEY=sk-ibt-... node index.js (MCP over stdio). Tests: npm test (starts the server over stdio, no key or network needed).
  • Security: your API key is only ever sent to https://ibluetext.com/api/v1 (the address is fixed in the code, not configurable). Every tool is annotated: reads are readOnlyHint, and tools that message a real person (send, campaign, WhatsApp, verify) are destructiveHint + openWorldHint, so clients can ask before they run.
  • REST API: https://ibluetext.com/docs/ · OpenAPI: https://ibluetext.com/openapi.json · For AI agents: https://ibluetext.com/llms.txt

Support

[email protected] · Privacy · Terms

MIT licensed. iBlueText is a product of RG Loomis LLC.

Source: README.md at commit 9dd84ec

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

3
  1. v1.0.2LatestNov 7, 2026
  2. v1.0.1Nov 5, 2026
  3. v1.0.0Oct 26, 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