EZ Texting MCP — Onboarding

Overview

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI assistants securely connect to external tools and data. EZ Texting's MCP server puts your account directly inside the AI clients you already use. No switching tabs, no copy-paste.

EZ Texting MCP exposes 48 tools across 4 groups (+3 meta-tools on the unified endpoint) — send SMS/MMS, manage contacts and groups, run workflows, fetch reports, manage webhooks, query account state.

Prerequisites

• EZ Texting account — sign in at eztexting.com.
• Browser — sign-in uses OAuth 2.0 authorization code with PKCE (S256) and opens on first connect. Clients register via Dynamic Client Registration or a Client ID Metadata Document; no API keys needed.
• Node.js 20+ — only if you fall back to the local stdio bridge. Verify: node -v.

Claude.ai (web)

1. Go to claude.ai → Settings → Connectors.
2. Click Add custom connector.
3. Name: EZ Texting
4. URL:

   https://mcp.eztexting.com/mcp

   Copy
5. Save → Click Connect → OAuth pop-up → sign in.

Available on Pro / Max / Team / Enterprise plans.

ChatGPT

ChatGPT supports remote MCP via custom connectors (Plus / Pro / Team / Enterprise — Developer mode).

1. Settings → Connectors → Advanced settings → enable Developer mode.
2. Connectors → Create.
3. Name: EZ Texting
4. MCP Server URL:

   https://mcp.eztexting.com/mcp

   Copy
5. Auth: OAuth (auto-discovered).
6. Save → Connect → sign in.

Claude Desktop

Remote — Custom Connector (recommended)

1. Settings → Connectors → Add custom connector.
2. Name: EZ Texting
3. URL: https://mcp.eztexting.com/mcp
4. Save → Connect → OAuth pop-up → sign in.

Pro / Max / Team / Enterprise plans. No config file, no Node.

Local stdio — fallback

Edit your config file, then fully quit + relaunch Claude Desktop.

{
  "mcpServers": {
    "eztexting": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"]
    }
  }
}

Verify: Settings → Developer → MCP Servers. eztexting shown as "running".

Claude Code

Remote — HTTP transport (recommended)

claude mcp add --transport http eztexting https://mcp.eztexting.com/mcp

Scope flag works the same:

claude mcp add --transport http --scope user eztexting https://mcp.eztexting.com/mcp
claude mcp add --transport http --scope project eztexting https://mcp.eztexting.com/mcp

Or in ~/.claude.json / .mcp.json:

{
  "mcpServers": {
    "eztexting": {
      "type": "http",
      "url": "https://mcp.eztexting.com/mcp"
    }
  }
}

Verify: claude mcp list. Then run /mcp in Claude Code and choose Authenticate; a browser window opens to sign in.

Local stdio — fallback

claude mcp add eztexting -- npx -y @eztexting/mcp-server

Or JSON:

{
  "mcpServers": {
    "eztexting": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"]
    }
  }
}

Cursor (0.46+)

Remote (recommended)

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "eztexting": {
      "type": "http",
      "url": "https://mcp.eztexting.com/mcp"
    }
  }
}

Or: Settings → MCP → Add new MCP server → choose HTTP transport.

Local stdio — fallback

{
  "mcpServers": {
    "eztexting": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"]
    }
  }
}

VS Code 1.99+ (GitHub Copilot Chat — Agent Mode)

Remote (recommended)

Command palette → MCP: Open User Configuration. Add:

{
  "servers": {
    "eztexting": {
      "type": "http",
      "url": "https://mcp.eztexting.com/mcp"
    }
  }
}

Workspace scope: same shape in .vscode/mcp.json. Open Copilot Chat → Agent mode → eztexting tools surface.

Local stdio — fallback

{
  "servers": {
    "eztexting": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"]
    }
  }
}

Windsurf (Codeium)

Edit ~/.codeium/windsurf/mcp_config.json (or: Settings → Cascade → MCP Servers → Add).

Remote (recommended)

{
  "mcpServers": {
    "eztexting": {
      "serverUrl": "https://mcp.eztexting.com/mcp"
    }
  }
}

Local stdio — fallback

{
  "mcpServers": {
    "eztexting": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"]
    }
  }
}

Restart Windsurf after editing.

Cline 3.0+ (VS Code extension)

Open Cline panel → MCP Servers icon → Configure MCP Servers → opens cline_mcp_settings.json.

Remote (recommended)

