How to Configure the MCP Server in BoldDesk
The MCP Configuration page enables administrators to manage how external AI tools, IDEs, and applications connect to BoldDesk through the Model Context Protocol (MCP). Administrators can configure authentication methods and monitor authorized OAuth clients from a centralized location. From a centralized configuration page, you can control MCP availability, choose authentication methods such as OAuth 2.0 or API keys, and manage connected OAuth clients. This ensures secure access, streamlined integrations, and greater flexibility when connecting AI assistants, automation workflows, and third-party applications to BoldDesk.
Enabling MCP Access
Turn on MCP to view and manage its configuration, including authentication settings and connected clients. You can access and enable MCP by following the steps below.
- Navigate AI > AI Agent & Tools > MCP Server
- Toggle on Model Context Protocol. Refer to the GIF below for more insights.
Configure Authentication Methods
BoldDesk MCP supports the following authentication methods:
| Authentication method | Recommended for | User consent required | Security model |
|---|---|---|---|
| OAuth 2.0 | AI assistants, IDE extensions, user-facing integrations, and third-party applications | Yes | Scoped access tokens |
| API key authentication | Backend services, scheduled jobs, internal automation, and service-to-service integrations | No | API key-based authentication |
You can enable or disable each authentication method independently from the MCP Configuration page.
OAuth 2.0 Authentication
Best for user-authorized clients and connected applications using scoped access tokens. Use the toggle switch to enable or disable OAuth 2.0 authentication. If you disable OAuth 2.0 authentication, AI agents will no longer be able to authenticate using OAuth 2.0. MCP actions relying on this method will stop working until it’s re-enabled.
Use Cases
- AI assistants and copilots
- IDE extensions
- Third-party applications
- User-specific access scenarios
Benefits
OAuth 2.0 provides several advantages:
- User consent-based authorization
- Token-based authentication
- Scoped permissions
- Improved security for third-party applications
- Easier access management and revocation
For more information on configuring OAuth 2.0 authentication, explore BoldDesk MCP Server Authentication Using OAuth 2.0.
API Key Authentication
For trusted backend automation, scheduled jobs, and service-to-service integrations. Use the toggle switch to enable or disable API Key Authentication. If you disable API Key authentication, AI agents will no longer be able to authenticate using API keys. MCP actions relying on this method will stop working until it’s re-enabled. Explore API Key Authentication.
Use Cases
- Backend services
- Scheduled jobs
- Service-to-service integrations
- Internal automation workflows
Best Practices
- Store API keys securely.
- Do not expose API keys in client-side applications.
- Rotate keys periodically according to your organization’s security policies.
For more information on configuring API key authentication, explore How to Configure API Key Authentication for the BoldDesk MCP Server.
Use OAuth for user and third-party access. Keep API keys for trusted backend tasks, store securely, and rotate regularly.
Disabling MCP Access
Disabling MCP immediately disconnects all connected OAuth clients and blocks any services currently using MCP. Active integrations will stop functioning until MCP is re-enabled.
To disable MCP:
- Navigate AI > AI Agent & Tools > MCP Server
- Toggle off Model Context Protocol.
- Confirm by clicking on Disable MCP
