BoldDesk MCP. Manage tickets, contacts, and agents from your chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
BoldDesk MCP Server connects your entire customer support workflow to any AI agent. Use this server to manage tickets, read customer history, and coordinate agent tasks right from your conversation.
You can list all tickets, create new ones, add private notes, or reply publicly to a customer, all without leaving your chat interface.
What your AI agents can do
Add ticket note
Adds a private note to a specific ticket record.
Create ticket
Creates a brand new support ticket in BoldDesk.
Get agent
Fetches detailed information about a single support agent by name or ID.
You can list tickets, retrieve specific details, and then update the ticket status or add a public reply using discrete tool calls.
The agent can list all contacts and retrieve specific customer profiles to inform the conversation or resolution.
Use the add_ticket_note tool to leave private comments on a ticket that only internal staff can see.
List all agents and retrieve details for specific agents, helping you track team assignments and availability.
Quickly create a new support ticket using the create_ticket tool, specifying the issue and the affected user.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
BoldDesk MCP Server: 10 Tools for Support and Customer Management
These ten tools let your AI agent handle the entire support process: creating tickets, updating status, checking customer data, and coordinating agents.
019d7560add ticket note
Adds a private note to a specific ticket record.
019d7560create ticket
Creates a brand new support ticket in BoldDesk.
019d7560get agent
Fetches detailed information about a single support agent by name or ID.
019d7560get contact
Retrieves all profile details for a specific customer contact.
019d7560get ticket
Gets the complete history and current status of a single ticket.
019d7560list agents
Lists all support agents currently registered in your system.
019d7560list contacts
Provides a list of every customer contact in your directory.
019d7560list tickets
Retrieves a list of all open and closed support tickets.
019d7560reply to ticket
Adds a public, visible reply to a specific ticket for the customer to see.
019d7560update ticket
Modifies existing ticket fields, such as changing status or adding core data.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with BoldDesk, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You've got the BoldDesk MCP Server hooked up to your AI agent, and it's time to run your whole support workflow straight from the chat. You can manage tickets, read customer history, and coordinate your team right here, without leaving the chat window. You'll list all tickets and retrieve specific ticket details; you can then update the ticket status or reply to the ticket publicly for the customer to see.
You also add a private note to a ticket, so only your team sees it. You can list all contacts and get specific customer profiles to keep the conversation informed. To get a new issue logged, you create a new ticket, and you can list all agents and get details for a specific agent to track who's on the job.
How BoldDesk MCP Works
- 1 Subscribe to the server and provide your BoldDesk API Key and Domain.
- 2 Your AI client identifies the user's intent (e.g., 'Check ticket 102').
- 3 The AI client calls the relevant tool (
get_ticket) and sends the data back to you for action.
The bottom line is: your AI agent executes API calls directly to BoldDesk, managing support tasks within the chat window.
Who Is BoldDesk MCP For?
Support Leads who need an instant overview of team capacity and ticket queues. Customer Success Managers who need to pull full customer histories into a chat window. Developers building automated processes who need to embed support logic into their own applications.
Quickly list tickets and check agent assignments to monitor team bandwidth without logging into the dashboard.
Retrieve a customer's full profile and recent ticket history directly into their workflow tool to write informed replies.
Use the agent to add private notes or reply publicly to a ticket, maintaining a full audit trail while staying in chat.
What Changes When You Connect
- Close the loop on context switching. Instead of logging into BoldDesk, checking the contact record, opening the ticket, and then drafting a reply, your agent uses the tools to pull all necessary history and write the response—all from the chat interface.
- Maintain a perfect audit trail. When you use
add_ticket_note, the note is stored privately on the ticket, ensuring internal review details are captured without cluttering the public customer reply. - Instantly generate tickets. Need to track a bug? Use
create_ticketto log the issue immediately. You specify the subject and user, and the ticket hits the queue without manual data entry. - Keep track of your team. Use
list_agentsandget_agentto quickly see who is assigned to what. You can monitor team activity and see who is available, all in natural language. - Deep customer context. Retrieving data with
get_contactgives you the full customer profile. This means your AI agent can write a reply that references past purchases or known issues, making the interaction feel personal. - Handle status changes easily. If a ticket needs to move from 'Open' to 'Awaiting Customer Reply', use
update_ticketto change the status and ensure the ticket moves through the correct process steps.
Real-World Use Cases
A Customer Calls with a Known Bug
A customer calls about a bug. The agent first uses get_contact to pull the customer's account details. Next, they use get_ticket to see the history of that specific bug report. Finally, they use reply_to_ticket to provide the resolution steps directly in the ticket, keeping everything visible to the customer.
Onboarding a New Feature Request
A customer suggests a new feature. The agent uses list_tickets to see if similar requests exist. They then use create_ticket to log the request, ensuring the product team gets a formal, trackable ticket ID immediately.
Investigating a Team Bottleneck
The support lead notices tickets are piling up. They use list_agents to see who is working. They then use get_agent to check a specific agent's assignment count, helping them rebalance the workload instantly.
Escalating a Complex Issue
A ticket needs engineering review. The agent uses get_ticket to gather all the initial conversation logs. They then use add_ticket_note to privately flag the ticket for the engineering team, ensuring the customer never sees the escalation details.
The Tradeoffs
Manual Dashboard Checking
The agent logs into BoldDesk, clicks the 'Tickets' tab, filters by 'Open,' scrolls through dozens of entries, finds the ID, then copies the ID into the chat to ask the AI to get details.
→
Just ask your AI client directly: 'Get details for ticket ID 105.' The agent uses get_ticket directly, skipping the dashboard clicks and getting the full history instantly in the chat.
Forgetting Context
The agent replies to the customer but forgets to update the ticket status (e.g., leaving it 'Open' when it should be 'Pending Review').
→
After drafting the reply, always follow up with a tool call: 'Update ticket 105 status to Pending Review.' Use update_ticket to ensure the ticket's state matches the conversation.
Too Much Data in One Place
The agent tries to paste a giant wall of text containing customer history, agent details, and ticket status all into a single chat message, making it hard for the AI to parse.
→
Use the specific tools one at a time. First, ask the AI to get_contact for the profile. Then, ask it to get_ticket for the history. This structured data retrieval keeps the chat clean and accurate.
When It Fits, When It Doesn't
Use this server if your team needs to manage the entire ticket lifecycle—from initial contact to internal escalation—without ever leaving your AI client. This is for teams whose primary bottleneck is context switching and manual data entry. You must be comfortable having the AI agent executing ten discrete, sequential API calls. Don't use it if your biggest need is advanced automation like routing tickets based on keywords (you'd need a dedicated workflow engine). Also, don't use it if you only need to read data; you still need to use get_ticket or get_contact to pull the specific data you need.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BoldDesk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Managing support tickets shouldn't feel like juggling five different tabs.
Today, handling a customer inquiry means bouncing between the CRM, the ticketing dashboard, and internal notes. You open the ticket, copy the customer's email, switch to the contact record to verify their account, and then paste that data back into the ticket to make a reply. It's a cycle of copy-pasting and switching windows.
With the BoldDesk MCP Server, you keep everything in the chat. You tell your agent to 'Check ticket 102 for the billing issue.' The agent runs `get_ticket`, pulls the full history, and you get the answer instantly. You can then use `reply_to_ticket` and `add_ticket_note` without leaving the chat.
BoldDesk MCP Server: Full Control Over Ticket Actions
The biggest time sink is the manual status change. You write the reply, then you have to remember to log back into the dashboard and click 'Change Status to Solved.' If you forget, the ticket remains open and unassigned, creating ghost work.
Now, you simply tell your agent: 'Reply to the customer, and then update ticket 102 to Solved.' The agent executes `reply_to_ticket` and then runs `update_ticket` in sequence. The ticket status is correct, and the audit trail is perfect.
Common Questions About BoldDesk MCP
How do I list all active support tickets using the list_tickets tool? +
You simply ask your agent to 'List all open tickets.' The agent runs list_tickets and provides a list of ticket IDs and subjects right in the chat.
Can I add private notes to a ticket using the add_ticket_note tool? +
Yes. You can tell your agent to 'Add a private note to ticket 105 for engineering review.' The note is logged internally and only visible to your team.
What is the difference between reply_to_ticket and update_ticket? +
Use reply_to_ticket when you need the customer to see your message. Use update_ticket when you need to change the ticket's metadata, like its status or priority, without sending a message.
How do I get a customer's profile using the get_contact tool? +
Ask your agent to 'Get the contact details for John Doe.' The agent runs get_contact and returns the full profile—emails, account IDs, and any other stored data.
Can I create a new ticket using the create_ticket tool? +
Yes. Just tell your agent: 'Create a new ticket about API timeouts for user jane@example.com.' The agent handles the creation and returns the new ticket ID.
How do I get details for a specific support agent using the get_agent tool? +
The get_agent tool fetches a specific agent's profile. You'll need the agent's ID to pinpoint the details, which helps you track their assignments or status.
What tools are available for managing customer contacts, like list_contacts and get_contact? +
You can list all contacts with list_contacts to get an overview of your directory. Then, use get_contact with a specific ID to pull detailed information on an individual user.
Can I modify an existing ticket's information using the update_ticket tool? +
Yes, update_ticket lets you change the core details of a ticket. You'll provide the ticket ID and the fields you want to modify, like changing the status or assignee.
Can I check the status of a specific support ticket? +
Yes! Use the get_ticket tool with the Ticket ID. Your agent will fetch the latest status, priority, and the full conversation history directly from BoldDesk.
How do I add a private note to a ticket for my team? +
Simply ask the agent to add_ticket_note and provide the Ticket ID and the content of your note. This will be added as a private internal note invisible to the customer.
Does the integration allow creating a ticket for a new user? +
Yes. When using create_ticket, if the requester email does not exist in your contact list, BoldDesk will automatically create a new contact profile for that user.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
BL.INK
Manage enterprise links via BL.INK — shorten URLs, track analytics, and manage branded domains directly from any AI agent.
SoundCloud
Manage your SoundCloud account — audit tracks, playlists, and followers via AI.
MakePlans
Online booking and appointment scheduling via MakePlans MCP.
You might also like
Repuso
Collect and manage customer reviews effortlessly with Repuso AI agents.
Skydropx API
Ship effectively across LatAm with Skydropx. Compare real-time carrier quotes, track live parcels, and draft PDF labels via prompt.
commercetools
commercetools is a flexible, cloud-native e-commerce platform that provides a headless API for composable commerce. This MCP server allows you to manage products, orders, and customer data programmatically.