{
  "mcpServers": {
    "eztexting": {
      "type": "streamableHttp",
      "url": "https://mcp.eztexting.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Local stdio — fallback

{
  "mcpServers": {
    "eztexting": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Save → Cline auto-restarts server. Refresh MCP panel if tools don't appear.

Zed

Zed remote-MCP support is limited as of writing. Use the local stdio bridge.

Open ~/.config/zed/settings.json. Add under context_servers:

{
  "context_servers": {
    "eztexting": {
      "command": {
        "path": "npx",
        "args": ["-y", "@eztexting/mcp-server"]
      },
      "settings": {}
    }
  }
}

Restart Zed. Tools surface in the assistant panel.

Data access & permissions

The connector acts as the EZ Texting user who signs in, with that user's account permissions.

• Reads — messages, scheduled messages, drip campaigns, conversations, contacts, groups, custom fields, templates, workflows, reports, webhooks, keywords, phone numbers and account details.
• Writes — sends and schedules SMS / MMS; creates, updates and deletes contacts, groups, custom fields, templates and scheduled messages; creates, updates, publishes and unpublishes workflows (a published workflow sends messages automatically); creates and deletes webhooks; updates conversation state; buys message credits.
• Credits — sending messages uses account credits.

Tools that only read are marked read-only; tools that send messages, overwrite or delete data are marked destructive, so your AI client asks before running them. To revoke access, disconnect the connector in your AI client.

See the EZ Texting Privacy Policy for how data is handled.

Available tools

48 tools across 4 functional groups (+3 meta-tools on the unified endpoint — see tool tiers).

Messaging — 21 tools

Contacts — 11 tools

Workflows — 8 tools

Workflow publishing eligibility is exposed via account_details (workflowPublishAllowed).

Admin — 8 tools

Unified /mcp — HOT & COLD tool tiers

The unified https://mcp.eztexting.com/mcp endpoint runs in hybrid mode. Rather than dumping all 48 tool schemas into every tools/list response (which consumes context budget before you type a single prompt), it lists a curated set of HOT tools and every write tool directly, and hides the remaining read-only tools behind three lightweight meta-tools — 31 tools listed in total. The meta-tools only ever reach read-only tools.

HOT tools — always in tools/list 10 tools

Listed statically on every connection. Zero latency, no discovery step needed.

Write tools — always in tools/list 18 tools

Every tool that creates, changes, deletes or buys something is listed directly, in addition to the HOT tools above (5 of which are writes). Write tools are never reachable through the meta-tools: buy_credits, contact_delete, contact_group_upsert, contact_group_delete, contact_group_membership, contact_field_upsert, contact_field_delete, message_schedule_create_recurring, message_schedule_update, message_schedule_update_recurring, message_schedule_delete, message_template_upsert, message_template_delete, webhook_create, webhook_delete, wf_save, wf_status, wf_create_from_template.

COLD tools — read-only, discoverable via meta-tools 20 tools

The remaining read-only tools (message lookups, schedules, templates, reports, drips, groups, fields, workflow reads, admin lookups) are hidden from tools/list but fully reachable via the meta-tools below. See the Available tools section for the full list.

Meta-tools — the discovery surface 3 tools

Always listed alongside HOT and write tools. Let the AI find and run COLD read-only tools without you spelling out tool names.

Typical flow with COLD tools

You don't need to manage this manually — the AI handles it automatically. For reference:

1. AI calls search_tools("phone number") → discovers phone_number_list
2. AI calls describe_tools(["phone_number_list"]) → gets full schema
3. AI calls execute_read_tool({"tool_name": "phone_number_list", "args": {}}) → lists the account's phone numbers

For clients or scripts that need all 48 tools listed without the discovery layer, use the relevant sub-server URL directly (e.g. /mcp/admin for webhook tools).

Token measurements

Measured via tools/list response size (the full JSON-RPC response). Token estimate: bytes ÷ 4

Sub-servers (narrow scopes)

Use the unified /mcp endpoint by default. Pick a sub-server when you want the full catalog without discovery overhead.

Remote — pin one sub-server

Point your client at the sub-server URL directly. Example (Claude Code):

claude mcp add --transport http eztexting-messaging https://mcp.eztexting.com/mcp/messaging

Or JSON (Cursor / VS Code / Claude Desktop / Claude Code):

{
  "mcpServers": {
    "eztexting-messaging": {
      "type": "http",
      "url": "https://mcp.eztexting.com/mcp/messaging"
    }
  }
}

Local stdio — pin one sub-server

{
  "mcpServers": {
    "eztexting-messaging": {
      "command": "npx",
      "args": ["-y", "@eztexting/mcp-server", "--server", "messaging"]
    }
  }
}

Example prompts