Overview

The BoldDesk MCP Server enables AI agents to seamlessly create, update, and manage support tickets in BoldDesk. Built on the Model Context Protocol (MCP), an open standard for connecting AI applications to external tools and services, it integrates easily with popular AI platforms such as Claude, ChatGPT, GitHub Copilot, and autonomous agent workflows.

The MCP server exposes a structured set of 31 tools that AI agents can access through the MCP standard, enabling consistent, reliable, and predictable interactions with BoldDesk. Any MCP-compatible client can connect, authenticate, and immediately start interacting with BoldDesk to perform real support operations.

The BoldDesk MCP Server is fully hosted, meaning there is no local installation, package, or infrastructure to maintain. Your MCP client connects straight to a per-account HTTPS endpoint.

What can you do with BoldDesk MCP?

  • Automate support workflows with AI-driven actions: Create, update, and route tickets from natural-language requests.
  • Manage ticket conversations conversationally: Post public reply, public note, or internal note messages, and pull message history.
  • Get real-time insights and act on them directly from your AI assistant: Look up ticket status, history, worklogs, activities and approvals.
  • Search and resolve BoldDesk records from within your MCP client: Contacts, contact groups, agents and groups.

Features

  • Fully managed and hosted: No local setup, npm installation, or ongoing maintenance; access via a simple HTTPS endpoint.
  • Dual authentication: OAuth 2.0 token or x-api-key header, scoped to the authenticated user's permissions and associated brands.
  • Multi-client support: Works with Claude Code, ChatGPT, GitHub Copilot, Code Studio, and any MCP-compatible client over remote HTTP transport.
  • Custom domain support: Use the default BoldDesk system domain or a mapped custom domain for the MCP endpoint.
  • 30 tools across 7 functional areas: Tickets, conversations, activities, approvals, worklogs, contacts search, and reference metadata.

How it works

The MCP Server acts as a secure bridge between AI agents and BoldDesk APIs, letting them communicate securely and consistently. With the MCP Server connected, AI agents can:

  1. Create, update, and manage support tickets.
  2. Reply to ticket conversations.
  3. Retrieve ticket details and message history.
  4. Search contacts, groups, and agents.
  5. Handle approval workflows.
  6. Create and track activities (tasks, calls, meetings).
  7. Log and retrieve billable/non-billable work time.

Available tools

The BoldDesk MCP Server exposes 30 tools, grouped into 7 functional areas:

Tool domain What's accessible
Tickets Full ticket records (subject, description, status, priority, brand, requester, assignee, tags, attachments, custom fields), ticket forms/field schemas, and valid statuses per brand.
Ticket conversations Public replies, public notes, internal notes, system messages, and full change history.
Ticket links Related, parent, and child ticket links, plus external web links.
Activities Tasks, calls, and meetings, with type, priority, status, assignee, dates, linked tickets/users, and comments.
Approvals Approval requests and their type (everyone / anyone / majority), approvers, status, and responses.
Worklogs Time entries against tickets or activities, with billable status.
Directory Contacts, contact groups/companies, agents, and assignment groups.
Identity & reference Current user identity, organization, brand access, and form capabilities; field options for categories, types, sources, time zones, and activity types.

View detailed tool reference

All of these are scoped by the authenticated user's BoldDesk permissions and brand access — an AI agent can only see and act on what that user could see and act on in BoldDesk itself.

Connect to the BoldDesk MCP Server

The hosted MCP Server works with AI chat interfaces, coding editors, and autonomous agent workflows. No local installation is required. Simply point your client at the endpoint and authenticate.

Endpoint:

https://your-subdomain.bolddesk.com/mcp

Replace your-subdomain with your BoldDesk account subdomain (a mapped custom domain also works). All tool calls are scoped to the authenticated user's permissions and associated brands.

Authentication Use either of the following:

  • An OAuth 2.0 token
    • {
  "servers": {
    "bolddeskMcp": {
      "type": "http",
      "url": "https://<your-subdomain>.bolddesk.com/mcp"
    }
  }
}
  • An x-api-key header.
    • {
  "servers": {
    "bolddeskMcp": {
      "type": "http",
      "url": "https://<your-subdomain>.bolddesk.com/mcp",
      "headers": {
        "x-api-key": "your-api-key-here"
      }
    }
  }
}

Per-client setup

Client How to connect
Claude Add the BoldDesk MCP Server as a custom connector and authenticated via OAuth 2.0.
ChatGPT Add the BoldDesk MCP Server as a plugin, authenticated via OAuth 2.0 or API key.
GitHub Copilot (VS Code) Configure .vscode/mcp.json, authenticated via OAuth 2.0 or API key.
Code Studio Add the server from the built-in MCP Servers UI using the HTTP connection type, authenticated via OAuth 2.0 or API key.
Any other MCP-compatible client Connect via remote HTTP transport with custom headers, using an OAuth 2.0 token or x-api-key header.

Fully managed and hosted

BoldDesk offers a fully managed, hosted MCP Server — no local setup or ongoing maintenance. Get started without installation or infrastructure, on a securely hosted and maintained service, reachable over a simple HTTPS endpoint.