Table of Contents
- Connection Issues
- Authentication Issues
- Tenant Issues
- Permission Issues
- Tool Issues
- Contacting Brightidea Support
Connection Issues
The client cannot connect to the server
Check that the MCP server URL ends in /mcp:
https://mcp.brightidea.com/mcp
Also confirm that the client is configured for Streamable HTTP or Remote HTTP. The hosted Brightidea MCP server does not use a local command, stdio, or SSE connection.
The client asks for a command instead of a URL
You are likely in the wrong connection mode. Choose the Remote MCP, Remote HTTP, or Streamable HTTP option in the client settings.
The local server works in a browser but not in MCP Inspector
If you're testing locally with MCP Inspector, the server may be rejecting the browser origin. Add the Inspector origin to your local server's configuration:
CORS_ORIGINS=http://localhost:6274,http://127.0.0.1:6274
Note: Restart the local server after changing environment variables.
Authentication Issues
Brightidea sign-in does not open
Confirm that your AI client supports OAuth for remote MCP servers. Also check that the MCP server URL is correct and that your browser allows popups or redirects from the AI client.
The client says authentication is required
Reconnect the Brightidea MCP server. This typically happens when a session expires, the client clears stored credentials, or a local development server restarts with in-memory OAuth state.
invalid_client appears during local testing
If the local server uses in-memory OAuth state, restarting the server clears dynamic client registrations. Remove and reconnect the MCP server in the client so it can register again.
Tenant Issues
The wrong tenant is connected
Disconnect and reconnect the MCP server. If prompted to choose a tenant, select the correct one during the Brightidea OAuth flow.
Tenant login is rejected
Confirm that:
- Your Brightidea account has access to the tenant.
- The Brightidea OAuth app is enabled for that tenant.
- The tenant host is allowed by the MCP server configuration.
If you're using a custom or test tenant, contact your Brightidea administrator or Brightidea support.
Permission Issues
A tool returns 403 Forbidden
This means your Brightidea account does not have permission for the requested action. Reconnecting will not grant additional roles. Ask a Brightidea administrator to confirm your access to the relevant campaign, group, rule, widget, report, or admin area.
A tool works for one campaign but not another
Brightidea permissions can differ by campaign, community, or role. Confirm that your account has access to the specific campaign or record used in the request.
Tool Issues
A direct API tool name does not work
Generated Brightidea API operations are not exposed as direct top-level tools. Use the API discovery workflow instead:
- Search for the operation with
search-api-tools. - Call the selected operation through
invoke-api-tool.
For common tasks, prefer the purpose-built workflow tools when available.
A bulk action looks risky
Stop and ask for a preview or dry run first. Review the output before applying the change.
A tool times out or hits a rate limit
Wait and retry. Large reports, bulk updates, and broad searches may take longer or hit tenant rate limits. Narrow the request by campaign, date range, status, or record IDs when possible.
Contacting Brightidea Support
When contacting support, please include the following:
- The MCP client you are using
- The MCP server URL
- The Brightidea tenant domain
- The approximate time of the issue
- The tool or request you attempted
- Any visible error message
- Whether the issue affects all tools or only one workflow
Note: Do not include passwords, MFA codes, OAuth tokens, API keys, or client secrets in your support request.
Related Articles
- Connect Brightidea MCP Server to an MCP Client
- Brightidea MCP Authentication and Access
- Use Brightidea MCP Safely
Comments