List of Available MCP Tools in BoldDesk
The hosted BoldDesk MCP Server provides a focused set of tools that enable AI assistants and MCP-compatible clients to perform common help desk operations. These tools allow AI agents to interact with tickets, conversations, users, and approval workflows while respecting the authenticated user’s permissions and access scope.
Ticket Management Tools
Ticket management tools support the complete lifecycle of a support ticket.
| Tool | Description |
|---|---|
| Create Ticket | Create a new support ticket with subject, description, priority, category, and custom fields. |
| Update Ticket | Update ticket properties such as priority, category, assignee, or custom fields. |
| Update Ticket Status | Change a ticket’s status using valid status transitions. |
| Get Ticket | Retrieve ticket details including status, priority, requester, assignee, and metadata. |
| List Tickets | View tickets within the authenticated user’s scope using supported filters. |
Conversation Management Tools
Conversation management tools allow AI agents to interact with ticket discussions and communication history.
| Tool | Description |
|---|---|
| Add Ticket Message | Add a public reply, public note, or internal note to a ticket conversation. |
| Get Ticket Messages | Retrieve the paginated conversation history of a ticket, including replies and notes. |
Discovery and Metadata Tools
These tools provide account and configuration information required for dynamic workflows.
| Tool | Description |
|---|---|
| Get User Info | Return tenant information, agent identity, accessible brands, and available forms. |
| Get Ticket Fields | Retrieve ticket types and fields, including API names, field types, and allowed values. |
| Get Ticket Statuses | Return valid status transitions based on a ticket’s current status. |
When to Use Discovery Tools
Use discovery tools before performing actions when the client must:
- Populate valid values for ticket fields (including custom fields).
- Validate allowable ticket status transitions.
- Determine which brands or forms the authenticated user can access.
Search and Lookup Tools
Search tools help locate customers, agents, and groups for ticket routing and assignment.
| Tool | Description |
|---|---|
| Search Contacts | Find customers by email address, name, phone number, or contact ID. |
| Search Agents | Find agents by name or identifier for ticket assignment. |
| Search Groups | Locate agent groups or teams by name or identifier. |
| Search Contact Groups | Search contact groups by name or identifier. |
Activity Tools
Activity tools enable users to create, track, and retrieve activity tickets within their authorized scope. They support activity management workflows by allowing users to create new activities, view existing activities with filters, and access detailed information such as status, priority, assignee, and related metadata.
| Tool | Description |
|---|---|
| Create Activity | Create a new activity ticket with subject, description, priority. |
| List Activity | View activity within the authenticated user’s scope using supported filters. |
| Get Activity Details | Retrieve activity details including status, priority, assignee, and metadata. |
Approvals Tools
Approval tools allow approval-based workflows to be managed through MCP clients.
| Tool | Description |
|---|---|
| Create Approval Request | Create and manage approval requests associated with support tickets. |
| List Approvals | View approval requests assigned or requested by authenticated user’s scope using supported filters. |
| Get Approval Details | Retrieve approval request details including status, requested by, approvers, and metadata. |
| Approver Action - Approve/Reject/Cancel | Change the approval request status - Approved / Rejected / Cancel based |
Recommended First Test
Before performing actions such as creating or updating tickets, verify your MCP connection using a read-only request.
| Example Prompt |
|---|
| Show me my open tickets |
This confirms that authentication, permissions, and connectivity are working correctly before running action-oriented tools.
