# Desku.io MCP MCP > Desku.io connects your support operations to any AI client, letting you handle everything from initial inquiry triage to final resolution. You can list and update tickets, check full conversation history across channels (email, chat, social), look up customer profiles, or even create a brand new ticket—all without opening the Desku dashboard. It centralizes complex helpdesk tasks into simple natural language commands. ## Overview - **Category:** customer-support - **Price:** Free - **Tags:** ai-support, unified-inbox, ticket-automation, customer-experience, helpdesk-software, chat-automation ## Description This MCP lets your agent take over your entire support workflow. Instead of navigating multiple dashboards just to figure out what happened with a customer's account, you ask your AI client and it does the heavy lifting across email, chat, and social channels. You can pull up detailed customer records, review every message history tied to a specific ticket, or even write a reply directly into the system. Need to update a status? Done. Want to add an internal note for a teammate? No problem. Because your AI agent runs on Vinkius, you gain visibility across all these actions; if you're building automations that need to check customer data before sending out a billing confirmation, the platform ensures every step is traceable and auditable. It turns complex support operations into simple conversations. ## Tools ### create_conversation Reply to a ticket ### create_ticket Create a new ticket ### get_customer Get customer details ### get_ticket Get ticket details ### list_agents List support agents ### list_conversations List conversation history for a ticket ### list_customers List support customers ### list_tickets io account. List support tickets ### update_ticket Update a ticket ## Prompt Examples **Prompt:** ``` List all active support tickets in Desku. ``` **Response:** ``` I've retrieved your support pipeline. You have 3 active tickets, including '#1024: Payment Failure' and '#1025: API Setup'. Would you like the full message history for the payment issue? ``` **Prompt:** ``` Show the conversation history for ticket #1024. ``` **Response:** ``` Fetching transcript... Ticket #1024 involves a customer reporting a 404 error during checkout. Agent Sarah replied with a fix 1 hour ago. The status is currently 'open'. Shall I add an internal note for Sarah? ``` **Prompt:** ``` Reply to ticket #1025: 'We have updated your API limits'. ``` **Response:** ``` Reply successfully sent! I've updated ticket #1025 with your message. The customer will be notified, and I've also updated the internal activity log. Need help with anything else? ``` ## Capabilities ### View Ticket Status and Details Fetch lists of current support tickets or pull up the full details for one specific ticket. ### Analyze Conversation History Retrieve the complete message transcript for any given ticket, giving you all context needed for a reply. ### Create and Update Communications Write new replies to tickets or add private notes visible only to internal staff. ### Manage Customer Records Get specific details about a customer by their ID, or list all active customers in the system. ### Initiate New Support Requests Create a brand new ticket for an issue that hasn't been reported before. ### Coordinate Team Resources Get directories and statuses of support staff to know who is available right now. ## Use Cases ### A user needs to know why a payment failed. The agent starts by calling list_tickets to find all recent issues. They then use get_ticket on the relevant ID and finally call list_conversations to read the chat history, diagnosing the failure reason before replying via create_conversation. ### A customer calls with a request for an account update. The agent first uses get_customer to verify the user's details. Then they use list_agents to check if there is a specialist available, and finally create_ticket to open a new formal support case. ### An internal report needs all closed tickets from last month. The operations lead calls list_tickets, filtering by date range and status. They can then use get_customer on the resulting ticket IDs to pull a summary of who those users were. ### A teammate needs help escalating an issue. Instead of guessing who is available, the agent calls list_agents to see who has 'Tier 3' clearance. They then use get_ticket on the current ID and call update_ticket to assign it directly to that person. ## Benefits - Speed up resolutions: You can reply directly using create_conversation or update_ticket, sending a message and changing the status without logging into three different places. - Never miss context: The list_conversations tool gives you the entire chat transcript for any ticket. This means you have all the necessary background info before typing a single word. - Instant customer visibility: Use get_customer or list_customers to pull up user data quickly, letting you tailor your response based on their history and profile. - Automate status changes: Don't manually change statuses. With update_ticket, you can programmatically mark tickets as 'resolved' or 'pending' when the task is done. - Triage new issues fast: If a customer hits you with something entirely new, use create_ticket to log it immediately and get it into the proper queue for follow-up. ## How It Works The bottom line is that you manage customer support workflows through conversation, not clicking through dashboards. 1. First, connect your Desku.io API key through the Vinkius platform using your preferred AI client (Claude, Cursor, etc.). 2. Next, tell your agent exactly what you need—for example, 'Get me all open tickets related to payments' or 'List customers who haven't logged in this month.' 3. Finally, your agent executes the required actions and returns clean data, allowing you to draft responses, change statuses, or create new records instantly. ## Frequently Asked Questions **How do I use list_tickets with Desku.io MCP?** list_tickets pulls up a filtered view of all support tickets, letting you see exactly which statuses (like 'open' or 'pending') are currently active in your system. **Can I use get_customer to look up details?** Yes. You call get_customer and provide the customer ID. It returns all the specific profile data you need, saving you from manual searching across multiple sheets or dashboards. **What is the difference between create_ticket and list_tickets?** list_tickets retrieves existing tickets in your pipeline, giving you a summary. You use create_ticket only when an issue happens that needs to be formally logged into your system. **Does Desku.io MCP allow me to add internal notes?** Yes. You can programmatically send replies using create_conversation, or you can use update_ticket to leave private collaborator notes visible only to your team members. **How do I use list_agents to check support team availability?** It provides a directory of all available agents and their current status. You can instantly see who is assigned or available for specific types of issues, which helps route the ticket faster. **What is the purpose of update_ticket versus just creating a message?** Use this tool to change the official status of the case—like moving it from 'Open' to 'Pending' or 'Closed.' It also lets you apply critical metadata, such as resolution codes, which simple replies can’t handle. **How do I use list_conversations if I need a full transcript?** It pulls the complete, chronological message history for a ticket. This gives you the high-fidelity context of every interaction that occurred, which is much deeper than just viewing the current metadata or status. **If I don't know a customer ID, can list_customers help me find them?** Yes. This tool retrieves a comprehensive list of all supported customers in your account. You can use this to search by name or company details before you pull up a specific ticket record.