Bold Reports® MCP Server Limitations

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

Can I connect one MCP configuration to more than one site?

No. 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.

Does the MCP Server support OAuth?

No. 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
  • Publicly hosted Bold Reports®

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

What are the limitations at a glance?

Limitation Scope Workaround
Single site per MCP configuration Configuration Use a separate MCP configuration 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.

Frequently asked questions

Does the MCP Server work with on-premise Bold Reports®?

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

How do I connect to multiple Bold Reports® sites?

Create a separate MCP configuration for each site. Each configuration connects to one site through its X-BoldReports-BaseUrl header.

Which authentication methods are supported?

API key-based authentication and personal access tokens are supported. OAuth 2.0 and third-party identity providers are not supported.

See also