Bring Omnichannel
to Google ADK
Learn how to connect Daktela to Google ADK and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Daktela MCP Server?
Connect your Daktela omnichannel contact center to any AI agent and simplify how you coordinate customer support, track communication history, and manage CRM records through natural conversation.
What you can do
- Ticket Lifecycle — Create, list, and query support tickets and cases to ensure customer issues are resolved promptly.
- Omnichannel Activities — Monitor real-time and past activities across calls, emails, and chats within your center.
- CRM Control — List and create contacts and accounts (companies) to maintain an organized customer directory.
- Call & Email History — Retrieve detailed logs of past phone interactions and email threads for audit and reporting.
- Team & Queue Coordination — List configured queues and system users to manage agent distribution effectively.
- Profile Oversight — Fetch your authenticated user profile and verify system configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Daktela Domain and Access Token (found in your user settings)
3. Start managing your omnichannel communications from Claude, Cursor, or any MCP client
Who is this for?
- Support Team Leads — quickly check ticket statuses and monitor queue volumes via simple AI commands.
- Customer Service Agents — create CRM contacts and log activities directly from the workspace.
- Operations Managers — verify call history and retrieve agent distribution metadata via the AI assistant.
Built-in capabilities (12)
Create a new CRM contact
Create a new ticket
Get current user information
Get details of a specific ticket
List CRM accounts
List recent activities in Daktela
List call history
List CRM contacts
List email history
List contact center queues
List support tickets
List Daktela users
Why Google ADK?
Google ADK natively supports Daktela as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 12 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.
- —
Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution
- —
Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Daktela
- —
Production-ready features like session management, evaluation, and deployment come built-in. not bolted on
- —
Seamless integration with Google Cloud services means you can combine Daktela tools with BigQuery, Vertex AI, and Cloud Functions
Daktela in Google ADK
Daktela and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Daktela to Google ADK 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 Daktela in Google ADK
The Daktela 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Google ADK 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
Daktela for Google ADK
Every tool call from Google ADK to the Daktela 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 all the open tickets in my Daktela account?
Yes! Use the list_tickets tool. Your agent will retrieve the complete directory of support cases, which you can then filter or summarize.
How do I create a new contact in the Daktela CRM?
Use the create_contact action. Provide the first name, last name, and optional email or phone number to register the person in your CRM database instantly.
Is it possible to list the history of past phone calls via AI?
Absolutely. Use the list_call_history query. The agent will retrieve a detailed log of past voice interactions, including participants and durations.
How does Google ADK connect to MCP servers?
Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
Can ADK agents use multiple MCP servers?
Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
Which Gemini models work best with MCP tools?
Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.
McpToolset not found
Update: pip install --upgrade google-adk