English Français العربية

EZTexting MCP

Official registry Other

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http eztexting-mcp 'https://mcp.eztexting.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eztexting-mcp": {
            "type": "http",
            "url": "https://mcp.eztexting.com/mcp"
        }
    }
}
NPM package @eztexting/mcp-server
Claude Code 
claude mcp add eztexting-mcp -- npx -y @eztexting/mcp-server@1.0.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eztexting-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@eztexting/mcp-server@1.0.4"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @eztexting/mcp-server
  2. Remote (recommended)
  3. Local stdio bridge — fallback
  4. Sub-servers
  5. Local bridge — per sub-server (advanced)
  6. Build from source
  7. Files written
  8. Requirements

@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).

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):

{
  "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.

{
  "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.git
cd mcp-server
npm install
npm run build
node dist/cli.js                        # unified /mcp endpoint
node 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)

Frequently asked questions

What is EZTexting MCP?

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

How do I install EZTexting MCP?

It runs as a remote server. In Claude Code: claude mcp add --transport http eztexting-mcp 'https://mcp.eztexting.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does EZTexting MCP need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is EZTexting MCP open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains EZTexting MCP?

It is published by eztexting. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.