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 38 tools — 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 — OAuth 2.1 PKCE pops on first connect.
• 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. First tool call triggers OAuth.

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.

Available tools

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

Messaging — 12 tools

Contacts — 11 tools

Workflows — 8 tools

Workflow publishing eligibility is exposed via account_details (workflowPublishAllowed).

Admin — 7 tools

Unified /mcp — HOT & COLD tool tiers

The unified https://mcp.eztexting.com/mcp endpoint runs in hybrid mode. Rather than dumping all 38 tool schemas into every tools/list response (which consumes context budget before you type a single prompt), it exposes a curated set of HOT tools directly and hides the rest behind three lightweight meta-tools.

HOT tools — always in tools/list 11 tools

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

COLD tools — discoverable via meta-tools 27 tools

All remaining tools (templates, reports, groups, fields, all workflows, admin bulk ops) 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 tools. Let the AI find and execute COLD 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("webhook") → discovers webhook_list, webhook_create, webhook_delete
2. AI calls describe_tools(["webhook_create"]) → gets full schema
3. AI calls execute_tool("webhook_create", {"url": "...", "events": [...]}) → creates the webhook

For clients or scripts that need all 38 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 against https://mcp.eztexting.com. 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