Chuanglan 253 MCP for AI. Run all global messages and verifications from conversation.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Chuanglan 253 connects your AI agent to a high-volume messaging gateway, letting you send millions of SMS messages globally. Use it for one-time passwords (OTP), security verifications, and bulk notifications—all managed through conversation instead of a dashboard.
What your AI can do
Create template
Builds new, approved SMS message formats that must be used for compliant sending.
Get account info
Retrieves the overall account settings and details for your Chuanglan 253 connection.
Get sms balance
Checks how many SMS credits you have left before launching a campaign.
Dispatch standard or international text messages to any phone number worldwide.
Generate and deliver one-time passwords (OTPs) for account logins or security checks.
List, create, and manage pre-approved message formats to ensure compliance before sending campaigns.
Check current SMS credit balances and query the delivery status of specific messages or large batches.
Send an automated voice call instead of a text message when OTP delivery is unreliable.
Ask an AI about this
Waiting for input…
Chuanglan 253: Messaging Gateway with 10 Tools
These tools give you granular control over every aspect of SMS communication—from checking balances to creating compliant templates and sending verified codes.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Chuanglan 253 on VinkiusCreate Template
Builds new, approved SMS message formats that must be used for compliant sending.
Get Account Info
Retrieves the overall account settings and details for your Chuanglan 253 connection.
Get Sms Balance
Checks how many SMS credits you have left before launching a campaign.
Query Batch Sms Status
Gathers the delivery status for multiple messages sent together using one tracking...
Query Sms Status
Returns the specific delivery status, including timestamps, for a single message ID.
Query Template List
Lists all existing, pre-approved SMS templates available in your account.
Send International Sms
Sends a standard text message to any number outside of China using the international gateway.
Send Sms
Sends a standard SMS message, following specific rules for domestic Chinese numbers...
Send Verification Sms
Sends a one-time password formatted text message used primarily for login...
Send Voice Verification
Initiates an automated voice call to deliver the security code instead of using SMS.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Chuanglan 253, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Chuanglan 253. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing global messaging used to mean jumping through hoops.
Today, if a marketing team needs to run an SMS campaign across different countries, they have to log into the vendor dashboard. They check their quota in one tab, draft and get approval on templates in another, then manually paste phone numbers while monitoring status updates across a third section.
With this MCP, you skip all those clicks. You just tell your agent, 'Send out the campaign now.' The system handles checking the balance with `get_sms_balance`, ensuring compliance via template management, and sending the messages—all before giving you a single confirmation.
Sending Verification Codes: The Automation of Security
Security flows used to involve rigid scripts or developers manually calling APIs for every user's login attempt, leading to slow, brittle authentication processes. A failure in one step meant the entire system stopped.
Now, you simply tell your agent 'Verify user X.' It uses `send_verification_sms` and handles the whole sequence—sending the code, and if necessary, falling back to a voice call using `send_voice_verification`. The process just works.
What your AI can actually do with this
You can connect Chuanglan 253 directly to your AI agent via Vinkius, handling all communication workflows in plain language. Instead of logging into an external portal just to send out codes or check balances, you simply ask your agent what needs doing. You’ll manage everything from sending bulk messages worldwide to running complex two-factor authentication flows for 1-click logins.
Need to monitor delivery status? Just ask. Want to make sure compliance is handled? The system lets you list and create approved templates first. It's about turning those messy, multi-step dashboard tasks—checking quota, drafting a message, sending it out, then checking if it arrived—into one simple conversation with your agent.
019d8425-4f1e-73ed-a5c5-0ad7690fd609 Here's how it actually works
The bottom line is you ask your AI client for what you need—a verification code, a balance check, or a bulk send—and it executes the API call without you ever touching a web dashboard.
Subscribe to the Chuanglan 253 MCP and enter your API credentials.
Your AI agent connects, giving it access to all messaging tools.
You issue a natural language request, telling the agent exactly what messages need sending or what status needs checking.
Who is this actually for?
This MCP is essential for security engineers and development teams who deal with high-volume user authentication. It solves the pain of relying on clunky, separate vendor dashboards just to run basic communication tasks.
Runs multi-factor authentication flows by triggering send_verification_sms or using voice calls when a user needs to log in.
Integrates messaging into CI/CD pipelines, automating the sending of confirmation emails and tracking status via query tools.
Manages large-scale campaigns by checking available quota with get_sms_balance before running a bulk send operation.
What Changes When You Connect
Eliminate dashboard logins. You don't need to navigate complex menus; you just tell your agent, 'Send a code,' and it handles the call to send_verification_sms.
Manage compliance upfront. Use query_template_list or create_template before running any campaign to ensure all messages are pre-approved.
Handle global scale without friction. Whether you need to send a simple message via send_international_sms or manage account status with get_account_info, it’s one conversational prompt away.
Real-time visibility on delivery. Instead of guessing, the agent can check the precise status of any message using query_sms_status or track large sends with query_batch_sms_status.
Flexible security options. If SMS fails, you don't stop; you switch methods by asking the agent to run send_voice_verification, keeping your authentication flow running smoothly.
See it in action
User signs up for a new account.
The user asks their agent, 'Verify John Doe's phone number.' The agent knows to use send_verification_sms with the correct country code and tracks the status using query_sms_status. It completes the entire authentication flow without human intervention.
A marketing team runs a regional campaign.
The lead asks, 'Check our available quota for Brazil.' The agent executes get_sms_balance first. If successful, it then triggers multiple sends using send_international_sms, providing immediate confirmation.
A developer needs to test a bulk notification system.
Instead of manually sending 50 messages, the dev asks the agent to 'Send these 50 alert messages.' The agent uses send_sms and provides a single ID for tracking all results using query_batch_sms_status.
A security team needs a reliable fallback method.
When the primary SMS channel fails, the team asks, 'Switch to voice verification.' The agent immediately reroutes the request and calls send_voice_verification, ensuring the user still gets their necessary code.
The honest tradeoffs
Checking status manually.
Having to log into a separate vendor portal, search for a message ID, and wait for the page to load just to see if it was delivered.
Just ask your agent: 'What's the delivery status of message ID 12345?' The agent uses query_sms_status and reports back immediately.
Overwriting templates.
Writing a new message manually every time, which might violate company compliance or use outdated branding language.
Always list existing formats with query_template_list, then ask the agent to draft and approve changes using create_template.
Ignoring global requirements.
Trying to send a message to Brazil using the domestic sending function, which will fail because of country code rules.
Always specify international sends by asking the agent to use send_international_sms and provide the full country code.
When It Fits, When It Doesn't
Use this MCP if your core need is reliable, high-volume communication—especially authentication (OTP) or global outreach. The tools are perfect for anything that involves sending a message and checking its status against compliance rules like query_template_list. Don't use it if you just need to store contacts; those tools belong in a CRM connector. Also, don't rely on this solely for payment processing or data storage—it only handles messages. If your workflow is simple (just sending one message), you could use a direct API call, but using the MCP with Vinkius gives you the massive benefit of running complex multi-step processes (like check balance -> create template -> send verification code) all in natural conversation.
Questions you might have
How do I check my SMS credit balance using get_sms_balance? +
You ask your agent directly, 'What's our current SMS credit balance?' It executes get_sms_balance and returns the real-time quota count without needing you to log in.
Can I send messages outside of China? +
Yes. You must use the dedicated tool, send_international_sms, which is built for global numbers and country codes, ensuring successful delivery everywhere.
What if SMS fails? Can I use send_voice_verification? +
Absolutely. If text message delivery isn't reliable, you tell your agent to switch methods. It then uses send_voice_verification to call the user instead.
How do I manage approved messaging formats? +
You use query_template_list to see what's available, or you ask the agent to create new ones using create_template for compliance review.
How do I check my overall account settings and permissions using get_account_info? +
The get_account_info tool gives you a direct view of your Chuanglan 253 account status. You can review all enabled features, current permissions, and general operational settings without having to log into the main dashboard.
Should I use query_batch_sms_status or query_sms_status when checking delivery? +
Use query_batch_sms_status if you sent a group of messages and need one status report for the entire batch. If you only want to check the specific outcome of a single, unique message ID, then use query_sms_status.
What are the requirements when I run create_template? +
Templates require pre-approval before they can be used for sending messages. You must also include variable placeholders like {1} or {2} if you plan to inject dynamic content into the template later.
Does sending a regular domestic message need special formatting with send_sms? +
Yes, when using send_sms for Chinese domestic SMS, the message body must begin with a signature enclosed in brackets, like [YourBrand]. This ensures the message passes compliance checks.
How do I format phone numbers for sending SMS? +
Phone numbers must include the country code without the 00 prefix. For example: China uses 86 (e.g., 8615800000000), Brazil uses 55 (e.g., 5511999999999), US uses 1 (e.g., 12025551234). The number should be 5-20 digits total. For Chinese domestic SMS, the message must start with a registered signature like [YourBrand].
What's the difference between send_sms and send_international_sms tools? +
The send_sms tool uses the standard SMS gateway (smssh.253.com) optimized for Chinese domestic messages and requires pre-registered templates and signatures. The send_international_sms tool uses the international gateway (intapi.253.com) for global delivery outside China, which supports SenderId and doesn't require Chinese-style signatures. International SMS permissions must be separately enabled in your account.
How does the MD5 signature authentication work? +
The Chuanglan API uses MD5 signature authentication for security. Your password is NEVER sent in the request body. Instead, it's combined with the request parameters and timestamp (nonce), then hashed with MD5 to generate a sign header. The server validates this signature to ensure request integrity. The framework handles all signature generation automatically — you only need to provide your account and password.
We've already built the connector for Chuanglan 253. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.