For server-to-server or fully autonomous workflows that run without a human in the loop, the hosted BoldDesk MCP Server supports both OAuth 2.0 tokens and API keys in request headers.

The hosted BoldDesk MCP Server is stateless and does not differentiate between interactive users and automated agents, making it suitable for both conversational and autonomous use cases.

API Key approach

Include your BoldDesk API key in the x-api-key header with every request:

{
  "headers": {
    "x-api-key": "your-api-key-here"
  }
}

OAuth 2.0 approach

Include your OAuth access token in the Authorization header:

{
  "headers": {
    "Authorization": "Bearer your-oauth-token-here"
  }
}

Examples

Read-only prompts

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

Action-oriented prompts

  • Create a ticket for John Smith at john@acme.com with subject “Login issue” and high priority.
  • Add an internal note to ticket #1042 indicating the issue has been escalated to the engineering team.
  • Update the status of ticket #850 to Resolved.

For workflows that create tickets, send replies, or change ticket statuses, consider requiring a human confirmation step before execution, especially when the BoldDesk MCP Server is used alongside other tools or MCP Servers.