Eztexting

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

FAQ from Eztexting

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.