The BoldDesk MCP Server can be integrated with popular AI assistants, development environments, and autonomous agent platforms. Once configured, AI-powered tools can securely access and manage support operations within your BoldDesk account using the Model Context Protocol (MCP).

This guide explains the requirements, supported clients, configuration methods, and example prompts for getting started.

Requirements

Before connecting a client to the BoldDesk MCP Server, ensure the following requirements are met:

Supported AI Clients

The hosted BoldDesk MCP Server supports multiple MCP-compatible clients and development environments.

Supported clients include:

• Claude Code
• ChatGPT
• GitHub Copilot
• Syncfusion Code Studio
• Autonomous agents

All supported clients use API key authentication.

Claude Code

Claude Code provides native support for remote MCP Servers over HTTPS, making it one of the easiest ways to connect to the BoldDesk MCP Server.

The recommended approach is to store your API key as an environment variable and reference it within a project-level .mcp.json file.

Configuration

{
  "mcpServers": {
    "bolddesk": {
      "type": "http",
      "url": "https://<your-subdomain>.bolddesk.com/mcp",
      "headers": {
        "x-api-key": "${BOLDDESK_API_KEY}"
      }
    }
  }
}

Replace <your-subdomain> with your BoldDesk account subdomain.

Benefits

• API keys are not stored directly in configuration files.
• Credentials remain portable across environments.
• Sensitive information is protected from accidental source control commits.

Verify the Connection

After saving the configuration:

1. Start Claude Code in the configured project.
2. Open /mcp.
3. Verify that the BoldDesk MCP Server appears as connected.
4. Confirm that tools are available.
5. Run a read-only prompt such as:

List my open tickets.

ChatGPT

You can connect the BoldDesk MCP Server to ChatGPT using one of the following plans:

• ChatGPT Pro
• ChatGPT Plus
• ChatGPT Business
• ChatGPT Enterprise
• ChatGPT Education

Before proceeding, ensure that Developer Mode is enabled.

Enable Developer Mode

1. Open Settings → Apps → Advanced Settings
2. Enable Developer Mode

Create the MCP App

1. Open Settings → Apps
2. Click Create App
3. Enter the following details:

4. Review the MCP Server risk notice.
5. Select I understand and want to continue.
6. Click Create.
7. Enter your BoldDesk API key.
8. Click Connect.
9. Start a new conversation and select the BoldDesk MCP app.

GitHub Copilot

The BoldDesk MCP Server can be integrated directly into Visual Studio Code through GitHub Copilot.

Prerequisites

• Visual Studio Code version 1.99 or later
• A valid BoldDesk API key
• Access to the hosted MCP endpoint

Workspace Configuration

Create the following file:

.vscode/mcp.json

Add the configuration below:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bolddesk-api-key",
      "description": "BoldDesk API key",
      "password": true
    }
  ],
  "servers": {
    "bolddeskMcp": {
      "type": "http",
      "url": "https://<your-subdomain>.bolddesk.com/mcp",
      "headers": {
        "x-api-key": "${input:bolddesk-api-key}"
      }
    }
  }
}

The promptString input ensures that GitHub Copilot requests the API key securely when establishing a connection.

The API key is never stored in configuration files or committed to source control.

Global Configuration

To make the BoldDesk MCP Server available across all Visual Studio Code workspaces:

1. Open the Command Palette.
2. Run MCP: Open User Configuration.
3. Add the same server configuration to the user-level MCP settings.

This enables the MCP Server globally across all projects.

Syncfusion Code Studio

The BoldDesk MCP Server can also be configured in Syncfusion Code Studio.

Configuration Location

Create the mcp.json file in the following location:

C:\Users\<user>\AppData\Roaming\Syncfusion Code Studio\User\mcp.json

Configuration Example

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bolddesk-api-key",
      "description": "BoldDesk API key",
      "password": true
    }
  ],
  "servers": {
    "bolddeskMcp": {
      "type": "http",
      "url": "https://<your-subdomain>.bolddesk.com/mcp",
      "headers": {
        "x-api-key": "${input:bolddesk-api-key}"
      }
    }
  }
}

Security Benefits

• Secure API key prompting.
• No plaintext credentials stored in files.
• Prevents accidental exposure through source control.

Autonomous Agents

The hosted BoldDesk MCP Server can be used in server-to-server integrations and autonomous AI workflows.

Authentication

Include the API key in the x-api-key header with every request.

Example Header

x-api-key: YOUR_API_KEY

The BoldDesk MCP Server is stateless and treats autonomous agents and interactive users the same way, making it suitable for:

• AI workflows
• Automation platforms
• Background processes
• Multi-agent systems
• Server-to-server integrations

Example Prompts

Read-Only Prompts

Use these prompts to validate connectivity and permissions before making changes.

1. List all open tickets assigned to me.
2. Which tickets have been waiting for a customer reply for more than 3 days?
3. Show me the details of ticket #1042.

Action-Oriented Prompts

Once connectivity is verified, you can perform support operations using natural language.

1. Create a ticket for John Smith at [email protected] with subject “Login issue” and high priority.
2. Add an internal note to ticket #1042 indicating the issue has been escalated to the engineering team.
3. Update the status of ticket #850 to Resolved.

Best Practices

To ensure safe and reliable automation:

• Validate your connection with read-only prompts first.
• Protect API keys and never expose them publicly.
• Use least-privilege access wherever possible.
• Review client-specific authentication settings carefully.
• Consider requiring human approval before executing actions that create, update, or close tickets.

By following these recommendations, you can confidently integrate AI assistants and autonomous agents with BoldDesk while maintaining security, accuracy, and operational control.