Overview of BoldDesk MCP Server
The BoldDesk MCP Server is a hosted server that implements the Model Context Protocol (MCP) to allow MCP-compatible AI clients to create, update, and manage BoldDesk support tickets and related support operations. Any MCP-compatible client can connect to the BoldDesk MCP Server, authenticate using an API key, and perform actions within the scope of the authenticated user’s permissions.
What the BoldDesk MCP Server Enables
The BoldDesk MCP Server provides a structured interface for AI systems to interact with BoldDesk support operations. After a client is connected:
- AI agents can execute support-related actions using MCP tools.
- Actions run under the authenticated user identity, so the effective access is limited by that user’s permissions and accessible brands.
- MCP transport uses an HTTPS endpoint with authentication via a request header.
Why Use the BoldDesk MCP Server
Organizations use the BoldDesk MCP Server to enable AI-assisted support operations such as:
- Automating repetitive support processes using AI-driven workflows.
- Managing tickets through natural language conversations.
- Accessing real-time support information from AI assistants.
- Integrating BoldDesk support operations into coding environments, AI applications, and custom automation platforms.
- Improving operational efficiency through intelligent support automation.
This section describes supported outcomes only. It does not introduce additional configuration or automation triggers beyond what is explicitly described in this guide.
How the BoldDesk MCP Server Works
The BoldDesk MCP Server acts as a secure bridge between AI agents and the BoldDesk platform. It translates AI requests into structured API operations while maintaining security, consistency, and predictable behavior.
Through the MCP Server, AI agents can:
- Create new support tickets.
- Update existing tickets.
- Manage ticket statuses and assignments.
- Reply to ticket conversations.
- Retrieve ticket details and conversation history.
- Search contacts, agents, and groups.
- Handle approval-related workflows.
All actions are executed within the scope of the authenticated user’s permissions and accessible brands.
Connecting to the BoldDesk MCP Server
The hosted MCP Server supports a variety of MCP-compatible clients, including AI chat interfaces, development environments, and autonomous agent frameworks.
Supported Clients
| Client | Setup Instructions |
|---|---|
| Claude Desktop | Configure the MCP Server at the project level using a .mcp.json file and authenticate with your API key. |
| ChatGPT | Add the BoldDesk MCP Server as a custom connector in ChatGPT Pro, Plus, Business, or Enterprise plans. |
| GitHub Copilot | Configure the MCP connection through the .vscode/mcp.json file in Visual Studio Code and authenticate using your API key. |
| Code Studio | Configure the MCP Server using the user-level mcp.json configuration file located in: C:\Users\<user>\AppData\Roaming\Syncfusion Code Studio\User\mcp.json Authentication should be performed using your API key. |
Connecting Other MCP Clients
If you’re using another MCP-compatible client that supports remote HTTP transport and custom headers, you can connect directly to the BoldDesk MCP endpoint using an x-api-key header.
Endpoint
https://your-subdomain.bolddesk.com/mcp
Replace your-subdomain with your BoldDesk account subdomain.
In addition to the default BoldDesk domain, you can also use a mapped custom domain for the MCP endpoint.
Fully Managed and Hosted
The BoldDesk MCP Server is fully managed and hosted, eliminating the need to deploy, maintain, or monitor server infrastructure.
Benefits include:
- No installation or infrastructure requirements.
- Secure hosting and maintenance by the BoldDesk team.
- Instant access through a standard HTTPS endpoint.
- Automatic updates and ongoing platform improvements.
- Faster onboarding for AI-powered support workflows.
Get Started
- Identify the MCP-compatible client to connect (Claude Desktop, ChatGPT, GitHub Copilot, Syncfusion Code Studio, or another MCP client with HTTP transport support).
- Configure the client to use the BoldDesk MCP endpoint.
- Authenticate using the BoldDesk API key via the
x-api-keyheader. - Confirm access aligns with the authenticated user’s permissions before executing ticket-modifying actions.
