Bold Reports® MCP Server Limitations

The hosted Bold Reports® MCP Server is a managed service with specific operational boundaries. Review the following limitations before integrating the MCP Server into your workflow.

1. Single Site Only

Each MCP configuration can connect to only one Bold Reports® site at a time. Multi-site configurations are not supported.

Supported:

"X-BoldReports-BaseUrl": "https://{yourdomain}/reporting/api/site/{tenant-name}"

Not Supported:

"X-BoldReports-BaseUrl": [
  "https://{yourdomain}/reporting/api/site/{tenant-name1}",
  "https://{yourdomain}/reporting/api/site/{tenant-name2}"
]

Use separate MCP configurations for each site you need to connect to.

2. No OAuth Configuration Support

The MCP Server currently does not support OAuth-based authentication when connecting to Bold Reports® instances. Only API key-based authentication is supported at this time.

Not Supported:

  • OAuth 2.0 authentication
  • OAuth token-based connections
  • Third-party identity provider integrations

Supported:

  • API key-based authentication
  • Personal access tokens
  • Public hosted Bold Reports®

Note: MCP currently works only with publicly hosted Bold Reports® sites. On-premise installations are not supported.

Summary of Limitations

Limitation Scope Workaround
Single site per MCP config Configuration Use a separate MCP config for each site
No OAuth configuration support Authentication Use API key-based authentication

The limitations listed above reflect the current state of the hosted MCP Server and are subject to change in future releases.