English Français العربية

EZTexting MCP

السجل الرسمي أخرى

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

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http eztexting-mcp 'https://mcp.eztexting.com/mcp'
إعداد JSON (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 (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "eztexting-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@eztexting/mcp-server@1.0.4"
            ]
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  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)

الأسئلة الشائعة

ما هو EZTexting MCP؟

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

كيف أثبّت EZTexting MCP؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http eztexting-mcp 'https://mcp.eztexting.com/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج EZTexting MCP إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل EZTexting MCP مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون EZTexting MCP؟

ينشره eztexting. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.