Connecting to the Brightidea MCP

Table of Contents

• Before You Start
• MCP Server URL
• Connection Steps
• Test the Connection
• Local Development Testing
• Common Configuration Mistakes

Before You Start

Confirm that you have the following before connecting:

• An active Brightidea account
• Access to the Brightidea tenant you want to use
• An MCP-compatible AI client that supports remote HTTP or Streamable HTTP MCP servers
• Permission from your organization to connect approved AI clients to Brightidea

MCP Server URL

Use the hosted Brightidea MCP server URL:

https://mcp.brightidea.com/mcp

If your organization uses a private or test deployment, use the URL provided by your Brightidea administrator.

Connection Steps

1. Open the connector or MCP server settings in your AI client.
2. Add a new remote MCP server.
3. Select Streamable HTTP or Remote HTTP as the transport type. Do not use a command-based or stdio transport — the hosted server does not support those.
4. Enter the Brightidea MCP server URL and save the connection.
5. When prompted, sign in through the Brightidea OAuth flow.
6. If you belong to more than one tenant, select the correct one when asked.
7. Approve the requested access, then return to the AI client and confirm the connector shows as connected.

Test the Connection

After connecting, try a read-only request first to confirm everything is working:

Summarize the campaigns I can access in Brightidea.

Or:

Search Brightidea for ideas about onboarding.

If your client supports listing MCP tools, list the tools and confirm that Brightidea tools appear.

Local Development Testing

Developers testing a local server should use:

http://127.0.0.1:3000/mcp

Use the same host consistently — if the local server is configured with 127.0.0.1, configure the client with 127.0.0.1 as well. Hosted AI clients usually cannot reach your local machine directly. To test a local server from a hosted client, use a secure HTTPS tunnel and configure the MCP client with the tunnel URL ending in /mcp.

Common Configuration Mistakes

• Using the root URL without /mcp at the end
• Choosing a command-based or stdio transport instead of remote HTTP
• Mixing localhost and 127.0.0.1 during local OAuth testing
• Using an expired tunnel URL after restarting a local tunnel
• Connecting with a Brightidea account that does not have access to the target tenant

Related Articles

• Brightidea MCP Server — Overview
• Brightidea MCP Authentication and Access
• Troubleshoot Brightidea MCP Connections