AI assistants & the MCP server
Use your EZ Texting account from AI tools like Claude and ChatGPT.
The EZ Texting MCP Server exposes your account to AI assistants through the Model Context Protocol. Connect it once and you can send messages, manage contacts and groups, build automation workflows, and pull reports in plain language, from Claude, ChatGPT, Cursor, VS Code, and any other MCP-capable client.
Full setup guides, per client, live at mcp.eztexting.com. This page is about where it fits next to the API.
At a glance
| Server URL | https://mcp.eztexting.com/mcp. Client-specific and scoped URLs are listed at mcp.eztexting.com. |
| Auth | OAuth 2.0 with PKCE. You sign in with your EZ Texting login; the AI client never sees your password. |
| Permissions | The assistant acts as your account. Destructive tools (deleting contacts, webhooks) ask for confirmation. |
| Tools | Messaging, contacts and groups, workflows, reports, and account tools. The current list is at mcp.eztexting.com. |
| Local option | npx -y @eztexting/mcp-server for clients that read a config file. |
API or MCP?
They're the same platform through two doors.
| Use the REST API when… | Use the MCP server when… |
|---|---|
| Your software needs to send, read, or react: a reminder service, an OTP flow, a CRM sync. | A person (or an agent on their behalf) needs to do something: "text the Tuesday group that we're closed", "how did Friday's campaign do?". |
| It has to run unattended and at volume. | It's ad hoc, exploratory, or one-off. |
| You need deterministic behavior and your own error handling. | You want the assistant to figure out the sequence of calls. |
They compose well:
- Prototype in chat, then code it. Ask the assistant to set up a contact group, a template, and a test send; look at what it did (the MCP tools call the same endpoints); then write the production version against the API with the IDs it created.
- Operate what you built. A support lead can ask "show me unread conversations from today" against the same account your app writes to.
- Let an agent call the API. If you're building your own agent, the MCP server is a ready-made tool set, so there's no need to wrap the REST endpoints yourself.
Things to know
- Credits and compliance apply exactly as with the API. An assistant that sends 5,000 single-segment SMS messages spends 5,000 credits, and opt-outs are enforced the same way. Give the assistant the same guardrails you'd give a new employee: a test group, clear instructions, review before campaigns.
- Contacts created through MCP carry
source: MCP, so you can tell them apart inGET /v1/contactsand in workflow triggers. - Scope the server when you connect a client that only needs part of the surface. The scoped URLs are listed at mcp.eztexting.com.
Related
- mcp.eztexting.com
- Core concepts
- Authentication — credentials for the REST API
Need help?
Try Troubleshooting, check status.eztexting.com, or contact support.
Updated about 19 hours ago
Did this page help you?