Eztexting MCP Server

@eztexting

代码仓库

基本信息

分类

其他

传输方式

stdio

作者

eztexting

提交者

Mike Collard

关于 Eztexting MCP Server

Send SMS/MMS, manage contacts and groups, build workflows, fetch reports, manage webhooks, query account state

#eztexting#sms#mms#marketing

Eztexting MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

Eztexting MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,直接连接服务器端点实时获取工具列表。

概览

What is Eztexting?

Eztexting is an MCP (Model Context Protocol) server that bridges AI assistants to the EZTexting service, exposing 38 tools across messaging, contacts, workflows, and admin domains. It is designed for developers and businesses who want to manage SMS/voice campaigns, contact lists, and automation workflows through natural language interfaces. A remote endpoint is the recommended method; the local stdio bridge is a fallback for clients that do not support Streamable HTTP MCP natively.

How to use Eztexting?

The preferred way is to point your MCP client directly at https://mcp.eztexting.com/mcp — OAuth 2.1 PKCE is handled automatically. If your client lacks remote MCP support, install the npm package @eztexting/mcp-server and add a stdio configuration (e.g., in claude_desktop_config.json). On first run, a browser opens for sign-in; tokens persist to ~/.mcp-auth/ for subsequent launches.

Key features of Eztexting

Remote MCP endpoint (recommended) — no local dependencies
OAuth 2.1 PKCE with automatic token persistence
38 tools covering messaging, contacts, workflows, and admin
Sub‑server URLs for narrow tool catalogs (e.g., /mcp/messaging)
Thin wrapper around mcp-remote — ~3k tokens catalog

Use cases of Eztexting

Send SMS/text messages and manage conversations from an AI assistant
Create, update, and segment contact lists and groups
Build and trigger marketing workflows from templates or scratch
Retrieve account stats, buy credits, and manage webhooks & keywords

常见问题

What is the difference between the remote endpoint and the local stdio bridge?

The remote endpoint (`https://mcp.eztexting.com/mcp`) lets modern clients connect directly without installing Node.js or any npm packages. The local bridge (`@eztexting/mcp-server`) is a thin stdio wrapper for clients that don’t support Streamable HTTP MCP natively.

What are the requirements to use Eztexting?

You need an EZTexting account and a browser available on first connect (for OAuth). Node.js 20+ is required only if you use the local stdio bridge; remote clients need none of that.

How does authentication work?

The server uses OAuth 2.1 with PKCE. On the first connection, a browser window opens to `https://mcp.eztexting.com/oauth2/…` for you to sign in. Tokens are cached in `~/.mcp-auth/`; subsequent launches skip the browser.

Can I use only a subset of the tools?

Yes. You can point your client at a sub‑server URL such as `https://mcp.eztexting.com/mcp/messaging` (remote) or pass `--server messaging` to the local bridge. Valid sub‑server names are `messaging`, `contacts`, `workflows`, and `admin`.

Where are authentication tokens stored?

Tokens and client info are saved in `~/.mcp-auth/mcp-remote-<version>/<serverUrlHash>/`. Deleting that directory forces a fresh sign-in.

其他分类下的更多 MCP 服务器

Reactive Resume

amruthpillai

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

39.5K

Screenpipe

screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

22.0K

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.