SmartBear MCP server

Configure the SmartBear MCP server for BugSnag On-premise.

Overview

The SmartBear Model Context Protocol (MCP) server provides a standardized way for AI agents to connect to and interact with your BugSnag On-premise installation. The MCP server is included in the On-premise installation along with an authorization server for users to set up an OAuth workflow for access.

Enabling the MCP server

You can enable the MCP server by reconfiguring BugSnag via the Admin Console (KOTS).

1. Navigate to the Config page in the Admin Console.
2. Scroll to the MCP settings section.
3. Check the box for Enable MCP.
4. Configure the following settings:
   • MCP server allowed endpoints: Comma-separated list of allowed endpoints for the MCP server in the format hostname:port. Setting to empty will allow all endpoints. Defaults to your Dashboard host.
   • MCP server allowed origins: Comma-separated list of CORS allowed origins for the MCP server. Setting to * will allow all origins. Defaults to *.
   • MCP OAuth server host: Hostname for the MCP OAuth server. Defaults to https://oauth.example.com and must be updated to your actual OAuth server host.
   • MCP OAuth server allowed origins: Comma-separated list of CORS allowed origins for the MCP OAuth server. Setting to * will allow all origins. Defaults to *.
   • MCP OAuth server access token expiry: Expiry time for access tokens issued by the MCP OAuth server in Golang duration format (e.g., 1h). Defaults to 1h.
   • MCP OAuth server refresh token expiry: Expiry time for refresh tokens issued by the MCP OAuth server in Golang duration format (e.g., 24h). Defaults to 24h.
   • MCP OAuth server auth code expiry: Expiry time for auth codes issued by the MCP OAuth server in Golang duration format (e.g., 10m). Defaults to 10m.
   • MCP OAuth server dynamic client expiry: Expiry time for dynamically registered clients in Golang duration format. Defaults to 0 (no expiry).
   • MCP OAuth server pre-configured clients: Clients can be pre-configured using the format ID@ID|SECRET|REDIRECT_URIS|SCOPES. Multiple clients can be separated by a semicolon (;).
5. Deploy the new configuration.

Load Balancing

In order to access the MCP server and its associated OAuth server from outside the cluster, you must configure load balancers. See our load balancing guide for the required ports and protocols.

AWS Resources

If you are using our provided CloudFormation template to install BugSnag, you can automatically provision external load balancers for the SmartBear MCP server and its associated OAuth server.

CloudFormation parameters

To create the load balancers and target groups, you should provide the following parameters when provisioning or updating your CloudFormation stack:

OAuth server load balancer

• CreateOAuthServerLBResources: Set to true to create the OAuth server load balancer.
• OAuthServerHostname: Hostname to use for creating a public DNS record for the OAuth server load balancer.
• OAuthServerCertificateArn: ARN of the certificate to use for the OAuth server load balancer.
• OAuthServerLBIngressCidrBlock: Optional override for the IPv4 CIDR block of addresses allowed to access the OAuth server load balancer.

If you are using an externally managed load balancer, you can specify the target group using OAuthServerLBTargetGroupArn. By default, the Kubernetes node port is 30008 and can be overridden with OAuthServerK8sNodePort.

SmartBear MCP server load balancer

• CreateSmartbearMcpLBResources: Set to true to create the SmartBear MCP load balancer.
• SmartbearMcpHostname: Hostname to use for creating a public DNS record for the SmartBear MCP load balancer.
• SmartbearMcpCertificateArn: ARN of the certificate to use for the SmartBear MCP load balancer.
• SmartbearMcpLBIngressCidrBlock: Optional override for the IPv4 CIDR block of addresses allowed to access the SmartBear MCP load balancer.

If you are using an externally managed load balancer, you can specify the target group using SmartbearMcpLBTargetGroupArn. By default, the Kubernetes node port is 30007 and can be overridden with SmartbearMcpK8sNodePort.

Once you have provisioned the load balancers, remember to reconfigure BugSnag via the Admin Console (KOTS) to set the MCP OAuth server host to match the hostname of the newly created OAuth server load balancer.