# Desku.io MCP MCP > Desku.io MCP unifies your customer support workflow across email, chat, and social channels. It lets your agent manage tickets, track customer history, and resolve issues using natural conversation commands. Stop switching tabs; control your entire helpdesk from one place. ## Overview - **Category:** customer-support - **Price:** Free - **Tags:** ai-support, unified-inbox, ticket-automation, customer-experience, helpdesk-software, chat-automation ## Description This connector gives you full control over your customer support operations, treating your helpdesk like a single, unified system accessed through dialogue. Your AI client can list active tickets, check out the complete message history for any issue, and programmatically add replies or internal notes without ever touching the Desku.io dashboard. You can also pull up detailed customer profiles to maintain context across every interaction. If you're looking at other ways to connect your support channels, checking Vinkius ensures you find the right fit; it hosts thousands of connectors like this one. The result is that your agent acts as a dedicated support engineer, managing everything from ticket creation to final closure using simple natural language prompts. ## Tools ### create_conversation Adds a new reply or note directly into an existing support ticket thread. ### create_ticket Automatically generates and logs a brand-new support issue in the system. ### get_customer Retrieves detailed profile information for a specified customer account. ### get_ticket Fetches all metadata and current status details for one specific ticket ID. ### list_agents Returns a directory of available support staff, showing who's active or assigned to which queue. ### list_conversations Retrieves the full message history and transcript for an entire ticket thread. ### list_customers Provides a list of all support customers registered in the system. ### list_tickets Lists multiple support tickets, giving you an overview of your entire active ticket pipeline. ### update_ticket Modifies existing ticket records, such as changing the status or adding internal comments. ## 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 ### Manage Ticket Lifecycle List all current tickets and update their status or metadata programmatically. ### Retrieve Customer Context Fetch comprehensive details for specific customers, including a complete log of every ticket they've ever generated. ### Analyze Conversation History Access the full message transcript and history associated with any given support ticket for context building. ### Interact Directly with Tickets Create new replies or add private internal notes directly to an open ticket. ### Track Support Staff Get a directory listing of available support agents and their current assignments. ## Use Cases ### The Hand-Off Scenario A Tier 1 agent gets an escalated ticket. Instead of emailing a manager for help, they ask their agent to 'list agents' and then use the available directory data to figure out who needs to take ownership, saving 10 minutes of coordination. ### The Failed Payment Follow-Up A customer calls about a billing issue. The agent asks for 'get_customer' details first, then uses the account data to check if there are any related tickets, making sure they don't address the wrong problem. ### The Bulk Status Update Operations needs to mark 20 old issues as 'closed.' Instead of opening 20 ticket records and changing the status one by one, they run a command that uses `update_ticket` on multiple IDs. ### The Quick Response A customer replies to an old thread. The agent asks 'create_conversation' with the solution, sending the reply and also updating the ticket status in one go. ## Benefits - Stop manually checking ticket statuses; simply asking to 'list active support tickets' gives you the status overview instantly using `list_tickets`. - You don't have to jump between tabs to see who's working—using `list_agents` shows team availability directly in your chat window. - Need context? Running `list_conversations` pulls the full, multi-turn history for any ticket so you can write an informed reply without deep searching. - The ability to pull up a customer's profile via `get_customer` means you know their whole story before you even draft your first line. - If a client has a new issue that needs tracking, running `create_ticket` logs it immediately, so nothing slips through the cracks. ## How It Works The bottom line is you manage complex customer relationships using simple commands instead of manual dashboard navigation. 1. Subscribe to the Desku.io MCP on Vinkius, then grab your API key from your Desku.io account settings. 2. Connect your agent client (like Cursor or Claude) and prompt it with a specific support task, e.g., 'What is the status of ticket #1234?' 3. The MCP executes the necessary tool call, fetches the data, and relays the actionable result back to your AI chat interface. ## Frequently Asked Questions **How do I check a customer’s entire history with the Desku.io MCP?** You use 'list conversations.' This tool pulls the complete, chronological message transcript for any ticket ID, giving you maximum context. **Can I update multiple tickets at once using the Desku.io MCP?** The `update_ticket` function allows programmatic modification of existing records. You can use it to bulk-change statuses or add metadata across several ticket IDs. **What if I need to start a new support case quickly?** Run 'create ticket.' This tool logs the issue immediately in your system, giving you a unique ID and ensuring it enters the proper workflow queue right away. **Does list agents tell me who is available to help now?** Yes. The `list_agents` function retrieves directories of support staff, helping you quickly understand team availability and current assignments. **When I use `list_tickets`, what does the MCP do if the list is very long?** The MCP handles standard API rate limiting for large requests. If you need to process thousands of tickets, we recommend chunking your calls or referencing Desku's specific documentation for dedicated batch endpoints. **How accurate is the data returned by `get_customer`?** It provides core profile information and a summary of the customer’s full ticket history. For highly niche data points, always cross-reference the specific details with Desku's official API docs. **If I use `update_ticket` and an error occurs, how do I know why?** The MCP returns a clear status code and detailed message explaining exactly what failed. You must capture this response to inform your agent so it can retry the action or flag it for manual review. **`get_ticket` requires specific authentication? What do I need?** You'll need an API Key from your Desku.io profile settings. This key authenticates all actions, allowing your agent to read ticket details and manage the associated data. **How do I find my Desku API Key?** Log in to Desku.io, click your profile picture, navigate to **Profile Settings**, and you will find your API Key at the bottom. **Can I add internal notes for other agents?** Yes! Use the `create_conversation` tool and specify that the message is an internal note to coordinate with your team privately. **How do I see who is assigned to a ticket?** The `get_ticket` tool retrieves complete metadata including the assigned agent ID and their current status.