Bring Cloud Phone
to Cline
Learn how to connect Toky to Cline and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Toky MCP Server?
Connect your Toky cloud phone system account to any AI agent and simplify how you manage your business communications, call logs, and SMS outreach through natural conversation.
What you can do
- Call Management — List and search call history, retrieve detailed metadata, and monitor recent voicemails.
- SMS Automation — Send individual text messages to customers and leads directly via AI commands.
- Contact Oversight — List, create, and manage your phone directory to keep customer data synchronized.
- Team Coordination — Query agent lists and retrieve detailed profiles for your communication team.
- Operational Status — Fetch detailed metadata for specific calls or voicemails to understand interaction context.
- Communication Visibility — Monitor your cloud telephony activities directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Toky API Key (found in your developer settings)
3. Start managing your cloud phone system from Claude, Cursor, or any MCP client
Who is this for?
- Sales & Support Teams — quickly send SMS follow-ups and retrieve call logs via simple AI commands.
- Operations Managers — monitor agent availability and verify communication history across the team.
- Business Owners — maintain an organized record of customer interactions and voicemails directly from the workspace.
Built-in capabilities (10)
Create a new Toky contact
Get details for a specific Toky agent
Get details for a specific Toky call
Get details for a specific Toky contact
Get details for a specific Toky voicemail
Use limit and offset for pagination. List Toky agents
Use limit and offset for pagination. List Toky calls
Use limit and offset for pagination. List Toky contacts
Use limit and offset for pagination. List Toky voicemails
Send an SMS via Toky
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Toky tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Toky in Cline
Toky and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Toky to Cline 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 Toky in Cline
The Toky 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 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline 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
Toky for Cline
Every tool call from Cline to the Toky MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see my recent call history via AI?
Yes! Use the list_calls tool. Your agent will retrieve the history of all incoming and outgoing calls, including durations and participant details.
How do I send an SMS to a customer using the AI?
Use the send_sms action. Provide the destination phone number and your message text. The agent will trigger the SMS transmission through your Toky account instantly.
Is it possible to check for new voicemails via AI?
Absolutely. Run the list_voicemails query. The agent will retrieve a list of all recorded voicemails, which you can then inspect for specific interaction details.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.