EZTexting MCP

com.eztextingPublished by eztexting.comOfficial publisherv1.0.4Updated Nov 2, 2026

Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, reports.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Official EZTexting MCP server that lets an assistant send SMS/MMS messages and manage contacts, workflows, reports and account settings.

What you can do
  • Send and track SMS/MMS messages, list and read messages, and manage templates, conversations and message reports
  • Create and manage contacts, contact groups and custom contact fields
  • List, fetch, save, run and monitor workflows, including templates and workflow statistics
  • View account details, statistics, keywords and webhooks, and buy messaging credits
When to use it
Useful when you want an assistant to run EZTexting text-messaging campaigns or customer outreach: sending messages, maintaining contact lists, building or checking workflows, and pulling delivery or account reports.
Requirements
An EZTexting account and OAuth 2.1 PKCE sign-in through a browser on first connect. The recommended setup is the remote endpoint at mcp.eztexting.com/mcp; the npm package @eztexting/mcp-server is a stdio bridge for clients without native remote MCP support and needs Node.js 20+.
Before you install
The server can send real SMS/MMS messages and change contacts and workflows, so actions reach real recipients and cost messaging credits; a buy_credits tool can spend money on the account. Sign-in tokens are cached locally under the user's home directory by the stdio bridge, and message and contact data is handled by EZTexting's hosted service.

Installation

In SourceWeft

  1. Open EZTexting MCP 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.eztexting%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": {
    "eztexting": {
      "type": "http",
      "url": "https://mcp.eztexting.com/mcp"
    }
  }
}

README

@eztexting/mcp-server

mcp-name: com.eztexting/mcp

Stdio bridge to the EZTexting MCP service at https://mcp.eztexting.com. Use this only when your client doesn't speak Streamable HTTP MCP natively.

Prefer remote. Most modern MCP clients (Claude.ai, ChatGPT, Claude Desktop, Claude Code, Cursor 0.46+, VS Code 1.99+, Windsurf, Cline 3.0+) connect direct to https://mcp.eztexting.com/mcp — no npm, no Node, no child process. See the onboarding guide for copy-paste configs.

Thin wrapper around mcp-remote targeting the unified /mcp endpoint. One stdio MCP entry, all 38 tools (some staticly loaded and others discoverable), one OAuth 2.1 PKCE dance. ~3k tokens of catalog (measured).

Remote (recommended)

Point your client at:

https://mcp.eztexting.com/mcp

OAuth 2.1 PKCE auto-discovers via /.well-known/oauth-authorization-server. See https://mcp.eztexting.com/ for per-client snippets (Claude Desktop, Claude Code --transport http, Cursor, VS Code type: http, Windsurf, Cline).

Local stdio bridge — fallback

Add to claude_desktop_config.json (or equivalent — only if your client lacks remote MCP support):

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

First run: browser opens to https://mcp.eztexting.com/oauth2/.... Sign in. Tokens persist to ~/.mcp-auth/mcp-remote-<version>/<hash>/. Subsequent launches skip the browser.

To force a fresh sign-in, delete that directory.

Sub-servers

The unified /mcp endpoint includes all of these. Use the per-sub-server form below only if you want narrow tool catalogs or separate Claude Code identities.

Sub-serverURLTools
messaginghttps://mcp.eztexting.com/mcp/messagingmessage_send, message_list, message_get, message_template_*, conversation_*, message_report_*
contactshttps://mcp.eztexting.com/mcp/contactscontact_*, contact_group_*, contact_field_*
workflowshttps://mcp.eztexting.com/mcp/workflowswf_list, wf_fetch, wf_save, wf_status, wf_schema, wf_templates, wf_stat, wf_create_from_template
adminhttps://mcp.eztexting.com/mcp/adminaccount_details, buy_credits, stat_get, webhook_*, keyword_list

Tool names are exposed unprefixed; EZTexting's catalog has no cross-sub-server collisions.

Local bridge — per sub-server (advanced)

Pass --server <name> to scope to one sub-server. Each invocation runs its own mcp-remote child. Remote clients should just point at the sub-server URL directly (e.g., https://mcp.eztexting.com/mcp/messaging) — no flag needed.

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

Valid names: messaging, contacts, workflows, admin.

Build from source

git clone https://github.com/eztexting/mcp-server.gitcd mcp-servernpm installnpm run buildnode dist/cli.js                        # unified /mcp endpointnode dist/cli.js --server messaging     # single sub-server

Files written

mcp-remote owns the auth cache: ~/.mcp-auth/mcp-remote-<version>/<serverUrlHash>/{tokens.json,client_info.json}. One hash per distinct upstream URL.

Requirements

  • EZTexting account
  • Browser available on first connect (OAuth 2.1 PKCE)
  • Node.js 20+ — only if using the local stdio bridge (remote clients don't need it)

Source: README.md at commit 087b3e1

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. v1.0.4LatestSep 16, 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