Bring Onewaysms
to Claude Desktop
Learn how to connect OneWaySMS to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the OneWaySMS MCP Server?
Connect your OneWaySMS account to any AI agent and take full control of your global SMS orchestration through natural conversation. OneWaySMS provides a reliable and high-speed gateway for business messaging, and this integration allows you to send standard or Unicode SMS, monitor credit balances, and track delivery statuses directly from your chat interface.
What you can do
- SMS & Messaging Orchestration — Send individual or bulk text messages programmatically to ensure your alerts and notifications are always synchronized.
- Unicode & Multilingual Support — Dispatch messages using standard ASCII or Unicode (for special characters and emojis) via natural language to reach your global audience.
- Credit & Balance Intelligence — Access and monitor your available SMS credit balance directly from the AI interface to ensure uninterrupted service.
- Transaction & Delivery Control — Retrieve real-time delivery status for any message using its unique Transaction ID (MTID) using simple AI commands.
- Operational Monitoring — Track system responses and manage regional gateway settings to ensure your communication pipeline is always optimized.
How it works
1. Subscribe to this server
2. Enter your OneWaySMS API Username and API Password from your dashboard
3. Start managing your SMS communications from Claude, Cursor, or any MCP-compatible client
No more manual logging to check if a message was delivered. Your AI acts as a dedicated messaging coordinator or operations assistant.
Who is this for?
- Operations Managers — quickly send emergency alerts and monitor credit usage without switching apps.
- Customer Success Teams — automate the delivery of status updates and track message reception via natural conversation.
- Developers — integrate real-time SMS capabilities and balance tracking directly within the chat.
Built-in capabilities (11)
Verify API connectivity
Check remaining SMS credits
Get a detailed delivery report for a message
Get current API and gateway configuration
Retrieve character limits and regional policies
Track message delivery status
List approved Alphanumeric Sender IDs
Send SMS to multiple recipients at once
Send a one-time verification code via SMS
Send a standard text message
). Limit 70 chars per credit. Send a Unicode text message
Why Claude Desktop?
Claude Desktop is the definitive way to connect OneWaySMS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
OneWaySMS in Claude Desktop
OneWaySMS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OneWaySMS to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OneWaySMS in Claude Desktop
The OneWaySMS MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
OneWaySMS for Claude Desktop
Every tool call from Claude Desktop to the OneWaySMS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the delivery status for a specific SMS by its transaction ID?
Yes! Use the get_status tool with the Transaction ID (MTID). Your agent will respond with the current delivery state (e.g., Delivered, Failed, or Pending) in seconds.
How do I find my OneWaySMS API Username and Password?
Log in to your OneWaySMS dashboard, navigate to the API section, and you will find your dedicated API Username and API Password (which are different from your web login).
What is the character limit for ASCII vs Unicode messages?
Standard ASCII messages allow up to 160 characters per SMS. Unicode messages (which support special characters and emojis) are limited to 70 characters per SMS.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.