SureM SMS MCP
OfficialThe SureM SMS MCP server enables you to send messages and voice calls via the SureM platform, primarily through natural language commands in Claude.
Domestic SMS/LMS: Automatically sends as SMS (≤90 bytes, EUC-KR) or upgrades to LMS (91–2,000 bytes) based on message length — no manual type selection needed.
International SMS: Send to non-Korean numbers with automatic encoding detection and support for up to 500 characters.
MMS with Image Attachments: Attach 1–3 JPG images via the
upload_mms_imagetool (stdio mode only).TTS Voice Calls: Convert text (up to 90 characters) to speech and deliver it as a phone call.
Scheduled Sending: Schedule messages for a future time using
yyyyMMddhhmmssformat, or send immediately if no time is specified.Message Length Validation: Pre-validates message length before sending to avoid wasted API calls.
API Authentication Management: Automatically caches and refreshes API tokens.
Note: Sender phone numbers must be pre-registered in SureBiz. Scheduled message cancellation must be done manually via the SureBiz website. MMS image attachment is available in stdio mode only.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SureM SMS MCP010-1234-5678에 '회의 30분 전입니다' 문자 보내줘. 발신번호 15884640."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SureM SMS MCP
An MCP server that allows you to send text messages via SureM just by talking to Claude.
"발신번호 15884640으로 010-0000-0000에 '오늘 저녁 7시 약속 잊지 마세요' 문자 보내줘"Key Features
Natural Language Sending — Send SMS/LMS automatically by talking to Claude as if in a conversation.
Automatic SMS/LMS Switching — Automatically selected based on message length (bytes in EUC-KR):
90 bytes or less → SMS
91 ~ 2,000 bytes → LMS
Scheduled Sending — Schedule messages for a specific time (sends immediately if not specified).
Message Length Validation — Warns before sending if it exceeds 2,000 bytes.
Automatic Token Refresh — Automatically caches/refreshes API authentication tokens (every 50 minutes).
Related MCP server: SMS Masivos MCP Server
Getting Started (4 Steps)
Step 1. Install Required Programs
Program | Description |
The client that uses this MCP | |
v16 or higher |
After installation, verify with the following commands in your terminal (PowerShell / Terminal):
node --versionStep 2. Sign up for SureM and Generate SecretKey
Visit SureBiz (surebiz.co.kr) and sign up.
After logging in, go to Basic Info → My Info.
Generate a
SecretKeyfrom the REST API Authentication Key menu at the bottom of the page.Note down your SureM ID (UserCode) and SecretKey.
These two values are required as environment variables when installing the MCP.
Step 3. Register IP and Sender Number
The SureM API can only be used from pre-registered IPs and sender numbers. Please register both of the following first.
3-1. Register Your PC's IP
Search for "my IP address" on Naver to check your public IP.
Register that IP in SureBiz → Basic Info → Customer Support → IP Management.
If the IP is not registered, an "HTTP 403 Failure" error will occur.
3-2. Register Sender Number
The sender number used for sending messages must be pre-registered on SureBiz.
Register the sender number you intend to use in SureBiz → Basic Info → Sender Number.
Only numbers that have passed the registration review can be used in the MCP.
If you attempt to send from an unregistered number, the message will not be sent due to a sender number registration error.
Step 4. Install MCP
Choose the method appropriate for your OS.
🪟 Windows (Automatic Installation)
Open PowerShell and run the following command:
irm https://raw.githubusercontent.com/suremapp/surem-sms-mcp/main/scripts/install-windows.ps1 | iexOnce the script runs, it will prompt you to enter your UserCode and SecretKey in order. (Have these values ready.)
.\scripts\install-windows.ps1 -UserCode "슈어엠_아이디" -SecretKey "API_키"🍎 Mac (Automatic Installation)
Run the following command in your terminal. After running, you will be prompted to enter your UserCode and SecretKey.
curl -s https://raw.githubusercontent.com/suremapp/surem-sms-mcp/main/scripts/install-mac.sh | bashcurl -s https://raw.githubusercontent.com/suremapp/surem-sms-mcp/main/scripts/install-mac.sh | bash -s 슈어엠_아이디 API_키✏️ Manual Installation
Add it directly to the claude_desktop_config.json file of Claude Desktop.
File Location:
OS | Path |
Windows (Microsoft Store) |
|
Windows (Standard) |
|
Mac |
|
Configuration:
{
"mcpServers": {
"surem-sms-mcp": {
"command": "npx",
"args": ["-y", "surem-sms-mcp"],
"env": {
"SUREM_USER_CODE": "슈어엠_아이디",
"SUREM_SECRET_KEY": "API_키"
}
}
}
}Verify Installation
Completely exit and restart Claude Desktop (if it is running in the system tray, ensure it is closed from the tray icon).
Check if
surem-sms-mcpis enabled in the + button → Connectors menu at the bottom left of the chat window.
How to Use
Simply speak to Claude in natural language. The sender number must be pre-registered on SureBiz.
Examples
"발신번호 15884640으로 010-0000-0000에 '내일 오전 10시 미팅입니다' 문자 보내줘""010-0000-0000에 배송 완료 안내 문자 보내줘. 발신번호는 15881234야.""아래 내용으로 LMS 발송해줘.
받는 사람: 010-0000-0000
발신번호: 15884640
제목: 주문 확인
내용: 주문하신 상품이 오늘 출고됩니다. 감사합니다."If the message is long, it will automatically switch to LMS. No separate instructions are needed.
Scheduled Sending
Specify a time to schedule the message.
"내일 오전 9시에 010-0000-0000로 '좋은 아침입니다' 문자 보내줘. 발신번호는 15884640.""2026년 4월 25일 오후 2시 30분에 010-0000-0000에 세미나 안내 LMS 예약 발송해줘.
발신번호: 15884640
제목: 세미나 안내
내용: 오늘 오후 3시 3층 대회의실에서 세미나가 진행됩니다."⚠️ Cancellations of scheduled messages must be done manually on SureBiz. You can cancel scheduled items in the SureBiz → Reservation/Results → Reservation Inquiry menu.
Provided Tools
send_message
Sends an SMS or LMS by receiving the recipient number, content, and sender number. The type is automatically selected based on message length.
Parameter | Required | Description |
| ✅ | Recipient phone number (e.g., |
| ✅ | Message content to send |
| ✅ | Sender number (pre-registered on SureBiz, e.g., |
| ⬜ | LMS subject — Used when the message exceeds 90 bytes and switches to LMS (Default: |
| ⬜ | Scheduled time — |
Sending results can also be checked in the Result Inquiry menu on the SureBiz site. Cancellation of scheduled messages is only possible via the Reservation/Results → Reservation Inquiry menu on the SureBiz site.
FAQ
[ ] Check if the SecretKey was entered correctly.
[ ] Check if your current PC's public IP is registered on SureBiz (IP may change if using VPN/tethering/moving offices).
[ ] Check if
SUREM_USER_CODEis your SureM ID.
If the request was successful but the message was not received, check in the following order:
Check the reason for failure in the SureBiz Result Inquiry menu.
Reasons for failure can vary, such as:
Sender number not registered / pending approval
Recipient has registered for 080 opt-out
Mobile carrier spam filtering
Incorrect recipient number format
Messages can be sent up to a maximum of 2,000 bytes based on EUC-KR. Since 1 Korean character = 2 bytes, the limit is approximately 1,000 characters.
[ ] Ensure Claude Desktop was completely exited and restarted (including the tray icon).
[ ] Check if the JSON syntax in
claude_desktop_config.jsonis correct.[ ] Ensure Node.js is installed and the
node --versioncommand works.
Cancellation of scheduled messages is not provided by the MCP. You must cancel it directly on the SureBiz site.
Log in to SureBiz (surebiz.co.kr).
Go to the Reservation/Results → Reservation Inquiry menu.
Select the scheduled item to cancel and proceed with cancellation.
License
Copyright © 2026 SureM Co., Ltd. All Rights Reserved.
This software is the exclusive property of SureM Co., Ltd.
Contact
SureM Customer Center: 1588-4640
Email: suremapp@surem.com
Website: surebiz.co.kr
Available Tools
1 toolsend_messageB
슈어엠 API로 문자를 발송합니다. 메시지 길이에 따라 SMS(90바이트 이하) / LMS(91~2000바이트)가 자동 선택됩니다. reservedTime을 지정하면 예약 발송됩니다.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | 수신자 전화번호 (예: 01012345678) | |
| text | Yes | 발송할 메시지 내용 | |
| reqPhone | Yes | 발신번호 (예: 15884640) | |
| subject | No | LMS 제목 (메시지가 길 경우 사용, 기본값: '메시지') | |
| reservedTime | No | 예약 발송 시각 (yyyyMMddhhmmss, 미입력 시 즉시 발송). 예약 취소는 슈어비즈 → 예약,결과 → 예약조회 메뉴에서 수동으로 진행 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key behaviors: automatic SMS/LMS selection based on message length (90 bytes threshold) and scheduled sending capability with reservedTime. However, it doesn't mention authentication requirements, rate limits, error handling, or what happens after sending. The description adds value but leaves significant behavioral aspects unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately concise with three sentences that each add value: states the core purpose, explains automatic message type selection, and describes scheduled sending capability. It's front-loaded with the main function. Some minor redundancy exists between description and schema for reservedTime.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a message-sending tool with no annotations and no output schema, the description provides basic operational context but lacks important details. It covers what the tool does and some behavioral aspects, but doesn't address authentication, error responses, success indicators, or system limitations. The description is minimally adequate but has clear gaps for a mutation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions the reservedTime enables scheduled sending and implies subject is for LMS, but doesn't provide additional context about parameter interactions or usage patterns. Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: '슈어엠 API로 문자를 발송합니다' (send messages via SureM API). It specifies the action (send) and resource (messages) but doesn't differentiate from siblings since none exist. The description adds useful context about automatic SMS/LMS selection based on message length.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It mentions automatic SMS/LMS selection and scheduled sending capabilities, but doesn't indicate prerequisites, constraints, or comparison to other messaging approaches. With no sibling tools, this is less critical but still a gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.1- First observed
send_message
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose: sending SMS/LMS messages via the SureM API.
The single tool name 'send_message' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for a server named 'SureM SMS MCP', which suggests a broader SMS service domain. Expected operations like checking message status, managing contacts, or handling templates are missing, making the surface feel incomplete for the implied scope.
The server is severely incomplete for an SMS service domain. It only provides message sending, lacking essential operations such as retrieving message delivery status, listing sent messages, managing contacts, or handling templates, which are typical for such services.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Send and schedule SMS and WhatsApp messages, manage contacts and templates, and track delivery.
- SureSMSOAuthcom.suresms
Send SMS, manage contacts and groups, and read delivery reports. OAuth 2.1 SureSMS login.
The Mobile Text Alerts SMS MCP server enables your AI to send SMS messages & manage contacts
Envoyez des SMS et gérez vos campagnes directement depuis vos agents IA.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.161MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to send SMS, manage contacts, verify numbers, and query campaigns via SMS Masivos platform using natural language.3026MIT

ReadySMS MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables sending SMS messages, managing contacts, campaigns, and inbox from AI assistants like Claude and ClickUp.33MIT- AlicenseNot gradedqualityDmaintenanceEnterprise-grade WhatSMS integration for Claude AI providing 173 tools for SMS, WhatsApp, OTP, contacts, and device management.13MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/suremapp/surem-sms-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server